[prometheus-users] Prevent large integers from being displayed in scientific notation in golang

2020-11-20 Thread Ken Sato
Hello, I wonder how can I show large integers as integers with the client_golang. For example, if I set 1234567 in a gauge, it is displayed like this sample_gauge 1.234567e+06 I would like to show it as follows. sample_gauge 1234567 I understand the value of metrics is float64 and it shou

Re: [prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread juan chaves
ok Stuart Clark, thanks for your help. success, expected result. the documentation does not make it clear which files to add. I added the labels in each file: site01.yml - targets: site01.localhost labels: group: slack01 site02.yml - targets: site02.localhost labels: group:

Re: [prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread Stuart Clark
On 20/11/2020 18:16, juan chaves wrote: I read the documentation, but I have no idea how to assemble this part. would you have an example? Assuming YAML your file is currently something like targets:   - target1   - target2 You'd just add a labels section as well labels:   label1: value  

Re: [prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread juan chaves
I read the documentation, but I have no idea how to assemble this part. would you have an example? Em sexta-feira, 20 de novembro de 2020 às 14:02:12 UTC-3, Stuart Clark escreveu: > On 20/11/2020 16:47, juan chaves wrote: > > what did you say i understand. > > however there is the blackbox_expor

Re: [prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread Stuart Clark
On 20/11/2020 16:47, juan chaves wrote: what did you say i understand. however there is the blackbox_exporter and the files site01.yml and site02.yml in file_sd_configs, I need each one to direct to an alert rule. then it is easy to target the alert rules matching the alertmanager routes. Y

[prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread juan chaves
what did you say i understand. however there is the blackbox_exporter and the files site01.yml and site02.yml in file_sd_configs, I need each one to direct to an alert rule. then it is easy to target the alert rules matching the alertmanager routes. Em sexta-feira, 20 de novembro de 2020 às 13:

Re: [prometheus-users] The possibility of multiple push gateways

2020-11-20 Thread Harald Koch
On Fri, Nov 20, 2020, at 07:54, Stuart Clark wrote: > A "normal" push gateway setup, with auto-restart in case of failure > (e.g. Kubernetes, systemd, auto scaling group), optionally with state > storage on disk is usually adequate to handle failures (which should be > pretty rare). If there was

[prometheus-users] Re: Use different receiver for each list in the blackbox file.

2020-11-20 Thread b.ca...@pobox.com
By adding labels to some alerts (which you can do in your alerting rules), and by matching on those labels in the "routes " section of your alertmanager config. There are examples here

[prometheus-users] Use different receiver for each list in the blackbox file.

2020-11-20 Thread juan chaves
Hello people. this is my blackbox configuration it has two files (lists of sites). below my configuration of alerts using slack. my question is, how can i use different receiver for each list in the blackbox. ex: sites01.yml use slack sites02.yml use email. config blackbox - job_name: '

[prometheus-users] exposing jms and jdbc jmx data

2020-11-20 Thread shayan shafizadeh
hi i need to expose jdbc and jms jmx data for my java programs. how can i configure the yml config file for Prometheus jmx exporter to expose in its http service my jdbc and jms jmx data? i dont have the mbean names that the jdbc driver or jms driver expose jmx data with. -- You received thi

[prometheus-users] Re: Keeping specific systemd name labels

2020-11-20 Thread b.ca...@pobox.com
As the error says, you are using unsupported regex syntax. Prometheus supports the syntax of the RE2 library: https://github.com/google/re2/wiki/Syntax For more complex ways of combining drop/keep expressions, you can use __tmp labels. Here is an example which doesn't solve your particular pr

[prometheus-users] Re: Collect specific OIDs

2020-11-20 Thread Cihan Tunali
Here is prometheus.yml config. - job_name: 'snmp2' scrape_interval: 120s scrape_timeout: 120s file_sd_configs: - files : - /etc/prometheus/targets2.yml metrics_path: /snmp params: module: [customsnmp] relabel_configs: - source_labels: [__addres

[prometheus-users] Collect specific OIDs

2020-11-20 Thread Cihan Tunali
Hello all, I want to collect only 1.3.6.1.2.1.31.1.1.1.10 and 1.3.6.1.2.1.31.1.1.1.6 OID from my devices via snmp_exporter. Is there any way to do it? I tried to generate snmp.yml file and cleaned generator.yml but still i got all OIDs and collection them took to much time (such as 2minutes :(

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

2020-11-20 Thread 闵骏
I'm setting up a kubernetes cluster for user. They need to deploy different deployment, each of them have their own metrics for pods/deployment/service, and also have its own bear_token to write to remote storage. It's something like a big company user, own the cluster, with multiple departmen

Re: [prometheus-users] Re: Keeping specific systemd name labels

2020-11-20 Thread Matthias Rampke
Go regexes unfortunately do not support negative matches. I believe you can get the behavior that you need by having a temporary label, and changing it based on the various conditions: 1. you want to keep all metrics by default (action replace, target __tmp_keep, replacement "yes") 2. you want to

Re: [prometheus-users] Checkpoint FW mibs vs snmp generator

2020-11-20 Thread 'Vasilii Mazyliuk' via Prometheus Users
Ok I fugured it out I needed all MIBs from `make mibs` as well and I have tried only checkpoint mibs. Problem solved! Thanks for the help and sorry for disturbance! On Friday, 20 November 2020 at 11:38:38 UTC+2 Vasilii Mazyliuk wrote: > Actually I don't know what does it mean here by > *Cannot

Re: [prometheus-users] The possibility of multiple push gateways

2020-11-20 Thread Stuart Clark
On 2020-11-20 12:25, Andy Pan wrote: Got it! Thank you very much! About the inconsistent metrics, is it possible to dispatch metrics by hash and put those metrics with the same labels into the same push gateway, avoiding the inconsistent metrics? You were originally talking about having multipl

[prometheus-users] Re: The result of delta function is not same with raw data?

2020-11-20 Thread b.ca...@pobox.com
On Friday, 20 November 2020 at 02:29:12 UTC mono...@gmail.com wrote: > *Query*: > 1. normal query: error_counter_something{job=“monitor”, device=“dev0”, > serial=“”} > 2. delta query: delta(error_counter_something{job=“monitor”, > device=“dev0”, serial=“”}[$__interval] > 0) > >

Re: [prometheus-users] The possibility of multiple push gateways

2020-11-20 Thread Andy Pan
Got it! Thank you very much! About the inconsistent metrics, is it possible to dispatch metrics by hash and put those metrics with the same labels into the same push gateway, avoiding the inconsistent metrics? 在2020年11月20日星期五 UTC+8 上午1:29:52 写道: > On 17/11/2020 03:42, Andy Pan wrote: > > I thin

Re: [prometheus-users] The result of delta function is not same with raw data?

2020-11-20 Thread Brian Brazil
On Fri, 20 Nov 2020 at 02:29, Sungup Moon wrote: > Hello. > > Currently I’m making a dashboard to detect some device errors using error > counter. That error counter is a cumulative data, so I think delta() can be > a good function to detection. > Delta is for gauges, it is incorrect to use it w

[prometheus-users] Re: Keeping specific systemd name labels

2020-11-20 Thread Emre Kiratli
^((?!.*myspecificservice.*).)*$ does not work prom log : err="parsing YAML file /etc/config/prometheus.yml: error parsing regexp: invalid or unsupported Perl syntax: `(?!`" 20 Kasım 2020 Cuma tarihinde saat 13:20:18 UTC+3 itibarıyla Emre Kiratli şunları yazdı: > https://github.com/promethe

[prometheus-users] Keeping specific systemd name labels

2020-11-20 Thread Emre Kiratli
https://github.com/prometheus/prometheus/issues/3092 This is my current issue i just want to watch mysql,postgresql labels and drop the rest. Did anyone figure this out? -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from t

Re: [prometheus-users] Checkpoint FW mibs vs snmp generator

2020-11-20 Thread 'Vasilii Mazyliuk' via Prometheus Users
Actually I don't know what does it mean here by *Cannot find module*Because lines 17-23 in GaiaTrapsMIB.mib looks like this: 17 IMPORTS 18 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, enterprises 19 FROM SNMPv2-SMI 20

[prometheus-users] Re: Windows_process metrics not being exported

2020-11-20 Thread Nicholas Reid
Is there a way to troubleshoot why I'm not seeing any process metrics? The event viewer is showing that the process collector is enabled . Is there some debug logging that I can enable? On Wednesday, 18 November 2020 at 16:51:07 UTC Nicholas Reid wrote: > Hi All, > > I am using the windows_expo

Re: [prometheus-users] Checkpoint FW mibs vs snmp generator

2020-11-20 Thread Ben Kochie
Exactly as I said, you're missing MIB files for required includes *Cannot find module (SNMPv2-SMI):* At line 19 in /root/go/src/ github.com/prometheus/snmp_exporter/generator/mibs/GaiaTrapsMIB.mib *Cannot find module (SNMPv2-TC):* At line 23 in /root/go/src/ github.com/prometheus/snmp_exporter/gen

Re: [prometheus-users] Checkpoint FW mibs vs snmp generator

2020-11-20 Thread 'Vasilii Mazyliuk' via Prometheus Users
Top of the parse_errors looks like this: root@ubuntu:~/go/src/github.com/prometheus/snmp_exporter/generator# ./generator parse_errors level=info ts=2020-11-20T08:23:56.422Z caller=net_snmp.go:142 msg="Loading MIBs" from=/root/go/src/github.com/prometheus/snmp_exporter/generator/mibs level=warn