Re: [prometheus-users] Debugging OOM issue.

No, concurrency only affects how many queries are running at the same time. On Wed, Nov 25, 2020 at 8:45 AM Yagyansh S. Kumar wrote: > Thanks, Ben. Was thinking of doing the same because a single query is > causing my Prometheus to go down occasionally. > One query though, will limiting the conc

Re: [prometheus-users] Debugging OOM issue.

Thanks, Ben. Was thinking of doing the same because a single query is causing my Prometheus to go down occasionally. One query though, will limiting the concurrency slow down the overall evaluation process? On Wed, Nov 25, 2020 at 1:07 PM Ben Kochie wrote: > Maybe set a lower `--query.max-sample

Re: [prometheus-users] Debugging OOM issue.

Maybe set a lower `--query.max-samples` flag setting. The default is 50 million samples. I typically lower this to 20 million to avoid too-heavy queries. You can also lower the defualt `--query.max-concurrency=20` to avoid overloading. Likely, if you need to make large queries, you should allocate

[prometheus-users] Selectors in kubernetes_sd_configs don't restrict services based on labels

Hello, I'm trying to scrape all services that have labels *app: core. *However, after adding the below section to kubernetes_sd_configs, I'm not getting limited services in the Prometheus targets list. In fact, the configuration file does not save saying not able to parse the YAML config file.

[prometheus-users] Templating

Hi All, We have configured multiple Prometheus alerts with one single template in Alertmanager configuration and every alert is triggered with Runbook and Grafana link. Now the problem is, All my alerts are referring to different Grafana dashboards. Currently whenever we receive any alert, its

Re: [prometheus-users] Debugging OOM issue.

Thanks, Christian. Today I noticed something that is totally new to me. Prometheus went down and I got the query because of which it went down but strangely at that time I checked the server did not go OOM, the Memory dropped directly from constant usage of 77% to zero, but usually when a Query

[prometheus-users] Re: what's the best practice to collect metrics and write to different remote storage with different bear_token_file

BTW, someone also make another suggestions, maybe useful for people who have same scenerio. Instead of having a agent to scrape data for every tenant, we can use one prometheus to scrape the data, and write a remote write adapter to receive these data, split them, and route to different remote

[prometheus-users] what is the right way to setup alertmanager in Federation?

If we enable Alertmanagers in dedicated clusters, then how do we route the alerts to receiver ? Do we send the alerts to receivers directly from dedicated clusters? or should we route the alerts from dedicated clusters to central Federation Alertmanager? If yes, how to chain the alertmanagers?

Re: [prometheus-users] Re: How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

On 24/11/2020 17:30, b.ca...@pobox.com wrote: I'm guessing what's happened is: 1. You've run an (unnamed) security scanner against node_exporter 2. The scanner has come back with this message, telling you that node_exporter should return an STS header. I'm saying that the scanner's conclusion

[prometheus-users] Metrics API not registered when using promethus adapter

Hi I have installed a new prometheus adaptor using this https://github.com/prometheus-community/helm-charts/tree/main/charts/prometheus-adapter,i could see v1beta1.custom.metrics.k8s.io registered,but couldn't see the v1beta1.metrics.k8s.io.I

Re: [prometheus-users] Re: How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

Perfect. you are spot on. Thanks for your inputs. It helps us. Thanks & Regards, Selvam E. On Tue, 24 Nov 2020, 23:00 b.ca...@pobox.com, wrote: > I'm guessing what's happened is: > 1. You've run an (unnamed) security scanner against node_exporter > 2. The scanner has come back with this mess

Re: [prometheus-users] Re: How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

I'm guessing what's happened is: 1. You've run an (unnamed) security scanner against node_exporter 2. The scanner has come back with this message, telling you that node_exporter should return an STS header. I'm saying that the scanner's conclusion is wrong. Firstly, node_exporter isn't a web se

Re: [prometheus-users] Re: How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

Thanks. I am still confused. Can we just configure Https in Prometheus for scrape to address cwe693 STS. Or If we enable TLS in node exporter to fix STS vaulnerability. Kindly clarify. Thanks Selvam E. On Tue, 24 Nov 2020, 21:49 b.ca...@pobox.com, wrote: > node_exporter isn't accessed via

Re: [prometheus-users] Prometheus using AWS Timestream

On 24/11/2020 14:06, 'ellis...@googlemail.com' via Prometheus Users wrote: the guy that wrote the adapter suggests that a Grafana plugin would be used to read the information from Timestream in AWS. Yes, but that doesn't help for alerting, recording rules, etc. which are in Prometheus. -- Y

[prometheus-users] Re: How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

node_exporter isn't accessed via a browser - it's accessed only from prometheus scrapes. If you configure prometheus to scrape using https, then it will only use https. STS won't make any difference. Furthermore, if you configure node_exporter to use TLS, then it will *only* serve TLS. It doe

[prometheus-users] How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter?

How to enable STS to address CWE-693: Protection Mechanism Failure in node_exporter? -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsu

Re: [prometheus-users] Prometheus using AWS Timestream

the guy that wrote the adapter suggests that a Grafana plugin would be used to read the information from Timestream in AWS. On Tuesday, 24 November 2020 at 12:47:12 UTC Stuart Clark wrote: > On 24/11/2020 09:53, 'ellis...@googlemail.com' via Prometheus Users wrote: > > Hi all, > > > > Is anyone

Re: [prometheus-users] Prometheus using AWS Timestream

On 24/11/2020 09:53, 'ellis...@googlemail.com' via Prometheus Users wrote: Hi all, Is anyone using Prometheus in AWS to monitor and if so have you thought about using Timestream as a remote storage solution? I can see that there is a remote write adapter available at https://github.com/dpat

[prometheus-users] Prometheus using AWS Timestream

Hi all, Is anyone using Prometheus in AWS to monitor and if so have you thought about using Timestream as a remote storage solution? -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails

[prometheus-users] Re: Timescale DB setup

Hey Sree hari, I had sent you a follow mail mentioning the details. Is it resolved by now? If not, feel free to mention on TimescaleDB slack on promscale channel: invite link

Re: [prometheus-users] Sample Code in Go/C++ to Publish Metrics to a Remote Write Endpoint

Hey AI, We (TimescaleDB team) are in the process of adding support to easily push prometheus metric data to Promscale/TimescaleDB. The PR is already merged and we are writing examples and docs for users to understand in simple terms how to use this feature. For knowing more information on this

[prometheus-users] Re: Security on Prometheus target

1. basic_auth is HTTP basic authentication : a standard and well-documented HTTP mechanism. The exporter itself will have to implement this mechanism of course (or you can sit the exporter behind a proxy which implements it) 2. the au