Opened 8 years ago

Closed 6 years ago

#1676 closed enhancement (worksforme)

Differentiate instances of the same components in logs

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


If multiple instances of a single component are running, it would be convenient to differentiate them in logs in case the outputs are mixed up (eg. have b10-auth-1, b10-auth-2, etc).

This might turn out to be an easy extension of #1675, when the system knows it should start n instances of single component, it could provide a different number as a command line argument to each of the instances and the component would modify its name in logs according to this.


Change History (6)

comment:1 Changed 8 years ago by shane

  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:2 Changed 8 years ago by shane

This probably depends on #1622.

comment:3 Changed 8 years ago by stephen

This may be best done by introducing another layer of logger (named after the process number) below the top-level one (e.g. instead of messages from "", they would come from something like ""). The wildcard-handling code when setting logger characteristics may need to be modified, but using another layer of logger should mean that setting characteristics for e.g. "b10-auth.*" would still affect all b10-auth components.

comment:4 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 6

comment:5 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:6 Changed 6 years ago by tomek

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

That is already done if there are multiple processes. PID is logged. Since DHCP components are not going to use multi-threading, this is sufficient for our needs.

Note: See TracTickets for help on using tickets.