Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • BIND BIND
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 524
    • Issues 524
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 101
    • Merge requests 101
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source Projects
  • BINDBIND
  • Issues
  • #513

Closed
Open
Created Aug 30, 2018 by Sara Dickisnon@sara.dickinson

New metrics to report DNSSEC signing operations and IXFRs [ISC-support #13431]

Description

For large DNSSEC signed zones with frequent updates there are many signing operations happening both due to the updates and part of routing re-signing. If the zone has a secondary configured there are also frequent IXFRs, some of which can be very big. It would be helpful to have metrics to report and monitor this activity on the master.

Versions

9.14.X, 9.15.X

Request

The main request is to add the following metrics to the statistics:

  1. Total number of signing operations
  2. Number of maintenance signing operations (i.e. signature refresh/update)

It would be helpful to also give the key id used for signing.

Two further requests that would help with monitoring of outgoing IXFRs on busy masters (particularly when the secondary is operated by a different organisation):

  1. Add metrics on the size of the IXFRs e.g. min, max and average size of IXFRs
  2. Add the same details to the XFR log on the master that are reported on the secondary: transfer of 'example.com/IN' from 127.0.0.1#7753: Transfer completed: 1 messages, 14 records, 986 bytes, 0.001 secs (986000 bytes/sec). The log on the master currently only reports that the transfer started and ended.

Links / references

Edited Jun 25, 2019 by Matthijs Mekking
Assignee
Assign to
Time tracking