-
Notifications
You must be signed in to change notification settings - Fork 31
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
[ATMOSPHERE-103] chore: Add loki rule to delect Nova cell down #495
Conversation
f3c46fc
to
147ea35
Compare
@okozachenko1203 I think the main issue here is that Loki is not integrated with the AlertManager deployed by the operator, so the alerts will be going to Can you either make a new PR or update this one to send the alerts to AlertManager (as mentioned in https://grafana.com/docs/loki/latest/alert/#scheduling-and-best-practices) Once we have that setup, then the alerts will actually "make sense" otherwise now they won't be going anywhere. |
147ea35
to
72dbfc6
Compare
Looks like a merge conflict and needs some work to pass CI |
recheck |
f961b53
to
0ab8a70
Compare
0ab8a70
to
ed3215a
Compare
ed3215a
to
ba841dc
Compare
ok, i found that ruler sidecar is not deployed in singleBInary deployment mode. |
8cc1e4e
to
3419e56
Compare
c47b0b1
to
0b8b6b4
Compare
/cherry-pick stable/2024.1 |
/cherry-pick stable/2023.2 |
/cherry-pick stable/2023.1 |
/cherry-pick stable/zed |
@mnaser: new pull request created: #1938 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@mnaser: new pull request created: #1939 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@mnaser: new pull request created: #1940 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@mnaser: #495 failed to apply on top of branch "stable/zed":
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@mnaser: new issue created for failed cherrypick: #1941 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
fix #490 Reviewed-by: Oleksandr K.
fix #490 Reviewed-by: Oleksandr K.
fix #490 Reviewed-by: Oleksandr K.
fix #490 Reviewed-by: Oleksandr K.
fix #490 Reviewed-by: Oleksandr K.
fix #490