action #181040
Updated by dheidler about 2 months ago
## Motivation
It would be great if we could include more context in **Failed systemd services** emails. It's already possible to find out what services were affected, but relies on the person handling the alert to disambiguate and check the time of the alert to confirm what it was about.
It would be a big improvement if all important information (which service failed on which machine with which log message) is contained within the notification email.
## Acceptance Criteria
* **AC1:** Failed systemd services emails include more detail about the error
## Suggestions
* Use deep links including the exact timestamp in alert emails e.g. https://monitor.qa.suse.de/d/KToPYLEWz/failed-systemd-services?orgId=1&from=2025-04-11T00:00:00.000Z&to=2025-04-11T23:59:59.000Z&timezone=UTC
* Include failing services in the email body
* Include output of systemctl status $service in the email body
* File an upstream feature request