Ad Widget

Collapse

Item key parameter with right square bracket

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • glumov
    Junior Member
    • Jan 2015
    • 6

    #1

    Item key parameter with right square bracket

    Hello!
    I want to monitor traffic on windows network interface named Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC [NDIS 6.0].

    Since parameter's name contains right square bracket I quoted it.
    And key value became like this: net.if.in["Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC [NDIS 6.0]"]

    But in logs I see: item "012_server:net.if.in["Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC [NDIS 6.0]"]" became not supported: Not supported by Zabbix Agent

    What is wrong? Is it a bug?
    Last edited by glumov; 12-02-2015, 13:13. Reason: solved
  • filipp.sudanov
    Senior Member
    Zabbix Certified Specialist
    • May 2014
    • 137

    #2
    Try escaping the [ ] in a way like

    Code:
    net.if.in["Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC \[NDIS 6.0\]"]
    Does it helps?

    Comment

    • glumov
      Junior Member
      • Jan 2015
      • 6

      #3
      I've tried this too. But the result is the same:
      item "012_server:net.if.in["Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC \[NDIS 6.0\]"]" became not supported: Not supported by Zabbix Agent

      If do not quote the string, zabbix even forbids to save the item (without escaping [ ] too):
      Invalid key "net.if.in[Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC \[NDIS 6.0\]]" for item "Network Realtek (incoming traffic)" on "My Server": incorrect syntax near "]".

      Any ideas?
      Last edited by glumov; 09-02-2015, 20:58.

      Comment

      • jan.garaj
        Senior Member
        Zabbix Certified Specialist
        • Jan 2010
        • 506

        #4
        Item
        Code:
        net.if.in["Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC [NDIS 6.0]"]
        has quoted string as parameter, so only quotation mark must be escaped.
        Ref: https://www.zabbix.com/documentation...items/item/key

        There must be some reason, why is item not supported (maybe wrong name) - check it. See section "More detail than just ZBX_UNSUPPORTED":
        We already looked at one incredibly useful feature, available in 2.4 – ability to change log level while Zabbix daemons are running. Zabbix 2.4 also provides several other improvements that should help a lot with problem troubleshooting. Articles in 2.4 feature series: Part 1 – Multiple LLD filters Part 2 – Controlling redirects and header retrieval […]
        Last edited by jan.garaj; 10-02-2015, 00:48. Reason: item edited
        Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.
        My DevOps stack: Docker / Kubernetes / Mesos / ECS / Terraform / Elasticsearch / Zabbix / Grafana / Puppet / Ansible / Vagrant

        Comment

        • filipp.sudanov
          Senior Member
          Zabbix Certified Specialist
          • May 2014
          • 137

          #5
          What exactly is your Zabbix version?

          Comment

          • glumov
            Junior Member
            • Jan 2015
            • 6

            #6
            Originally posted by filipp.sudanov
            What exactly is your Zabbix version?
            Zabbix server: 2.2.8 (1:2.2.8-1+precise)
            Zabbix agent for windows: 2.2.7

            Comment

            • filipp.sudanov
              Senior Member
              Zabbix Certified Specialist
              • May 2014
              • 137

              #7
              Check the name of the network interface. Zabbix takes the data from Windows performance counters and there the network interface name differs from the one seen in control panel. E.g. on my system "Ethernet adapter Local Area Connection 3" is actually called "Intel(R) PRO/1000 MT Desktop Adapter #2"

              You can check this by running
              Code:
              typeperf -qx
              and the name seems to be the same as in "Description" field if you run
              Code:
              ipconfig -all

              Comment

              • glumov
                Junior Member
                • Jan 2015
                • 6

                #8
                Originally posted by filipp.sudanov
                You can check this by running
                Code:
                typeperf -qx
                Exactly this command I used to find out the interface's name. And it's Realtek RTL8168_8111 Family PCI-E Gigabit Ethernet NIC [NDIS 6.0]
                Output of
                Code:
                ipconfig /all
                will be later (I can not access the server right now).

                Comment

                • glumov
                  Junior Member
                  • Jan 2015
                  • 6

                  #9
                  Hello!
                  According to ipconfig interface's name is Realtek RTL8168/8111 Family PCI-E Gigabit Ethernet NIC (NDIS 6.0)
                  I changed key's value and it worked.

                  So it was bad idea to use typeperf -qx for finding out interface's name.
                  Better refer ipconfig /all , description.

                  Thanks everyone.

                  p.s. How can I change thread title to solved? I editted the first post, but the thread's title did not change.
                  Last edited by glumov; 12-02-2015, 13:15.

                  Comment

                  Working...