Bug 56774 - Improve the "ugly" output of the univention-directory-logger
Improve the "ugly" output of the univention-directory-logger
Status: NEW
Product: UCS
Classification: Unclassified
Component: General
UCS 5.0
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2023-10-27 16:31 CEST by Christina Scheinig
Modified: 2024-02-12 12:55 CET (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2023100521000523
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christina Scheinig univentionstaff 2023-10-27 16:31:49 CEST
A customer wants to use the directory-logger for some kind of ldap monitoring.
He suggested to shape this "ugly" output into something more readable.

JSON would be much better for that and various log management programs(Graylog/ELK) can parse this much nicer.
Comment 1 Florian Best univentionstaff 2023-10-27 21:51:58 CEST
Binary attributes cannot be displayed in JSON, so we would need to have knowledge about the schema and transform e.g. into base64 or something else.
Comment 2 Christina Scheinig univentionstaff 2023-11-01 14:19:30 CET
As a reply, the customer said:
The whole thing has a certain structure. With some python knowledge this should be possible with jc[1], you just have to build a parser for it.
Then theoretically something like this could work:
tail -f /<LOGFILE> | jc --ldapaudit > json.output
Comment 3 Robert Heyer univentionstaff 2024-02-12 12:55:14 CET
Another customer (2149) need this machine-readable (JSON) for an external monitoring tool with a focus on evaluating revision security