Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add timestamp as label for alertmanager #298

Merged
merged 1 commit into from
Jan 11, 2022

Conversation

Alan01252
Copy link
Contributor

Without the timestamp there is not enough entropy in the hash for
alertmanager to recongise that this is a new alert for some cases.

Adding the timestamp ensures that a new hash for the alert is created
each time and therefore no updates get missed.

Without the timestamp there is not enough entropy in the hash for
alertmanager to recongise that this is a new alert for some cases.

Adding the timestamp ensures that a new hash for the alert is created
each time and therefore no updates get missed.

Signed-off-by: Alan Hollis <[email protected]>
@Alan01252 Alan01252 force-pushed the feature/alertmanager branch from 0c1e0cb to 5a21f69 Compare January 5, 2022 09:46
@Alan01252
Copy link
Contributor Author

This allows the alertmanager administrator to determine how to group alerts.

As an example if you choose not to group by timestamp you can send alerts to slack which look like.

image

However if you want to then group by timestamp and get all the alerts

image

Copy link
Member

@stefanprodan stefanprodan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Thanks @Alan01252 🏅

@stefanprodan stefanprodan added the area/alerting Alerting related issues and PRs label Jan 11, 2022
@stefanprodan stefanprodan merged commit 1035a1f into fluxcd:main Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/alerting Alerting related issues and PRs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants