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

Hipchat notification #202

Closed
valentin2105 opened this issue Aug 22, 2017 · 8 comments
Closed

Hipchat notification #202

valentin2105 opened this issue Aug 22, 2017 · 8 comments

Comments

@valentin2105
Copy link

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 :

apiVersion: monitoring.appscode.com/v1alpha1
kind: ClusterAlert
metadata:
  name: component-status
  namespace: default
spec:
  check: component_status
  checkInterval: 30s
  alertInterval: 2m
  notifierSecretName: notifier-config
  receivers:
  - notifier: hipchat
    state: CRITICAL
    to: ["#DevOps"]

(#DevOps) is my room name.
I have created the secret notifier-config with this command :

kubectl create secret generic notifier-config -n kube-system \
    --from-file=./HIPCHAT_AUTH_TOKEN

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.

@tamalsaha
Copy link
Contributor

Hi, the ClusterAlert object and notifier Secret notifier-config needs to be in the same namespace. From your description, ClusterAlert is in default namespace and notifier-config is in kube-system namespace.

@valentin2105
Copy link
Author

valentin2105 commented Aug 22, 2017

Yeah, thanks for your answer, I have created the secret in kube-systemand default and it seem to have to same behavior.

@tamalsaha
Copy link
Contributor

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?

@valentin2105
Copy link
Author

@tamalsaha Thanks for your investigations. There isn't any error on icinga containers.

@tamalsaha
Copy link
Contributor

@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.

@tamalsaha tamalsaha added the bug label Aug 23, 2017
@valentin2105
Copy link
Author

It's solved, Thanks for your reactivity,

Any way to tweak message sended to Hipchat ? via Icinga or the ressource ?

Thanks ago ! :)

@tamalsaha
Copy link
Contributor

Any way to tweak message sended to Hipchat ? via Icinga or the ressource ?

Not possible now. What do you want to see?

@valentin2105
Copy link
Author

Hum nothing specially ! I will try more and propose feature if I find good idea :)

Ty

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants