531c5873e7
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> |
||
|---|---|---|
| .. | ||
| v1 | ||
| v1alpha1 | ||
| v1beta1 | ||
| v1beta2 | ||
| v1beta3 | ||
| README.md | ||