Opened 8 years ago

Last modified 3 years ago

#1055 new enhancement

Utility for logging message maintenance

Reported by: shane Owned by:
Priority: medium Milestone: Outstanding Tasks
Component: logging Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 8.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

It would be useful to have a utility to manage our logging messages. It should have the following functionality:

  • Check that any defined message is actually used somewhere
  • Check that each message used is defined (a possible problem for Python)
  • Check that message IDs are not reused

Subtickets

Change History (10)

comment:1 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 8 years ago by jelte

it should also check if the call that uses it has the correct number of arguments

comment:3 Changed 8 years ago by jinmei

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

comment:4 Changed 8 years ago by stephen

We talked about keeping a record of old messages. As part of this ticket I would propose adding tools to deal with this issue:

  • Maintenance of old messages file: a tool that given a prior release of BIND 10, lists all the messages that were in that release but are not in the current one. This could be run as part of the release process and used to update the "old messages" file. (It would be less error-prone than asking developers to maintain the old messages file as they go along.)
  • Avoid re-use of an old message ID: a tool to check that no message IDs in the current release are in the "old messages" file. This could be run as part of the main build procedure or as part of "distcheck".

comment:5 Changed 8 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 8

comment:6 Changed 8 years ago by jinmei

  • Milestone set to Next-Sprint-Proposed

comment:7 Changed 8 years ago by jreed

Also check if parameter placeholder is missing, such as fixed by commit d18c04987a47c89aa3038d2bb0e99aa40b2f4e51.

comment:8 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:9 Changed 4 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to Kea1.2

comment:10 Changed 3 years ago by tomek

  • Milestone changed from Kea1.2 to Outstanding Tasks

This ticket is not in the current scope of 1.2, so moving to Outstanding.

Note: See TracTickets for help on using tickets.