[prometheus-users] Re: Epoch related

[BHARATH KUMAR]

Hello,

How to get the current time in epochs in the Prometheus query? 

Like can we get this info using Node Exporter metrics or any timestamp 
function we can use to get that?

Any leads?

Thanks & regards,
Bharath Kumar.

On Tuesday, 26 July 2022 at 22:00:00 UTC+5:30 BHARATH KUMAR wrote:

> Hi,
>
> I had a table with column name *last loggedin time* in grafana dashboard.
>
> This will give info regarding on particular server at what time the user 
> had accessed that server last time
>
> The Prometheus query is as below:
> (max_over_time(last_time_user_logged_in_time{instance=~"$ip"}[5m]) * 1000) 
>
> Now I need to compare during the last 24 hours, how many servers are not 
> accessed.
> at the end of the query, I want to compare some epochs so that I will give 
> output, but the epoch we need to pass is dynamic.
>
> How to do that?
>
> Any suggestions please?
>
> Thanks & regards,
> Bharath Kumar.
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/e9233a20-a966-4c82-a2e1-1b7a5a665ab4n%40googlegroups.com.

[prometheus-users] Epoch related

[BHARATH KUMAR]

Hi,

I had a table with column name *last loggedin time* in grafana dashboard.

This will give info regarding on particular server at what time the user 
had accessed that server last time

The Prometheus query is as below:
(max_over_time(last_time_user_logged_in_time{instance=~"$ip"}[5m]) * 1000) 

Now I need to compare during the last 24 hours, how many servers are not 
accessed.
at the end of the query, I want to compare some epochs so that I will give 
output, but the epoch we need to pass is dynamic.

How to do that?

Any suggestions please?

Thanks & regards,
Bharath Kumar.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/82fe5d7a-a235-4921-8eda-95071c7c5525n%40googlegroups.com.

Re: [prometheus-users] Prom QL

[BHARATH KUMAR]

Thanks Sir

On Monday, 25 July 2022 at 12:26:43 UTC+5:30 Stuart Clark wrote:

> On 25/07/2022 07:30, BHARATH KUMAR wrote:
> > I am talking about grafana dashboard. I created a custom variable as 
> > follows:
> >
> > CPU:
> > All : <=100,
> > lt 10 && gt 0 : >0<=10,
> > lt 30 && gt 10 : >10<=30
> >
> > So this CPU filter will be added at the top of grafana dashboard. Now 
> > If I select ALL in CPU filter I am not able to find the unreachable 
> > servers list in the grafana dashboard as those servers are not present 
> > in prometheus Data Source(since these are in unreachable state).
> >
> > My query:
> > 
> ((1 - avg(irate(node_cpu_seconds_total{mode="idle",instance=~"$ip"}[5m])) by 
> (instance)) * 100) 
>
> > $CPU
> >
> > Here we are comparing the value in $cpu
> >
> > Is there any other way to compare the values that are not present in 
> > prometheus data source so that when I click ALL option I can able to 
> > see all servers data.
>
> If you are not scraping something (because the scrape is failing) then 
> no data exists about that server.
>
> For the drop down selector in Grafana you could use the "up" metric, 
> which will still have values for servers that weren't able to be 
> scraped, but selecting one of those would then result in an empty 
> dashboard as there wouldn't be any CPU values.
>
> -- 
> Stuart Clark
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/3a2e28b6-800a-4586-9822-323d874d385fn%40googlegroups.com.

Re: [prometheus-users] Re: Does prometheus SNMP exporter supports v3?

[Michael Kogelman]

Also, if it doesn’t seem to be working be sure you’re not using AES256 on a 
Cisco product. NetSNMP does not support this — it’s just Cisco doing their own 
thing.

Get Outlook for iOS

From: prometheus-users@googlegroups.com  on 
behalf of Brian Candler 
Sent: Tuesday, July 26, 2022 3:21:39 AM
To: Prometheus Users 
Subject: [prometheus-users] Re: Does prometheus SNMP exporter supports v3?

if_mib: &if_mib
  ...

if_mib3:
  <<: *if_mib
  version: 3
  auth:
security_level: authPriv
auth_protocol: SHA
username: bla
password: blabla
priv_protocol: AES
priv_password: blablabla

On Tuesday, 26 July 2022 at 08:06:48 UTC+1 shelt...@gmail.com wrote:
Just want to crosscheck snmp exporter supports SNMPv3, if yes can someone share 
the sample config, i want to deploy SNMP exporter on kubernetes.

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/34a2eb08-f56b-4b14-a3d6-45eb9ff44b2dn%40googlegroups.com.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/DM5PR07MB41337A9794C291D676DC2448F1949%40DM5PR07MB4133.namprd07.prod.outlook.com.

Re: [prometheus-users] Re: blackbox metrics scraping

[nina guo]

Hi Stuart, Brian

I checked the blackbox exporter logs as below for module check_smtp, seems 
only every 30 secs, the next probe started. But actually I set the 
scrape_interval for this job is 60s..


07:54:34  Beginning probe
07:55:05  Beginning probe
07:55:34  Beginning probe
07:56:05  Beginning probe
07:56:34  Beginning probe
07:57:05  Beginning probe
07:57:34  Beginning probe

