nzin / prometheus-cachethq Goto Github PK

Every time you have a fix for an incident, it opens a new incident, rather than fixing it on the same incident thread.

Wrong way:

Right way:

Environment variable 'LABEL_NAME' is not working and it's always taking default label as 'alertname'. I verified in the Bridge container that the new environment variable is set as environment variable however it's using it.

Configuration made to overwritte the default label : changed the environment variable as mentioned below :

environment:
  - CACHETHQ_URL=http://cachet:8000
  - CACHETHQ_TOKEN=dsfasfasfasfasfasf34324
  - LOG_LEVEL=debug
  - PROMETHEUS_TOKEN=89898004e8af5ef479fe1322deb54e3f9
  - LABEL_NAME=application

Current Result : bridge is using 'alertname' label always to update the status in Cachet.
Expected Result : bridge should use 'application' label to update the status in Cachet.

$ docker exec -it 98f env
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
HOSTNAME=98feee220f9d
TERM=xterm
CACHETHQ_TOKEN=
CACHETHQ_URL=http://cachet:8000
LABEL_NAME=application
LOG_LEVEL=debug

May I kindly request you to check what's wrong here or If I have wrong interpretation about using this variable ?

Regards,
Sanjay.

Is possible to "somehow" use custom CA certificate for -cachethq_url ? I am running cachet behind https://
Thanks

I have feature request :)

I am wondering if something like -e FORCE_CREATE_COMPONENT_IN_CONSUL=true can be used for explicit component creation if not exists in Cachet.

When You have dynamic environment like K8s, its very hard to keep components 1:1 to Your services in K8s.
I know that proper way should be to register/unregister services in Consul,Etcd,etc and then dynamicaly create/delete components in Cachet, but this can be a starter point for this type of problem.

Thanks