notification-controller/docs/spec/v1beta3
Timur Demin 531c5873e7 Alertmanager: Change timestamp label to .StartsAt
notification-controller posted all outgoing Alertmanager alerts with
"timestamp" label, effectively preventing grouping alerts related to the
same resource and forcing users to configure a separate alert receiver
with `send_resolved: false`.

This changes it to instead set "startsAt", which was previously set
(automatically by Alertmanager) to alert posting time. "endsAt" remains
unset, as we have no way of figuring that out but the reconciliation
interval of the resource that generated the alert, which can currently
only be found out by making a Kubernetes API round-trip.

Note that this requires users to adapt alert templates that relied on
.Labels.Timestamp.

Signed-off-by: Timur Demin <me@tdem.in>
2024-04-27 16:20:12 +05:00
..
README.md Add v1beta3 spec docs 2023-11-28 16:17:03 +05:30
alerts.md Add v1beta3 spec docs 2023-11-28 16:17:03 +05:30
events.md Add v1beta3 spec docs 2023-11-28 16:17:03 +05:30
providers.md Alertmanager: Change timestamp label to .StartsAt 2024-04-27 16:20:12 +05:00

README.md

notification.toolkit.fluxcd.io/v1beta3

This is the v1beta3 API specification for defining events handling.

Specification

Go Client