Ad Widget

Collapse

Cannot Add Windows Active and IIS Active Because of Overlapping Key

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • techmattr
    Member
    • Sep 2022
    • 39

    #1

    Cannot Add Windows Active and IIS Active Because of Overlapping Key

    Cannot inherit item with key "zabbix[host,active_agent,available]" of template "IIS by Zabbix agent active" to host "ServerName", because an item with the same key is already inherited from template "Windows by Zabbix agent active".

    When I try to add the IIS by Zabbix agent active to my host which already has the Windows by Zabbix agent active or if I try to add them at the same time I get the above error.

    I think it's due to both templates having the same host availability check. I tried disabling the item in the IIS template but that did not work. I tried deleting it and it says I cannot delete an inherited item.

    So how do I monitor IIS items on a Windows server?

    Ubuntu 22.04 / Zabbix 6.4.4 / Agent 2 - 6.4.4
  • Answer selected by techmattr at 31-07-2023, 17:07.
    techmattr
    Member
    • Sep 2022
    • 39

    So, I had to delete the "IIS: Active agent availability" item from the IIS by Zabbix agent active template rather than just disable it. Once I did that I was able to add it to the host. I recently upgrade from 6.2.2 to 6.4.4. This wasn't an issue in 6.2.2.

    Comment

    • SanMonitor
      Member
      • Aug 2022
      • 48

      #2
      If I understand correctly your IIS by Zabbix Agent inherits from a template with a Zabbix agent active check? (Since you get the message cannot delete an inherited item)
      Can you remove this inheritance?

      Comment

      • techmattr
        Member
        • Sep 2022
        • 39

        #3
        So, I had to delete the "IIS: Active agent availability" item from the IIS by Zabbix agent active template rather than just disable it. Once I did that I was able to add it to the host. I recently upgrade from 6.2.2 to 6.4.4. This wasn't an issue in 6.2.2.

        Comment

        Working...