Opened 7 years ago

Last modified 4 years ago

#2928 new enhancement

Include the debug log level in log messages

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

Description

Include the log level in log messages, so that an admin will know what log level to set when updating config.

This is an action item from April2013MeetingDNSWednesday20130417.

Subtickets

Change History (13)

comment:1 follow-up: Changed 7 years ago by vorner

Hm. In the descriptions, the documentation, or in the log output?

It is in the log output. I don't see how to include it in documentation witouth too much work in an automated way.

comment:2 in reply to: ↑ 1 ; follow-up: Changed 7 years ago by muks

Replying to vorner:

Hm. In the descriptions, the documentation, or in the log output?

It is in the log output. I don't see how to include it in documentation witouth too much work in an automated way.

The log level should be included in the log output, so that admins have the required info to filter it if necessary. I think Jeremy had requested this during the F2F meetings.

comment:3 in reply to: ↑ 2 Changed 7 years ago by jreed

Yes, this ticket is about log output.
But yes I do want it in the documentation, but that will be another ticket.
My goal is for the admins to know what to log, currently it is guess work, but even after this ticket, it will still be guess work because no docs to know where to start from.

comment:4 follow-up: Changed 7 years ago by vorner

But the output does contain the log level, doesn't it?:

2013-05-09 11:21:35.591 ERROR [b10-auth.auth/32476] AUTH_DATASRC_CLIENTS_BUILDER_COMMAND_ERROR command execution failure: failed to load a zone vorner.cz./IN: not configured for the class

comment:5 in reply to: ↑ 4 Changed 7 years ago by jreed

Replying to vorner:

But the output does contain the log level, doesn't it?:

2013-05-09 11:21:35.591 ERROR [b10-auth.auth/32476] AUTH_DATASRC_CLIENTS_BUILDER_COMMAND_ERROR command execution failure: failed to load a zone vorner.cz./IN: not configured for the class

It logs the severity (ERROR) and the message ID. We need it to log, when DEBUG, the debuglevel.

I don't yet have a preference on how that would be formatted.

comment:6 follow-up: Changed 7 years ago by vorner

OK, now I understand. So you want something like:

2013-05-09 11:21:35.591 DEBUG:50 [b10-auth.auth/32476] AUTH_DATASRC_CLIENTS_BUILDER_COMMAND data source builder received command: LOADZONE

comment:7 in reply to: ↑ 6 Changed 7 years ago by jreed

Replying to vorner:

OK, now I understand. So you want something like:

2013-05-09 11:21:35.591 DEBUG:50 [b10-auth.auth/32476] AUTH_DATASRC_CLIENTS_BUILDER_COMMAND data source builder received command: LOADZONE

Yes, but I don't know how that will work with syslog(3).

comment:8 Changed 7 years ago by muks

  • Estimated Difficulty changed from 0 to 3

comment:9 Changed 6 years ago by shane

  • Milestone New Tasks deleted
  • Summary changed from Include the log level in log messages to Include the debug log level in log messages

comment:10 Changed 5 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:11 Changed 4 years ago by tomek

  • Milestone changed from Remaining BIND10 tickets to Kea1.1

comment:12 Changed 4 years ago by tomek

  • Milestone changed from Kea1.1 to DHCP Outstanding Tasks

comment:13 Changed 4 years ago by tomek

  • Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks

Milestone renamed

Note: See TracTickets for help on using tickets.