journald handler doesn't output user identity to metadata

Bug #1718935 reported by Juan Antonio Osorio Robles on 2017-09-22
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

Even though the user_identity is set in the log message, the 'project_name', 'project_id', 'user_name' and 'user_id' are not set in the journald metadata as advertised by the handler; only the request_id is set. This is a sample record output:

Fri 2017-09-22 11:26:14.506314 UTC [s=bf4abb74b860497fa733bc2e3f5b880f;i=54c5;b=dc4374ea37dd40eaa23a96568df75479;m=25e84349f;t=559c57a0abe3f;x=5a5ea4cb4ee08d03]
    MESSAGE=2017-09-22 11:26:14.505 17 INFO keystone.common.wsgi [req-c4a79e5d-b313-49d1-86c5-f716bc94a29e - - - - -] GET http://overcloud-controller-0.ctlplane.localdomain/v3/

It would be great if that data would be set in the metadata, as well as the user and project domains.

Doug Hellmann (doug-hellmann) wrote :

I'm not really familiar with journald. Are there fields built into its structure for that sort of info? Or should we add it to another field, like the message?

Fix proposed to branch: master

Changed in oslo.log:
assignee: nobody → Juan Antonio Osorio Robles (juan-osorio-robles)
status: New → In Progress

There is extra info that one can set. And actually, oslo.log's handler already has code to set that information, it's just never filled into the record.

Change abandoned by Juan Antonio Osorio Robles (<email address hidden>) on branch: master

Doug Hellmann (doug-hellmann) wrote :

I'm not sure why the patch in #4 was abandoned, but if someone else wants to pick this up I think we'd be happy to have all of the journald metadata filled in.

Changed in oslo.log:
status: In Progress → Triaged
assignee: Juan Antonio Osorio Robles (juan-osorio-robles) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers