Ad Widget

Collapse

Cant exclude interface (fw) from Network interface discovery

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Martin Jørgensen
    Junior Member
    • Feb 2020
    • 10

    #1

    Cant exclude interface (fw) from Network interface discovery

    HI

    I have a simple but strange problem.

    On my Linux Zabbix agent2 i have this output from zabbix_agent2 -p

    Code:
    net.if.discovery   [s|[{"{#IFNAME}":"lo"},{"{#IFNAME}":"veth104i0"},{"{#IFNAME}":"fwpr112p0"},{"{#IFNAME}":"fwpr113p0"},{"{#IFNAME}":"fwbr103i0"},{"{#IFNAME}":"fwln102i0"},{"{#IFNAME}":"fwln113i0"},{"{#IFNAME}":"vmbr0"}
    My plan is to exclude all interfaces starting with "fw"

    I have done these things

    1. Adding ^fw.* - "Result is false" to global Regular expressions, under "Network interfaces for discovery" - don't work, interfaces is still getting discovered and created on host.
    2. Adding ^fw.* to {$NET.IF.IFNAME.NOT_MATCHES} macro on template - don't work, interfaces is still getting discovered and created on host.
    3. Set ^fw.* To filters under the Network interface discovery rule - don't work, interfaces is still getting discovered and created on host.

    Every time i removed the templates from the host and run zabbix_server -R config_cache_reload, then reapplied the templates.

    Network discovery is set to 5m for testing.

    Running Zabbix server 5 and Agent is Linux Agent2

    On https://regexr.com/
    ^fw.* matches all interfaces starting with fw

    I have the same problem with Interface named tap

  • Archer
    Junior Member
    • Nov 2020
    • 1

    #2
    Click image for larger version

Name:	Screenshot from 2020-11-01 18-47-30.png
Views:	2105
Size:	64.2 KB
ID:	412049
    try to fix interfaces in macros

    Comment

    • hh_ph
      Junior Member
      • Nov 2020
      • 15

      #3
      I'm also working on this and would love a filter or regex answer
      I have attempted the above but it didn't appear to work.

      Comment

      Working...