Re: [prometheus-users] Re: Freeze dates & release dates

We only have a fixed release schedule for Prometheus itself. Exporter releases are cut by the maintainers as needed, depending on the changes merged. /MR On Fri, Jun 5, 2020, 02:08 Ranganath Sunku wrote: > I meant to ask for Prometheus node_exporter in particular. > > On Thursday, June 4, 2020

Re: [prometheus-users] Re: Freeze dates & release dates

There is no specific release schedule or cadence for the node_exporter. We release when there is sufficient need and or bug fixes are ready. On Fri, Jun 5, 2020 at 2:08 AM Ranganath Sunku wrote: > I meant to ask for Prometheus node_exporter in particular. > > On Thursday, June 4, 2020 at 5:03:49

[prometheus-users] Is there any unique id for an alert sent by alert-manager?

Learned from this link is-the-fingerprint-field-in-alertmanager-unique that both fingerprint and generatorURL are not unique. Wonder whether prometheus would provide a function to generate a GUID that

[prometheus-users] alertmanager: no private IP found

I made a service for alertmanager, which is like this: Description=Alert Manager Wants=network-online.target After=network-online.target [Service] Type=simple User=alertmanager Group=alertmanager ExecStart=/usr/local/bin/alertmanager \ --config.file=/etc/alertmanager/alertmanager.yml \ --s

[prometheus-users] Re: Timestamp of last change of metric

timestamp(my_metric) gives you the time at which the last sample in my_metric was recorded. timestamp(my_metric == 1)in principle ought to give you the last time when it was 1, but I think instant queries only look back a few minutes, so you might need to use a subquery. Documentation link: h

[prometheus-users] Re: file_sd_configs common label

Yes, by adding the common labels to each target group: [ { "targets": [ "localhost:9100" ], "labels": { * "env": "production",* "job": "slave" } }, { "targets": [ "localhost:9200" ], "labels": { * "env": "production",* "job": "mas

[prometheus-users] Re: alertmanager: no private IP found

It seems this label solve the problem --cluster.advertise-address="public-ip:9093" On Saturday, June 6, 2020 at 4:04:42 PM UTC+4:30, Saeedeh Moghimi wrote: > > I made a service for alertmanager, which is like this: > > > Description=Alert Manager > Wants=network-online.target > After=network-

Re: [prometheus-users] Resuable Template not found

Here is my alertmanager version info: alertmanager, version 0.20.0 (branch: HEAD, revision: f74be04 ) build user: root@00c3106655f8 biold date: 20191211-14:13:14 go version: gol.13.5 Please clarify what y

Re: [prometheus-users] Resuable Template not found

The configuration file that you posted was mangled - partly by your E-mail client I guess, and partly by you (there are two single quotes before ''my.host') However, if I use *exactly* the following configuration file: global: smtp_smarthost: 'my.host:25' smtp_hello: 'my.system' smtp_from

[prometheus-users] Re: file_sd_configs common label

thanks. On Saturday, June 6, 2020 at 7:57:51 AM UTC-4, Brian Candler wrote: > > Yes, by adding the common labels to each target group: > > [ > { > "targets": [ > "localhost:9100" > ], > "labels": { > * "env": "production",* > "job": "slave" > } > }, > { >

[prometheus-users] unexspected behaviour for collector.mountstat on kubernetes

Hi, I'm getting unexpected results with prometheus-node-exporter on kubernetes. I'm using the prometheus operator and I enabled the mounstat collector (I can see the right config in the description for the daemonset and for the pods). But no statistics are collected. The /proc of the node is mo

[prometheus-users] How to setup prometheus using ansible

I have a task to setup an environment where I need to have an autoscaling group, load balancer and two ec2 instances with prometheus installed on them. Along side a single standalone ec2 instance with prom aggregation gateway package installed on it. All this has to be set up using ansible. I a