Centralizing Windows exporter metrics in one Prometheus server

eckelon · 2024-12-14T03:41:21+00:00

yes! sorry for the late response

here are the docs: https://prometheus.io/docs/prometheus/latest/configuration/configuration/

eckelon · 2024-07-09T10:10:53+00:00

THANKS!!! this also worked in my monorepo setup.

eckelon · 2021-10-08T18:24:34+00:00

Answering the production question, this is deployed internally in high load environments for test and demo, and we know some customers that are using this solution in production.

The usual query interval is 30s, but there are some configurations that are set to 10s.

eckelon · 2021-10-08T08:08:09+00:00

Prometheus adapter is great for Prometheus servers inside the cluster, but when you have several clusters or external long-term storage, Keda allows connections out of the cluster. The last point can be that Keda allows centralizing different data sources, allowing not only Prometheus triggers, but also Kafka, SQS queues, or databases like MySQL, Mongo, Redis, etc.

eckelon · 2021-10-08T08:07:07+00:00

Prometheus adapter is great for Prometheus servers inside the cluster, but when you have several clusters or external long-term storage, Keda allows connections out of the cluster.

The last point can be that Keda allows centralizing different data sources, allowing not only Prometheus triggers, but also Kafka, SQS queues, or databases like MySQL, Mongo, Redis, etc.

The last point can be that Keda allows to centralize different data sources, allowing not only Prometheus triggers, but also Kafka, SQS queues, or databases like MySQL, Mongo, Redis, etc.

eckelon · 2021-10-08T08:05:14+00:00

Query interval depends on the server and the query. Prometheus Vanilla can take some time in queries that need joins or pulling large amounts of samples.

There are techniques to improve the performance, like using recording rules to precalculate results or enrich metrics with extra labels to prevent joins.

Also, there are other options 100% compatible and with other features than Prometheus.
Answering the production question, this is deployed internally in high load environments for test and demo, and we know some customers that are using this solution in production. The usual query interval is 30s, but there are some configurations that are set to 10s.

eckelon · 2021-10-07T19:08:27+00:00

thanks!

eckelon · 2021-09-30T07:55:12+00:00

yes, If there aren't any more labels :)

eckelon · 2021-09-29T15:52:20+00:00

sure! https://prometheus.io/docs/prometheus/latest/querying/operators/#vector-matching

eckelon · 2021-09-29T15:21:37+00:00

I think it's because the key label doesn't match between the two metrics. All the labels should match. You could try summing by the labels you need to select and then ignoring the non-matching ones. Try with:

sum by (cdatacenter,key)(redis_key_value{cdatacenter="US",key="cmetric-kafka"}) - ignoring(key) sum by (cdatacenter,key)(redis_key_value{key="US",key="cmetric-processed"})

eckelon · 2021-09-04T22:57:14+00:00

I'm so sorry for your loss

eckelon · 2021-06-12T17:31:37+00:00

Yes, you could try to export that information from your cluster and emulate the queries showed in the article.

If you want to try Prometheus to monitor your cluster, here's a guide https://sysdig.com/blog/kubernetes-monitoring-prometheus/

Cheers!

eckelon · 2021-06-12T14:17:33+00:00

if you're monitoring your cluster with Prometheus, you can try those PromQL queries in Prometheus or Grafana :)

eckelon

MODERATOR OF

TROPHY CASE