Active items, intended to be updated with zabbix_sender only, get "Unsupported item key" treatment every RefreshActiveChecks

XMLWordPrintable

    • Type: Incident report
    • Resolution: Won't fix
    • Priority: Major
    • None
    • Affects Version/s: 2.4.3
    • Component/s: Agent (G)
    • None
    • Environment:
      Linux

      I have configured some integrations that use a zabbix_sender as a pipe to stream data to zabbix server, that data is independent of UserParameters the problem with that is that the "active checks" thread of the agent send every RefreshActiveChecks period the list of the items managed outside of the agent as:

      ...
      "value":"Unsupported item key.",
      "state":1,
      ...
      

      This makes the item become unsupported until my integrations kick-in and send a value for the marked as unsupported items. Is not a big problem, but makes the UI look like changing a lot from unsupported to supported items. Also the logs become verbose about those messages.

      I will like to be able to tell the agent to ignore those checks, the agent will get those on the list after a

      {"request":"active checks"}

      but the agent will ignore the designed ones, avoiding the become unsupported, then become supported, etc.

      Another option can be from the active item configuration, configure a yes/no parameter to avoid the sending of the item in the list of active checks, as response to the "active checks" request from the active agent.

      I know I could configure another host to serve as the bucket for all the active checks streamed from the zabbix_sender and that will solve my problem but I will get duplicated hosts, and difficulty to correlate data or treat the data as coming from the same host.

      Thanks.

            Assignee:
            Unassigned
            Reporter:
            Andres Abelardo Villarroel Acosta
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: