Opened 7 years ago

Closed 5 years ago

#2639 closed enhancement (wontfix)

b10-msg utility for looking up message information at the command line

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

Description

Seen in a message on the bind-users list:

By the way, all of the BIND10 logging
messages are unique and we provide a paragraph or more documentation for
each of its 933 possible log identifiers!)

I haven't checked whether you have that, but that screams for a CLI
utility to show the paragraph without having to browse documentation. :)

https://lists.isc.org/pipermail/bind-users/2013-January/089541.html

So the idea would be to have a simple utility so that you could execute like this:

$ b10-msg BIND10_SELECT_ERROR
There was a fatal error in the call to select(), used to see if a child process has ended or if there is a message on the message bus. This should not happen under normal circumstances and is considered fatal, so BIND 10 will now shut down. The specific error is printed. 

We can think of possible extensions to this (like an interface which supports tab-expansion, or searches by regular expression, and so on), but I think this basic approach would cover 95% of use cases.

Subtickets

Change History (5)

comment:1 Changed 7 years ago by shane

  • Sub-Project changed from DNS to Core

comment:2 Changed 7 years ago by vorner

I think it would be more convenient to have a bash completion script, than tab interface. For that, it would need to be able to search by a prefix and list the message IDs only (without description).

Also, I guess a regexp would be an overkill. Simple * expansion could be enough.

I guess the bigger problem is loading the dictionaries. We then can just do a linear search through them if we are lazy, as there are just few thousand of them.

But yes, it is a nice idea. And we probably should make sure it can be conveniently called from a script (eg. it has a machine parseable output with some switch).

comment:3 Changed 7 years ago by shane

  • Milestone New Tasks deleted

comment:4 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:5 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

No longer applicable after bind10 framework removal.

Closing ticket.

Note: See TracTickets for help on using tickets.