Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-5643

[RFE][DNS METRICS] Split CoreDNSErrorsHigh alert rule

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • openshift-4.12.z
    • Network Edge
    • None
    • False
    • None
    • False
    • Not Selected

      1. Proposed title of this feature request
      Split CoreDNSErrorsHigh alert rule by creating one alert rule for each plugin in the default root zone.

      2. What is the nature and description of the request?
      At the moment this alert rule is based on a certain percentage of SERVFAIL response code logged in the DNS pods for the entire root zone.
      Looking at the upstream documentation, it seems there is also a possibility to check for other results like plugin generating the respective response code:

      coredns_dns_responses_total

      {server, zone, view, rcode, plugin}

      - response per zone, rcode and plugin.

      Since the default root zone includes both forward and kubernetes plugins, customer would like to request that we would have 2 alert rules like for example:

      • CoreDNSErrorsHigh would gather SERVFAIL responses from the kubernetes plugin;
      • UpstreamDNSErrorsHigh would gather SERVFAIL responses from all upstream resolvers.

      3. Why does the customer need this? (List the business requirements here)
      This would help to quickly narrow down the origin of the errors and spend less time looking around within and outside of the platform what is actually occurring and where it does.
      Right now the silencer would apply to the entire alert which is not the best option because customers would miss possible important alerts on internal DNS errors.

      4. List any affected packages or components.
      CoreDNS Prometheus metrics

              mcurry@redhat.com Marc Curry
              rhn-support-andcosta Andre Costa
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: