Re: [prometheus-users] prometheus federate transfter alerts stopped to main prometheus

[Stuart Clark]

On 22/11/2022 05:53, Prashant Singh wrote:

Dear All,

I am using federate prometheus and configured to central prometheus . 
but getting alerts from federate prometheus also . how can avoids 
alerts from federate.



  - job_name: 'K8S-Federate'
    #scrape_interval: 15s
    honor_labels: true
    metrics_path: '/federate'
    scheme      : http

    params:
      'match[]':
       - '{job!=""}'

The alert rules are set in each Prometheus, so if you are not wanting 
them you'd need to look at the configuration and change/remove.


--
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/da2abd71-8606-7e34-f566-c37313fa8b91%40Jahingo.com.

[prometheus-users] prometheus federate transfter alerts stopped to main prometheus

[Prashant Singh]

Dear All,

I am using federate prometheus and configured to central prometheus . but 
getting alerts from federate prometheus also . how can avoids alerts 
from federate.


  - job_name: 'K8S-Federate'
#scrape_interval: 15s
honor_labels: true
metrics_path: '/federate'
scheme  : http

params:
  'match[]':
   - '{job!=""}'


thanks,
prashant 

-- 
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/16ec6a85-f9e7-4e93-9753-96a50ae7e70fn%40googlegroups.com.

Re: [prometheus-users] Troubleshoot Suggestions

[Brian Candler]

> My issue is I don't get a webpage when I try to access the server

What do you get instead - an error response (if so, what error)? A timeout?

You can check whether the packets are arriving on your prometheus server:

tcpdump -i eth0 -nn -s0 -X tcp port 9090

Replace eth0 with your primary interface name if it's different. (ip addr 
list)

On Monday, 21 November 2022 at 06:13:43 UTC sup...@gmail.com wrote:

> PROTO=2 is IGMP, which has nothing to do with the TCP connection required 
> for Prometheus.
>
> Sounds like you have a typo in your UFW rules.
>
> On Mon, Nov 21, 2022 at 7:05 AM Mitchell Tuckness  
> wrote:
>
>> Hi All,
>>
>> I just put Prometheus on a virtual machine following this guide 
>> .
>>  
>> The service is running; I don't see any errors in my Syslog that I can pin 
>> directly to Prometheus. I was hoping I could get advice on where to look; 
>> what might be wrong? I am leaning toward the config file, but as far as I 
>> can tell, it should be OK for just this basic setup.
>>
>> My issue is I don't get a webpage when I try to access the server. UFW is 
>> allowing that port. Prometheus service is running. 
>>
>> The only thing I see that is odd in the Syslog is:
>>
>> Nov 15 16:17:01 prometheus CRON[1131]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Nov 15 17:00:27 prometheus prometheus[770]: ts=2022-11-15T17:00:27.963Z 
>> caller=compact.go:519 level=info component=tsdb
>> msg="write block" mint=1668520812852 maxt=166852800 
>> ulid=01GHY3R9TKDCF0H656G28KP10J duration=103.526641ms
>> Nov 15 17:00:27 prometheus prometheus[770]: ts=2022-11-15T17:00:27.966Z 
>> caller=head.go:1213 level=info component=tsdb ms
>> g="Head GC completed" caller=truncateMemory duration=2.790302ms
>>
>>
>>
>>
>> *Nov 15 17:03:38 prometheus kernel: [13219.657945] [UFW BLOCK] IN=enp0s3 
>> OUT= MAC=01:00:5e:00:00:01:40:f5:20:0c:4b:f3:08:00 SRC=192.168.1.7 
>> DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4 PROTO=2Nov 15 17:03:38 
>> prometheus kernel: [13219.658284] [UFW BLOCK] IN=enp0s3 OUT= 
>> MAC=01:00:5e:00:00:01:40:f5:20:0c:4b:f3:08:00 SRC=192.168.1.7 DST=224.0.0.1 
>> LEN=32 TOS=0x00 PREC=0x00 TTL=1 ID=4 PROTO=2*Nov 15 17:17:01 prometheus 
>> CRON[1145]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
>> Nov 15 18:17:01 prometheus CRON[1157]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>>
>> -- 
>> 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-use...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/prometheus-users/8ce61c16-3dae-4ddc-a0dc-50cb8416faffn%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/2090410d-14fa-42d9-8195-9107e0da011cn%40googlegroups.com.

