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

Sending alerts to HipChats result in: "failed to send alert data to HipChat: failed to understand HipChat response. code: 204 content:" #266

Closed
OrangeTux opened this issue Mar 1, 2016 · 2 comments
Milestone

Comments

@OrangeTux
Copy link
Contributor

I've set up Kapacitor so it sends alerts to HipChat. It works totally fine, but I saw these lines in the log of the Kapacitor daemon every time Kapacitor sends an alert.

[task_name:alert5] 2016/03/01 09:32:19 E! failed to send alert data to HipChat: failed to understand HipChat response. code: 204 content: 

Task info:

Name: task_name
Error: 
Type: stream
Enabled: true
Executing: true
Databases Retention Policies: ["rio"."default"]
TICKscript:
var data = stream
    .from()
        .database('rio')
        .measurement('system')
        .groupBy('project', 'host')

data.deadman(0.0, 5m)
    .message('{{ index .Tags "project" }}:{{ index .Tags "host" }} {{ if eq .Level "OK" }}is up again.{{ else }}looks down.{{ end}}')
    .stateChangesOnly()
    .hipChat()


DOT:
digraph task_name {
stream0 -> stream1 [label="8905242"];
stream1 -> noop3 [label="556494"];
stats2 -> derivative4 [label="120406"];
derivative4 -> alert5 [label="120351"];
}

Again, HipChat receives the alerts correctly, so it's not a problem to me.

@ivankennethwang
Copy link

happens to me too. 👍

@nathanielc
Copy link
Contributor

Thanks for the report, I'll get this fixed.
On Mar 9, 2016 8:46 PM, "Ivan Kenneth Wang" notifications@github.com
wrote:

happens to me too. [image: 👍]


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

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

No branches or pull requests

3 participants