[systemd-bugs] [Bug 89102] RFE: Support custom fields in systemd-journal-upload

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=89102

--- Comment #3 from Zbigniew Jedrzejewski-Szmek <zbyszek at in.waw.pl> ---
(In reply to Duncan Innes from comment #2)
> Could you point me to the request.  I did search for similar, but turned up
> nothing.  If there's already an RFE, I'll just track that one.
Might now have been public. Chances are that it'll get implemented in
a week or two.

> > Second, we might consider adding fields from /usr/lib/os-release
> > automatically, things like description of the OS like CPE_NAME, BUILD_ID,
> > and stuff from /etc/machine-info, DEPLOYMENT, LOCATION, CHASSIS. I can see
> > how this would be useful, but I'm not sure if it is worth the overhead.
>
> Sure - I didn't realise /etc/machine-info was able to store user data.  It's
> limited to PRETTY_HOSTNAME, ICON_NAME, CHASSIS, and DEPLOYMENT though.  I
> think it would be a big benefit to large estates to be able to specify
> custom fields as well here.  Would the overhead not be limited to reading
> this file at s-j-upload startup, then inserting the data into each exported
> entry?  A flag on s-j-upload command could indicate whether or not to add
> extra fields.  Default to NO.  User then chooses whether to increase system
> load & network traffic by adding extra data.  I might be over-simplifying
> this though.
I'm thinking of something like this in /etc/systemd/journal-upload.conf:
SendFields=DEPLOYMENT CPE_NAME CUSTOM1=value
where fields without a value specified would be extracted from machine-info
and os-release, and fields with a value would be send with the given value.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150212/affa12c1/attachment.html>