[prometheus-users] Re: SNMP Exporter showing UNKNOWN module

[Brian Candler]

The error is right there:
Unknown module "router"

Almost certainly you are running snmp_exporter to load a different config 
file than the SNMP.yml you've shown.

On Monday, 21 November 2022 at 06:06:33 UTC pleasan...@gmail.com wrote:

> HI all,
>
> Appreciate if anyone can help or leave an input. As per title my SNMP 
> exporter state is DOWN and when clicked it is showing unknown with error 
> "server 
> returned HTTP status 400 Bad Request". 
>
> I tried to capture snmp to my router (target 192.168.1.253) for testing 
> but it seems not working.
>
> Below is my SNMP yml :-
>
> router:
>   version: 2
>   auth:
> community: onecommunity
>
>
>   walk:
>   - 1.3.6.1.2.1.1.3 # sysUpTime
>   - 1.3.6.1.2.1.31.1 # ifHCInOctets
>   - 1.3.6.1.2.1.2.2.1.10 # ifInOctets
>   - 1.3.6.1.2.1.2.2.1.16
>   - 1.3.6.1.2.1.31.1.1.1
>
>   metrics:
>   - name: ifHCInOctets
> oid: 1.3.6.1.2.1.31.1.1.1.6
> type: counter
> indexes:
> - labelname: interface
>   type: gauge
> lookups:
>   - labels: [interface]
> oid: 1.3.6.1.2.1.2.2.1.2
> labelname: DisplayString
>   - labels: [interface]
> oid: 1.3.6.1.2.1.31.1.1.1.18
> labelname: alias
>
> Below is my prometheus yml:-
>
>   - job_name: routersnmp
> metrics_path: /snmp
> params:
>   module: [router]
> static_configs:
>   - targets:
> - 192.168.1.253
> relabel_configs:
>   - source_labels: [__address__]
> target_label: __param_target
>   - source_labels: [__param_target]
> target_label: instance
>   - target_label: __address__
> replacement: 192.168.1.181:9116  # URL as shown on the UI
>
>
> Below is the screenshot:-
> [image: snmpexporter1.png][image: snmpexporter2.png]
>
>

-- 
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/05e51ace-93d7-4234-acda-564d3f4304f1n%40googlegroups.com.

Re: [prometheus-users] Prometheus Growth

[Stuart Clark]

On 20/11/2022 22:53, Julio Leal wrote:

Hi everyone!
I'm doing a study about how much time we have in our prometheus instances.
First of all, I thought that prometheus memory grew because number 
timeseries ingested. I thought like this because timeseries stay in 
memory to recover informations more faster.
But I got timeseries from last 3 months and I found that my timeseries 
ingested was grew little, like this graph and in the same time, I 
needed to increase the memory ram and CPU of the our instances sometimes.


There was an interesting talk at the recent PromCon EU 
(https://promcon.io/2022-munich/talks/why-is-it-so-big-analysing-the-m/) 
which is available on YouTube, but basically the main memory usage is 
generally due to the number of time series, with only a very minor usage 
due to queries.


--
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/1ec0a449-2a46-3c3d-31aa-79c0e0280bd3%40Jahingo.com.

Re: [prometheus-users] Modify the check interval of blackbox exporter HTTP probe

[Stuart Clark]

On 18/11/2022 19:09, Lunar Angelo Pajaroja wrote:
Hi is it possible to modify the check interval of HTTP probe. Example 
I just want blackbox (http module) to check "http://example-endpoint; 
just every one minute.
Just change the scrape interval of the job that is checking that 
endpoint with the Blackbox Exporter.


--
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/4739bb6f-de84-b3ad-59eb-ea35d51b739a%40Jahingo.com.