maas.log entries should be prefixed with the service that logged them

Bug #1376944 reported by Jason Hobbs
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Medium
Unassigned

Bug Description

It's hard to tell whether a log message comes from the region controller or the cluster controller. Following syslog's lead and changing the format to something like this would be neat:

<DATE> maas-region: [WARNING] blah

Revision history for this message
Blake Rouse (blake-rouse) wrote :

I agree this would be a lot better, as people get confused on where the message is coming from.

Revision history for this message
Newell Jensen (newell-jensen) wrote :

I second this notion.

Changed in maas:
assignee: nobody → Newell Jensen (newell-jensen)
Changed in maas:
assignee: Newell Jensen (newell-jensen) → nobody
Revision history for this message
Julian Edwards (julian-edwards) wrote :

There's already provision to do this, it's just that nobody is using it. The logger name is printed in the log line and that name is controlled by what is passed to get_maas_logger(), so perhaps we can just review every occurrence of that and prefix the name with region- or cluster-

Changed in maas:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Christian Reis (kiko) wrote :

Is there no way to know that automatically?

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Hi!

We believe this is no longer an issue in the latest MAAS releases. As such, we are marking this bug report as invalid. If you believe this is still an issue, please re-open this back report.

Thanks

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.