using IP address as the first parameter to net.if.* keys on Windows

XMLWordPrintable

    • Type: Incident report
    • Resolution: Unresolved
    • Priority: Trivial
    • None
    • Affects Version/s: 2.0.4, 2.0.5
    • Component/s: Agent (G)
    • Environment:
      agent on Win 2008

      There are random failures in the agent/server when it comes to the keys in items that will result in an items showing as "not supported" The item IS supported, because in some cases it was working previously, but in all cases it's from a template that works fine on other like servers. thus far I have seen this failure with system.cpu.util and net.if.in
      Once an item decides it is not supported, it will never work again. enabling the item does nothing as it returns to not supported on the next check. this renders zabbix completely useless to monitor that item.

            Assignee:
            Unassigned
            Reporter:
            Ebonweaver
            Votes:
            2 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: