SNMP exporter

[Bruce]

Hi !
I'am monitoring snmp device using prometheus snmp exporter !

I already set up a rule to authorise access between server and my host on my Fortigate 100D Firewall 
I always go no response from host while setting snmpwalk -v2c -c public ip-host 

I'am new on monitoring and system administration 
is there any other thingh to do to resolve my problem ? 

[Kiran Ali]

Did you set source ip while configuring snmp on Fortigate?

[Bruce]

Yes i did 

[Brian Candler]

It's the same question you asked on Apr 22: https://groups.google.com/d/topic/prometheus-users/KJlEfHqWSdE/discussion

If you can't get SNMP to work with a Fortigate using snmpwalk, then I'm afraid this is not an issue with Prometheus.  I suggest you either try your vendor for support, or a discussion group for Fortigate firewalls:

e.g. https://forum.fortinet.com/

[Bruce]

Well can u help with some steps to configure snmp Traps on prometheus ? 
All the services are enabled and authorised from my devices (internal network) to Prometheus (externel) !! ( One direction only)
What shall i do to monitor my devices without allowing services from Prometheus to Devices !!?
my product vendor told me that maybe i should use SNMP TRAPS !!

[Brian Candler]

Traps are logs (events), not metrics (counters/gauges).  snmp_exporter don't handle SNMP traps: https://github.com/prometheus/snmp_exporter/issues/69

You could write a custom exporter which counts SNMP traps, or you could use a trap receiver which writes logs, and a tool like mtail or grok_exporter to count particular patterns.  However, I strongly recommend you don't bother.  SNMP traps have very little useful information.

Most people configure their networks to allow SNMP polling from their monitoring station to their devices.  If you use SNMPv3 this can be done securely (with strong authentication and encryption).  If the problem is that your prometheus server is outside your firewall, and you won't configure your firewall to allow SNMP queries inbound, then the easy solution is to run another prometheus server inside your firewall.

[Ben Kochie]

You don't need the Prometheus server inside the network that has SNMP devices, only the snmp_exporter.

One simple deployment option would be to put the snmp_exporter behind the firewall with PushProx.

https://github.com/RobustPerception/PushProx

--
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/24cc43bd-036c-42ab-804e-b941aef7d99f%40googlegroups.com.

[Bruce]

And after setting another  prometheus server inside the Firewall ! 
What shall i do next ?

[Bruce]

thanks for not answeing me and giving me the half of the reponse needed :) 

[Brian Candler]

> And after setting another  prometheus server inside the Firewall ! 
> What shall i do next ?

Well obviously, you configure it with snmp_exporter to query your firewall.  But before that, check that can successfully communicate to it using snmpwalk, since if you can't do that, snmp_exporter won't be able to either.

You have posted the same thing several times, in each case showing that you are unable to talk to your firewall using snmpwalk.  You need to understand that this is not a prometheus problem - it is a problem with the configuration of your firewall or your network.

I'm sorry, but you will get no further response from me.

[Andrew Meyer]

I am curious to see how you have this setup in the prometheus.yml.  Which SNMP module are you scraping?  I can do this with the basic snmp module but if I want specifics, it won't work.

Also what did you put in the snmp generator.yml?

[khanhng...@gmail.com]

please refer this article.

https://itforvn.com/prometheus-tu-a-den-z-phan-03-giam-sat-firewall-fortigate-qua-snmp-voi-prometheus/

Vào lúc 10:12:22 UTC+7 ngày Thứ Bảy, 18 tháng 7, 2020, andre...@gmail.com đã viết: