failed to send alert data to VictorOps: failed to understand VictorOps response

[rj-reilly]

Here is my config.
enabled = true
api-key = "xxxxx"
routing-key = "everyone"
url = "https://alert.victorops.com/integrations/generic/20131114/alert"

global = false

[nathanielc]

@devilldog Which version are you using? There should be a more verbose error logged about how the communication with VictorOps failed.

[rj-reilly]

10.0-1

[nathanielc]

If you upgrade to v0.10.1-1 you will get a better error message and we can
debug further.

On Fri, Feb 12, 2016 at 1:44 PM, devilldog [email protected] wrote:

10.0-1

—
Reply to this email directly or view it on GitHub
#232 (comment)
.

[rj-reilly]

OK Will do thanks !

[rj-reilly]

I upgraded to 0.10.1 but i get the same message for VictorOps as before and i enabled DEBUG in the logs

[rj-reilly]

quickly looking at the code for a language i do not know, it looks like the error is not being returned and it is not actually printing out the error just the proceeding line "failed to understand response"

[rj-reilly]

any thoughts ?

[nathanielc]

@devilldog The relevant line in the code is https://github.com/influxdata/kapacitor/blob/master/services/victorops/service.go#L83
which defaults the error message to "failed to understand VictorOps response: " + string(body) where body is the raw response from VictorOps. You should see something like:

[task_name:alert5] 2016/02/17 12:26:04 E! failed to send alert data to VictorOps: failed to understand VictorOps response: RAW_RESPONSE

Can you post the logs you are seeing relating to the error?

[rj-reilly]

Yeah it is not including the actual response

[load_alert:alert2] 2016/02/14 19:22:09 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:09 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:09 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:29 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:39 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:39 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:22:59 E! failed to send alert data to VictorOps: failed to understand VictorOps response:
[load_alert:alert2] 2016/02/14 19:23:19 E! failed to send alert data to VictorOps: failed to understand VictorOps response:

[rj-reilly]

rpm -qa|grep kapac
kapacitor-0.10.1-1.x86_64

[nathanielc]

@devilldog I think I have finally reproduced the issue! VictorOps will return a 404 with no content when the API key is not valid. I have a fix coming that will print out a better error message indicating the actual error.

Can you double check your API key to make sure it is correct?

[rj-reilly]

yeah i came to the same conclusion, i will test and let you know thanks !