-
Notifications
You must be signed in to change notification settings - Fork 24
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
Hipchat notification #202
Comments
Hi, the |
Yeah, thanks for your answer, I have created the secret in |
Let me replicate the issue at my end and get back to you. If you check the logs for icinga container, do you see any error? |
@tamalsaha Thanks for your investigations. There isn't any error on icinga containers. |
@valentin2105 , we have pushed a new fix 3.0.1 to address this issue. https://github.com/appscode/searchlight/releases/tag/3.0.1 . Please upgrade the image tags for operator container to appscode/searchlight:3.0.1 and icinga container to appscode/icinga:3.0.1-k8s . Let me know how it goes. |
It's solved, Thanks for your reactivity, Any way to tweak message sended to Hipchat ? via Icinga or the ressource ? Thanks ago ! :) |
Not possible now. What do you want to see? |
Hum nothing specially ! I will try more and propose feature if I find good idea :) Ty |
Hi !
First, thanks for Searchlight, it the kind of tool that I missed in my cluster.
I try to enable Hipchat notifications but I can't make it work,
here is my
ClusterAlert.yaml
:(#DevOps) is my room name.
I have created the secret
notifier-config
with this command :The file HIPCHAT_AUTH_TOKEN contain the token (write with echo -n).
It's a room token, not a Global token. (I tried both).
When I stop
kube-controller-manager
for example, Icinga detect it quickly, got a CRITICAL alert, but not any Hipchat message anywhere. (and no logs at all.)Thanks for your help.
The text was updated successfully, but these errors were encountered: