Using Prometheus for Network Monitoring

[Amanda M.]

With the SNMP exporter it would seem that you can use Prometheus for monitoring networks, though I'm curious as to why one would choose it over other network monitoring tools?  We haven't even been able to find a way to set multiple community strings.  Without this ability we are unable to monitor devices that we can't set the community string for without using separate instances of Prometheus for every different community string.  This seems a bit of a clunky solution.

-  Amanda

[Brian Brazil]

On 28 June 2017 at 20:57, Amanda M. <sutek...@gmail.com> wrote:

With the SNMP exporter it would seem that you can use Prometheus for monitoring networks, though I'm curious as to why one would choose it over other network monitoring tools?  We haven't even been able to find a way to set multiple community strings.  Without this ability we are unable to monitor devices that we can't set the community string for without using separate instances of Prometheus for every different community string.  This seems a bit of a clunky solution.

You can create one module in the snmp exporter for every community string you need, and then choose which module to use over in Prometheus with relabelling.

--

Brian Brazil

www.robustperception.io

[amanda.nic...@gmail.com]

I'm not quite sure as to how the relabeling works in the prometheus file?  How does relabeling in the prometheus.yml affect the snmp modules?  As well, is the default module in the snmp.yml file meant to override the other modules, as that's the behavior we're observing.

[Brian Brazil]

On 29 June 2017 at 17:01, <amanda.nic...@gmail.com> wrote:

I'm not quite sure as to how the relabeling works in the prometheus file?  How does relabeling in the prometheus.yml affect the snmp modules?  

In the simplest form, create one scrape_config per job and set the module parameter to the SNMP exporter module you wish to use.

 

As well, is the default module in the snmp.yml file meant to override the other modules, as that's the behavior we're observing.

The default module is used if you don't specify any module. Modules are independent. If you can share the relevant bit of your prometheus.yml we can see if there's something off with it.

Brian

 

On Wednesday, June 28, 2017 at 4:44:20 PM UTC-4, Brian Brazil wrote:

On 28 June 2017 at 20:57, Amanda M. <sutek...@gmail.com> wrote:

With the SNMP exporter it would seem that you can use Prometheus for monitoring networks, though I'm curious as to why one would choose it over other network monitoring tools?  We haven't even been able to find a way to set multiple community strings.  Without this ability we are unable to monitor devices that we can't set the community string for without using separate instances of Prometheus for every different community string.  This seems a bit of a clunky solution.

You can create one module in the snmp exporter for every community string you need, and then choose which module to use over in Prometheus with relabelling.

--

Brian Brazil

www.robustperception.io

--
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+unsubscribe@googlegroups.com.
To post to this group, send email to prometheus-users@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/01f322d4-4a0a-4d7c-a06a-0e5b28742474%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Brian Brazil

www.robustperception.io