forked from prometheus/alertmanager
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Capture and expose notification delivery errors #31
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
santihernandezc
force-pushed
the
feature/errors-in-notifications
branch
from
January 19, 2023 17:21
2b95b71
to
42cc05b
Compare
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint.
…ager into feature/errors-in-notifications
santihernandezc
force-pushed
the
feature/errors-in-notifications
branch
from
January 19, 2023 17:43
42cc05b
to
f58105d
Compare
3 tasks
grobinson-grafana
pushed a commit
that referenced
this pull request
Apr 26, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
added a commit
that referenced
this pull request
Apr 26, 2023
Capture and expose notification delivery errors (#31)
JohnnyQQQQ
pushed a commit
that referenced
this pull request
May 8, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
JohnnyQQQQ
added a commit
that referenced
this pull request
May 8, 2023
Capture and expose notification delivery errors (#31)
grobinson-grafana
pushed a commit
that referenced
this pull request
Aug 14, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Aug 14, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]> Signed-off-by: George Robinson <[email protected]>
grobinson-grafana
added a commit
that referenced
this pull request
Aug 14, 2023
…fications Capture and expose notification delivery errors (#31)
grobinson-grafana
pushed a commit
that referenced
this pull request
Aug 25, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
added a commit
that referenced
this pull request
Aug 25, 2023
Capture and expose notification delivery errors (#31)
grobinson-grafana
pushed a commit
that referenced
this pull request
Sep 11, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
added a commit
that referenced
this pull request
Sep 18, 2023
Rebased main onto "Capture and expose notification delivery errors (#31)"
alexweav
pushed a commit
that referenced
this pull request
Oct 27, 2023
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 15, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 26, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 26, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 26, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 29, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Jan 30, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Feb 8, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Feb 14, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Feb 14, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Apr 22, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Apr 22, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
grobinson-grafana
pushed a commit
that referenced
this pull request
Apr 22, 2024
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the `/api/v2/receivers` endpoint. Co-authored-by: gotjosh <[email protected]>
There is an issue with this merge:
Either the required is incorrect (can't tell) or at couple of places there is missing code. For example if active/integrations are required, AlertToOpenAPIAlert should be fixed ! @santihernandezc what do you think? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it possible to store the last error for each receiver in case of notification delivery failure. These errors are exposed via the
/api/v2/receivers
endpoint.