kubectl logs prometheus-blackbox-exporter -c blackbox-exporter -n 
monitoring  | findstr "1.1.1.1:25"

ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Beginning probe" probe=tcp 
timeout_seconds=9.5
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolving target address" ip_protocol=ip6
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolving target address" ip_protocol=ip4
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolved target address" ip=1.1.1.1
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Dialing TCP without TLS"
ts=2022-07-26T07:54:34.873Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Successfully dialed"
ts=2022-07-26T07:54:34.873Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=0
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="220"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp="^220 ([^ ]+) 
ESMTP( .+)?$" line="220 ESMTP"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="EHLO prober\r"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=1
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-PIPELINING
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250-SIZE 1024"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-ETRN
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-STARTTLS
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp=^250-STARTTLS 
line=250-STARTTLS
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=2
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250-AUTH PLAIN LOGIN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-ENHANCEDSTATUSCODES
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-8BITMIME
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250 DSN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp="^250 .*$" 
line="250 DSN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="STARTTLS\r"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=3
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="220 2.0.0 Ready to 
start TLS"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp=^220 line="220 
2.0.0 Ready to start TLS"
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="TLS Handshake (client) succeeded."
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=4
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="EHLO prober\r"

Re: [prometheus-users] Re: blackbox metrics scraping

[nina guo]

Hi Stuart, Brian

I checked the blackbox exporter logs as below for module check_smtp, seems 
only every 30 secs, the next probe started. But actually I set the 
scrape_interval for this job is 60s..


07:54:34  Beginning probe
07:55:05  Beginning probe
07:55:34  Beginning probe
07:56:05  Beginning probe
07:56:34  Beginning probe
07:57:05  Beginning probe
07:57:34  Beginning probe

kubectl logs prometheus-blackbox-exporter -c blackbox-exporter -n 
monitoring  | findstr "1.1.1.1:25"

ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Beginning probe" probe=tcp 
timeout_seconds=9.5
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolving target address" ip_protocol=ip6
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolving target address" ip_protocol=ip4
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Resolved target address" 
ip=100.70.222.244
ts=2022-07-26T07:54:34.872Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Dialing TCP without TLS"
ts=2022-07-26T07:54:34.873Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Successfully dialed"
ts=2022-07-26T07:54:34.873Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=0
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="220"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp="^220 ([^ ]+) 
ESMTP( .+)?$" line="220 ESMTP"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="EHLO prober\r"
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=1
ts=2022-07-26T07:54:34.874Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-PIPELINING
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250-SIZE 1024"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-ETRN
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-STARTTLS
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp=^250-STARTTLS 
line=250-STARTTLS
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=2
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250-AUTH PLAIN LOGIN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-ENHANCEDSTATUSCODES
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line=250-8BITMIME
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="250 DSN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp="^250 .*$" 
line="250 DSN"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="STARTTLS\r"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=3
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Read line" line="220 2.0.0 Ready to 
start TLS"
ts=2022-07-26T07:54:34.875Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Regexp matched" regexp=^220 line="220 
2.0.0 Ready to start TLS"
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="TLS Handshake (client) succeeded."
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Processing query response entry" 
entry_number=4
ts=2022-07-26T07:54:34.882Z caller=main.go:180 module=smtp_starttls_server 
target=1.1.1.1:25 level=debug msg="Sending line" line="EHLO pr

[prometheus-users] Re: Does prometheus SNMP exporter supports v3?

[Brian Candler]

if_mib: &if_mib
  ...

if_mib3:
  <<: *if_mib
  version: 3
  auth:
security_level: authPriv
auth_protocol: SHA
username: bla
password: blabla
priv_protocol: AES
priv_password: blablabla

On Tuesday, 26 July 2022 at 08:06:48 UTC+1 shelt...@gmail.com wrote:

> Just want to crosscheck snmp exporter supports SNMPv3, if yes can someone 
> share the sample config, i want to deploy SNMP exporter on kubernetes. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/34a2eb08-f56b-4b14-a3d6-45eb9ff44b2dn%40googlegroups.com.

Re: [prometheus-users] Does prometheus SNMP exporter supports v3?

[Julien Pivotto]

While I don't have specific config to share with you, snmp exporter works
with snmp V3.

Le mar. 26 juil. 2022, 09:06, Shelten  a écrit :

> Just want to crosscheck snmp exporter supports SNMPv3, if yes can someone
> share the sample config, i want to deploy SNMP exporter on kubernetes.
>
> --
> 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 view this discussion on the web visit
> https://groups.google.com/d/msgid/prometheus-users/1687e818-4f76-42fd-b2ce-6eece7bc640bn%40googlegroups.com
> 
> .
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/CAFJ6V0pfWRYRu%3DJ05i0FuAewXf%2Br9JK0oTRDSuDZJ%2BA--VwH8A%40mail.gmail.com.

[prometheus-users] Does prometheus SNMP exporter supports v3?

[Shelten]

Just want to crosscheck snmp exporter supports SNMPv3, if yes can someone 
share the sample config, i want to deploy SNMP exporter on kubernetes. 

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/1687e818-4f76-42fd-b2ce-6eece7bc640bn%40googlegroups.com.