Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • stork stork
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 307
    • Issues 307
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 24
    • Merge requests 24
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • storkstork
  • Issues
  • #63
Closed
Open
Issue created Oct 24, 2019 by Vicky Risk@vickyDeveloper

Req 6.1 - Query Details

As a user I would like to monitor the volume of queries and responses. This should be fairly prominent.This is a baseline function that everyone needs. These statistics should be available on a per-server basis from BIND today.

In addition, I would like to be able to see in a detail view the distribution of rrtypes, response codes, query levels by TCP vs UDP, perhaps by some response size buckets.

Some of the details are not that interesting, unless you are investigating a specific problem (such as with TCP connections). Many of the response codes and rrtypes will be used infrequently and charts will have a lot of empty bars or columns and a few big ones.

Include queries that are dropped, if possible, perhaps in a display by response code?

It could be useful to see these displayed both per-server and aggregated across clusters of servers (for when you are investigating a possible pattern of abuse queries for example).

Assignee
Assign to
Time tracking