Massive log spam for health checks

ExportXMLWordPrintable

    • Type: Problem report
    • Resolution: Unresolved
    • Priority: Trivial
    • 8.0.1rc1
    • Affects Version/s: 8.0.0rc1
    • Component/s: Proxy (P), Server (S)
    • None
    • S26-W40/41
    • 1

      Since Zabbix 8.0 no more legacy protocols are allowed (non-JSON data), but in Openshift / Kubernetes port checks (health checks) environments simple port check availability leads to the following warnings:

      77:20261004:080059.489 trapper got non-JSON data from "10.128.0.2" (legacy protocols are not supported)
16979:20261004:080109.489 trapper got non-JSON data from "10.128.0.2" (legacy protocols are not supported)
17075:20261004:080119.489 trapper got non-JSON data from "10.128.0.2" (legacy protocols are not supported)
17175:20261004:080129.489 trapper got non-JSON data from "10.128.0.2" (legacy protocols are not supported)
17276:20261004:080139.490 trapper got non-JSON data from "10.128.0.2" (legacy protocols are not supported)

      It would be great to check at least data length for such messages, not just "{" as first character in received data.

            Assignee:
            Vladislavs Sokurenko
            Reporter:
            Alexey Pustovalov
            Team B
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: