Reviewing log sources and errors
A typical Ubuntu system contains a number of daemons and applications that will happily log to syslog or to a variety of other destinations. Some of these messages are errors that perhaps should not be showing, others may be genuine issues waiting to happen. Some more may just be totally superfluous information for the average user, and only contribute to wasting more space on disk.
We should spend a bit of time reviewing logs on one or a few representative sample(s) for the various flavors of Ubuntu we ship to find areas of improvement.
Blueprint information
- Status:
- Not started
- Approver:
- Steve Langasek
- Priority:
- Undefined
- Drafter:
- Mathieu Trudel-Lapierre
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
Blueprint: https:/
Sample log: http://
nealmcb notes:
How to put together standard ways to filter, highlight, and learn from our logs - machine learning from log files
Kibana?
a tag for logs in the default installation: "log-cleanup"?
Note and encourage apps that make it easier to get more or less logging info as needed, both log level and by subsystem
e.g. ?networkmanager features?
Should there be a way for users to turn up or down / off logging verbosity?
upstart in user session -> systemd user session --> logs to journald. ?
Bugs to open:
avahi
deja-dup
nm-applet
network-manager
gvfs
