Replies: 1 comment 1 reply
-
are you able to curl the endpoint locally from the pfsense (curl localhost:9116) ? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My pfsense server is acting as a gateway between my AWS account and another AWS account and I'd like to scrape metrics of the different interfaces that I want to monitor. Was trying to follow this guide and got about 99% of it completed except there's probably a misconfig somewhere in my process to be able to run snmp_exporter. Both servers are on the same VPC.
Host operating system:
prometheus EC2 - ubuntu 22.04
pfsense EC2 - ubuntu 22.04
snmp_exporter version: output of
snmp_exporter -version
v0.18.0
What did you do that produced an error?
curl http://<interface-ip>:9116/snmp?module=pfsense\&target=<interface-ip>
curl: (28) Failed to connect to <interface-ip> port 9116 after 134523 ms: Connection timed out
What did you expect to see?
interface metrics flowing into snmp_exporter and querying with PromQL
What did you see instead?
prometheus and pfsense are both privately hosted. Able to ping the pfsense server from prometheus. Able to run
snmpwalk -v 1 -c <my-secure-string> <interface-ip>
and get metrics immediately. Able to generate a new snmp.yml through the generator util and adding in the MIB files from the pfsense box.snmp_exporter is running as a daemon service on prometheus and looks like:
snmp.yaml looks like this with the walk OIDs and metrics metadata generated successfully:
prometheus.yml file pfsense section looks like this:
prometheus UI looks like this - what am i missing??
pfsense firewall page looks like this - using 'Any' as the source to validate before I slim it down:
Beta Was this translation helpful? Give feedback.
All reactions