-
Notifications
You must be signed in to change notification settings - Fork 10
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
Asset doesn't downloads from bonsai #13
Comments
This issue is blocked waiting on more information. The description or subsequent comments do not provide enough information to triage, investigate or resolve the issue. Please review the description against the issue template and ensure all relevant information is included. If you do not know what is expected you can ask on Gitter chat. |
i took information from here https://bonsai.sensu.io/assets/alerta/sensu-alerta-handler i filled up asset file like this:
And setup handler:
Afterwards i recieve log error decribed in topic |
Did you download and install the handler?
|
nope, as i didnt for sensu-slack-sender for example, i thought it is gonna fetch it automatically |
What version of Sensu are you running? |
alerta 7.4.0
Now, i built it and put to container, and get another
```
error {"assets":null,"component":"pipelined","handler":"alerta","level":"info","msg":"event pipe handler executed","namespace":"default","output":"Error: Alerta answered with non 2XX code: 405 !\n\u0026{Status:405 Not Allowed StatusCode:405 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Content-Type:[text/html] Content-Length:[173] Connection:[keep-alive] Server:[nginx/1.10.3] Date:[Thu, 19 Sep 2019 12:31:31 GMT]] Body:0xc0001c8680 ContentLength:173 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc00015ea00 TLS:\u003cnil\u003e}\nUsage:\n sensu-alerta-handler [flags]\n\nFlags:\n -e, --endpoint string The http endpoint of alerta (default \"http://172.17.0.1:8090/alert\")\n -E, --environment string Alerta environment (Development, Production\n -h, --help help for sensu-alerta-handler\n -k, --key string Alerta http auth key\n -t, --timeout int The amount of seconds to wait before terminating the handler (default 10)\n\n2019/09/19 15:31:31 Alerta answered with non 2XX code: 405 !\n\u0026{Status:405 Not Allowed StatusCode:405 Proto:HTTP/1.1 ProtoMajor:1 ProtoMinor:1 Header:map[Content-Type:[text/html] Content-Length:[173] Connection:[keep-alive] Server:[nginx/1.10.3] Date:[Thu, 19 Sep 2019 12:31:31 GMT]] Body:0xc0001c8680 ContentLength:173 TransferEncoding:[] Close:false Uncompressed:false Trailer:map[] Request:0xc00015ea00 TLS:\u003cnil\u003e}\n","status":1,"time":"2019-09-19T15:31:31+03:00"}
```
|
man, im using slack sender through assets, and it fetches tar.gz automatically and uses it
|
What version of Sensu??? |
sensu-go-backend 5.13.1-5957
|
What commands did you run? The README for slack suggests it still needs to be installed once downloaded... https://github.com/sensu/sensu-slack-handler |
in official guide of sensu there is nothing about manual building of binary's. just put asset and define handler, and it fetches itself |
What guide? Where? Please show me a link so I can check that. |
https://docs.sensu.io/sensu-go/5.12/guides/send-slack-alerts/ here says define asset, register it, create handler, assign asset to handler, done
19.09.2019, 15:54, "Nick Satterly" <notifications@github.com>:What guide? Where? Please show me a link so I can check that.—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
|
They skipped a step. If you look at the slack README and the alerta README they both clearly state...
|
alright, building binary than ... how about usage? do you have any full example ?
|
I've just updated the README. Let me know if that works for you. |
[POLICY] Alert environment does not match one of Production i think there is also needs an env_vars for environment |
So what is the environment that is being sent? It comes from |
i use namespace Default in sensuhow to set it up manually during handler execution ?
|
If your namespace is "Default" then add "Default" to the list of allowed environments in Alerta. See https://docs.alerta.io/en/latest/configuration.html#plugin-settings Allowing environment to be overridden in the handler config is possible. What if Sensu monitors more than one environment though? eg. Production, Staging, Test and Development etc. |
changing namespace in sensu worked |
Can't use use namespace for the environment? Or do you want to be able to define an alerta handler for each environment? "production", "development" etc? |
It's been updated to support
|
Fantastic, thanks for support |
{"assets":null,"component":"pipelined","handler":"alerta","level":"info","msg":"event pipe handler executed","namespace":"default","output":"sh: 1: sensu-alerta-handler: not found\n","status":127,"time":"2019-09-19T12:50:33+03:00"}
The text was updated successfully, but these errors were encountered: