Uploaded image for project: 'ZABBIX FEATURE REQUESTS'
  1. ZABBIX FEATURE REQUESTS
  2. ZBXNEXT-8372

Add common services, E.g. DNS to net.udp.service and net.udp.service.perf

XMLWordPrintable

    • Icon: Change Request Change Request
    • Resolution: Unresolved
    • Icon: Trivial Trivial
    • None
    • None
    • None
    • None

      Reopening as the original request (ZBXNEXT-8003) was not understood. **

      Add common services, E.g. DNS to net.udp.service and net.udp.service.perf

      Currently documentation only shows NTP available.

      We want general UDP monitoring and to see if ports return traffic and what the response time was.

      It's definitely not impossible. Just because a protocol doesn't guarantee delivery doesn't mean you can't measure if it did and how long it took. But it's fine, I'll script it myself . I appreciate your consideration either way.

      I feel like you might have misunderstood the request as it's not to get the listen status, it's to get performance or a return. I can re-file this.

      To those interested in this, on Linux you could easily do this via a script that does the following:

      Perform a dig or nslookup against a specific server

      Use the linux time function to run dig/nslookup

      Check if you got a valid response.

      Feed zabbix the time result or delivery ok status.

            Unassigned Unassigned
            dpcahill David Cahill
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: