New Metric Request: Add Net DNS Resolver Stats

Open
#246 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start at the OTEL collector integration that reads the TMOS endpoint /mgmt/tm/net/dns-resolver/stats. Compare the returned fields with the listed resolver statistics and existing TMOS GTM Cache handling, then verify that the requested resolver metrics are exposed with the expected values.

Written by the indexing model from the issue text.

Description

Some customers utilize TMOS net DNS resolvers to deliver critical services such as LTM with an explicit forward proxy configuration.

TMOS provides native statistics for these net DNS resolvers at /mgmt/tm/net/dns-resolver/stats

Some statistics for dns net resolvers that are important for my customers are:

{
"clientHits":{"value":63304},
"clientHitsPercent":{"value":66},
"clientHitsResponseTime":{"value":14},
"clientMisses":{"value":32345},
"clientMissesPercent":{"value":34},
"clientMissesResponseTime":{"value":116208},
"queries":{"value":80366},
"responses":{"value":80366},
"serveExpiredAnswers":{"value":0},
"serverErrFormerr":{"value":0},
"serverErrMemory":{"value":0},
"serverErrOther":{"value":970},
"serverErrPortV4":{"value":0},
"serverErrPortV6":{"value":0},
"serverErrRouteV4":{"value":0},
"serverErrRouteV6":{"value":424584},
"serverErrServfail":{"value":7}
}

It would be great to have these added to OTEL collector.

Note: this is not quite the same thing as TMOS GTM Cache; however, the stats output appears to be the same.

Dominant language
Python
Stars
106
Forks
43
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from f5devcentral/application-study-tool

All issues in f5devcentral/application-study-tool

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.