snapd should log fully to the journal
Bug #1796987 reported by
Dan Watkins
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| snapd |
Triaged
|
Medium
|
Unassigned | ||
| snapd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Currently, one has to run (multiple) snap commands to get the "logs" of what snapd has done on a system. This is not only annoying (because the commands one has to run are dynamic based on change IDs, so it requires scripting), but also means that normal methods of collating logging information from Ubuntu systems (whether that be grabbing files from a disk or pushing to a central logging service) fail to capture what snapd was doing to a system.
To solve this, I think it would be appropriate for snapd to log the human-readable text that `snap change <id>` shows you to the systemd journal.
Revision history for this message
| Dan Watkins (oddbloke) wrote | #1 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in snapd (Ubuntu): | |
| status: | New → Confirmed |
| Changed in snapd: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Paweł Stołowski (stolowski) wrote | #3 |
To post a comment you must log in.
Further to this, I believe snapd drops its record of old changes at some point, with no way of understanding what happened before its oldest recorded change. If these changes were logged, regular log rotation/retention would retain this information.