Re: [prometheus-users] Re: Select metric only if another does not exist

Seems to work correctly. Thank you very much! On Tuesday, August 4, 2020 at 5:57:30 PM UTC+3, Aliaksandr Valialkin wrote: > > Try the following query: > > metric_name unless on (hostname) another_metrics{type="value"} > > On Tue, Aug 4, 2020 at 2:44 PM Sam Lee > > wrote: > >> try metric{type != "

[prometheus-users] scrape_interval is not working properly.

Hello, I want to collect the HTTP requests per second every second. To do so, I'm using Prometheus and Prometheus Adapter. I set the value of 'scrape_interval', 'scrape_timeout', and 'evaluation_interval' to 1s in the Prometheus ConfigMaps resource of K8S as follows: [image: 스크린샷 2020-08

Re: [prometheus-users] Re: Select metric only if another does not exist

Try the following query: metric_name unless on (hostname) another_metrics{type="value"} On Tue, Aug 4, 2020 at 2:44 PM Sam Lee wrote: > try metric{type != "two"} ? > > 在 2020年8月4日星期二 UTC+8下午3:30:05，Seitan写道： >> >> Hello, >> I'm trying to do a promql query to select only hosts, that don't have >

[prometheus-users] Re: Able to specify bind port, but not address

"latest prometheus" -> prometheus-2.20.0.linux-amd64 > > -- 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+unsubscr...@googlegroups.com. To vi

[prometheus-users] Able to specify bind port, but not address

Latest prometheus, on RHEL8. Tried command: ./prometheus Expected behavior: bind to 0.0.0.0:9090 Observed behavior: bound to 127.0.0.1:9090 Tried command: ./prometheus --web.listen-address=0.0.0.0:9090 Expected behavior: bind to 0.0.0.0:9090 Observed behavior: bound to 127.0.0.1:9090 Tried

[prometheus-users] How to prevent sending resolve notification after resolve_timeout? 

Hey guys,I have a problem with configuration of resolve_timeout. As it means, a notication of resolved will be send after the timeout. But actually the issue still be firing, it disturb the correct resolved notification How can I prevent it? -- You received this message because you are subscrib

[prometheus-users] Re: Select metric only if another does not exist

try metric{type != "two"} ? 在 2020年8月4日星期二 UTC+8下午3:30:05，Seitan写道： > > Hello, > I'm trying to do a promql query to select only hosts, that don't have > specific label on them. > For example, selecting metrics from hosts who DO have label (type=value) > works: > > metrics_name * on (hostname) an

Re: [prometheus-users] external_labels from prometheus not able to use as filter in Grafana Dashboard variables

This sounds like a `label="$var"` vs `label=~"$var"` issue. Grafana sometimes formats the variable as a regexp, so you need to use `=~` for it to work. On Tue, Aug 4, 2020 at 6:52 AM Pavan Vasisht wrote: > Hi, > > Using the helm(*Version:"v3.2.4", > GitCommit:"0ad800ef43d3b826f31a5ad8dfbb4fe05d1

[prometheus-users] Re: Select metric only if another does not exist

metric{type != "two"} ? 在 2020年8月4日星期二 UTC+8下午3:30:05，Seitan写道： > > Hello, > I'm trying to do a promql query to select only hosts, that don't have > specific label on them. > For example, selecting metrics from hosts who DO have label (type=value) > works: > > metrics_name * on (hostname) anoth

[prometheus-users] can I add for remote_read

I have to remote_read from influxdb and another prometheus, can I add labels to distinguish the two remote_read just as below: # read data from kafka remote_read: - url: http://192.168.11.10:30070/api/v1/prom/read?db=prometheus read_recent: true labels: from: influxdb # read data from p

[prometheus-users] Prometheus memory issue

Hi All , I am facing Memory usage with Prometheus service and Maintaining 30 days of data from Node exporter, Process exporter and JMX exporter for 95 servers in Prometheus Database. Grafana and Prometheus are running on the same node. When loading node_exporter or JVM Graf

[prometheus-users] blackbox dns probe failed

Host operating system: output of uname -a Linux office-monitor 3.10.0-957.el7.x86_64 #1 SMP Thu Nov 8 23:39:32 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux blackbox_exporter version: output of blackbox_exporter -version blackbox_exporter, vers

[prometheus-users] Re: Select metric only if another does not exist

Hello, the problem is that the node has label with many values: metric{type="one"}, metric{type="two"}, metric{type="three"} I just need do query against those nodes, who has no metric{type="two"} On Tuesday, August 4, 2020 at 10:30:05 AM UTC+3, Seitan wrote: > > Hello, > I'm trying to do a pr

[prometheus-users] Re: Select metric only if another does not exist

On Tuesday, 4 August 2020 08:30:05 UTC+1, Seitan wrote: > > I'm trying to do a promql query to select only hosts, that don't have > specific label on them. > The empty value is equivalent to "no label": metric{type=""} will select timeseries 'metric' which have no label 'type'. -- You receive

[prometheus-users] Select metric only if another does not exist

Hello, I'm trying to do a promql query to select only hosts, that don't have specific label on them. For example, selecting metrics from hosts who DO have label (type=value) works: metrics_name * on (hostname) another_metrics{type="value"} Problem is when i try to do same select against hosts w