Skip to main content
Planned

--plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan interface filter

Related products:Infra Monitoring - Connectors
  • February 20, 2024
  • 4 replies
  • 150 views

Hi,

Could you please add interface filter to --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan.

Currently it is only possible to filter by ID, VDom and Name. 

We have devices where only MPLS is active or only Inet is active. 

For example:

checking sd-wan 'emea_hub' [vdom: root] [interface: emea-inet]

    state: up

    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s

    latency: 53.682ms

    jitter: 0.072ms

    packet loss: 0.000%

checking sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls]

    state: down

    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s

    latency: 0.000ms

    jitter: 0.000ms

    packet loss: 100.000%

 

If I filter using name as emea_hub I will get critical alert. So I need to filter by interface name.

 

bash-5.1$ /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan --hostname=1.2.3.4 --snmp-version='2c' --snmp-community='acb'  --warning-traffic-in='' --critical-traffic-in='' --warning-traffic-out='' --critical-traffic-out='' --warning-traffic-bi='' --critical-traffic-bi='' --warning-latency='' --critical-latency='' --warning-jitter='' --critical-jitter='' --warning-status='' --critical-status='%{state} eq "down"' --warning-packetloss='' --critical-packetloss=''  --verbose --filter-name=emea_hub

CRITICAL: sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls] state: down | 'root~emea_hub~emea-inet#sdwan.latency.milliseconds'=53.69ms;;;0; 'root~emea_hub~emea-inet#sdwan.jitter.milliseconds'=0.04ms;;;0; 'root~emea_hub~emea-inet#sdwan.packetloss.percentage'=0.000%;;;0;100 'root~emea_hub~emea-mpls#sdwan.latency.milliseconds'=0.00ms;;;0; 'root~emea_hub~emea-mpls#sdwan.jitter.milliseconds'=0.00ms;;;0; 'root~emea_hub~emea-mpls#sdwan.packetloss.percentage'=100.000%;;;0;100

checking sd-wan 'emea_hub' [vdom: root] [interface: emea-inet]

    state: up

    traffic traffic-in : Buffer creation, traffic-out : Buffer creation, traffic-bi : Buffer creation

    latency: 53.687ms

    jitter: 0.043ms

    packet loss: 0.000%

checking sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls]

    state: down

    traffic traffic-in : Buffer creation, traffic-out : Buffer creation, traffic-bi : Buffer creation

    latency: 0.000ms

    jitter: 0.000ms

    packet loss: 100.000%

4 replies

rchauvel
Centreonian
Forum|alt.badge.img+18
  • Centreonian
  • 1141 replies
  • February 23, 2024
NewNeeds Votes

Forum|alt.badge.img+5
  • Centreonian
  • 225 replies
  • October 16, 2025
Needs VotesPlanned

Forum|alt.badge.img+9
  • Author
  • Steward **
  • 36 replies
  • November 4, 2025

Also please fix the part in current plugin, that if the there is no matching SD-WAN entry, the plugin outputs just OK: and does not evaluate the --critical-status macro, because there is no object to evaluate it against. 

If there are no matching SD-WAN entries, the plugin simply prints OK: and exits, without running any threshold logic.

The --critical-status macro only applies if there is at least one matching SD-WAN entry.

 

So right now if the link name and ID do not match I get OK in monitoring, but I should get Critical.

(issue is that if device gets new additional SDWAN links, the LINK IDs will change, so that is why I need it to pop-up as critical)


ltirand
Centreonian
Forum|alt.badge.img+10
  • Centreonian
  • 199 replies
  • November 5, 2025

Hello ​@katska 

Indeed, this OK: empty is not desirable and should be replaced by a message such as:

UNKNOWN: Couldn't get sd-wan links with filters [...]

We will take care to add this.

However, this will have no bearing on what you enter in the status thresholds, which relate to variables and not to the success of the filters.

Kind regards.