Campfire handler

Luke_Tymowski · February 10, 2014, 2:04am

Hello,

I’m having trouble getting the Campfire handler to work.

Sensu: 0.12

Ruby: embedded

/etc/sensu/conf.d/campfire.json

{

“campfire”: {

"room": "Alerts",

"room_id" : "999999"

"account": "myaccount",

"token": "my campfire token"

}

/etc/sensu/conf.d/handler_campfire.json

{

“handlers”: {

“campfire”: {

“type”: “pipe”,

  "command": "/etc/sensu/handlers/campfire.rb"

}

In /var/log/sensu/sensu-server.log I see

{“timestamp”:“2014-02-10T01:52:51.329483+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"/etc/sensu/handlers/campfire.rb:35:in room': undefined method’ for nil:NilClass (NoMethodError)\n"}

{“timestamp”:“2014-02-10T01:52:51.329723+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"\tfrom /etc/sensu/handlers/campfire.rb:52:in `block in handle’\n"}

{“timestamp”:“2014-02-10T01:52:51.329835+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"\tfrom /opt/sensu/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout’\n"}

{“timestamp”:“2014-02-10T01:52:51.329938+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"\tfrom /opt/sensu/embedded/lib/ruby/2.0.0/timeout.rb:97:in `timeout’\n"}

{“timestamp”:“2014-02-10T01:52:51.330031+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"\tfrom /etc/sensu/handlers/campfire.rb:51:in `handle’\n"}

{“timestamp”:“2014-02-10T01:52:51.330126+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:"/etc/sensu/handlers/campfire.rb",“name”:“campfire”},“output”:"\tfrom /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-plugin-0.2.2/lib/sensu-handler.rb:41:in `block in class:Handler’\n"}

If I try /opt/sensu/embedded/bin/ruby /etc/sensu/handlers/campfire.rb I get nothing.

I’ve got the mailer.rb handler working. But after a few hours I’ve not gotten any further with campfire.

Any ideas?

thanks,

Luke

Nick_Stielau · February 10, 2014, 5:09pm

Hey Luke,

Your config looks OK to me, not sure what the issue is. You can always try piping an example JSON payload to the handler [1] (just running it directly probably won’t do much). You might try to debug the configs while your at it, i.e. ‘puts settings.inspect’ in the #room method.

Good luck!

[1] example json data passed into Sensu handlers via STDIN · GitHub

···

On Sunday, February 9, 2014 6:04:36 PM UTC-8, Luke Tymowski wrote:

Hello,

I’m having trouble getting the Campfire handler to work.

Sensu: 0.12

Ruby: embedded

/etc/sensu/conf.d/campfire.json

{

“campfire”: {

"room": "Alerts",

"room_id" : "999999"

"account": "myaccount",

"token": "my campfire token"

}

/etc/sensu/conf.d/handler_campfire.json

{

“handlers”: {

“campfire”: {

“type”: “pipe”,

  "command": "/etc/sensu/handlers/campfire.rb"

}

In /var/log/sensu/sensu-server.log I see

{“timestamp”:“2014-02-10T01:52:51.329483+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“/etc/sensu/handlers/campfire.rb:35:in room': undefined method ’ for nil:NilClass (NoMethodError)\n”}

{“timestamp”:“2014-02-10T01:52:51.329723+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“\tfrom /etc/sensu/handlers/campfire.rb:52:in `block in handle’\n”}

{“timestamp”:“2014-02-10T01:52:51.329835+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“\tfrom /opt/sensu/embedded/lib/ruby/2.0.0/timeout.rb:66:in `timeout’\n”}

{“timestamp”:“2014-02-10T01:52:51.329938+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“\tfrom /opt/sensu/embedded/lib/ruby/2.0.0/timeout.rb:97:in `timeout’\n”}

{“timestamp”:“2014-02-10T01:52:51.330031+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“\tfrom /etc/sensu/handlers/campfire.rb:51:in `handle’\n”}

{“timestamp”:“2014-02-10T01:52:51.330126+0000”,“level”:“info”,“message”:“handler output”,“handler”:{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“\tfrom /opt/sensu/embedded/lib/ruby/gems/2.0.0/gems/sensu-plugin-0.2.2/lib/sensu-handler.rb:41:in `block in class:Handler’\n”}

If I try /opt/sensu/embedded/bin/ruby /etc/sensu/handlers/campfire.rb I get nothing.

I’ve got the mailer.rb handler working. But after a few hours I’ve not gotten any further with campfire.

Any ideas?

thanks,

Luke

Luke_Tymowski · February 10, 2014, 5:16pm

Your config looks OK to me, not sure what the issue is. You can always
try piping an example JSON payload to the handler [1] (just running it
directly probably won't do much). You might try to debug the configs while
your at it, i.e. 'puts settings.inspect' in the #room method.

Actually, my problem was with my config.
/etc/sensu/conf.d/campfire.json

{

"campfire": {

"room": "Alerts",

"room_id" : "999999"

"account": "myaccount",

"token": "my campfire token"

}
}

Notice the missing comma on the room_id line.
Saw that first thing this morning but didn't/couldn't see it on the weekend.

But I now have two other problems. Sensu is posting to Campfire every 15
occurrences, but my check says to notify on every 1 occurrence. The mailer
handler is behaving as expected here. Is this a bug?

And I've got what looks like Ruby SSL errors.

{"type":"pipe","command":"/etc/sensu/handlers/*campfire*.rb","name":"
*campfire*"},"output":"/opt/sensu/embedded/lib/ruby/2.0.0/net/http.rb:918:in
`connect': SSL_connect returned=1 errno=0 state=SSLv3 read server
certificate B: certificate verify failed
(Faraday::Error::ConnectionFailed)\n"}

Fletcher talks about that problem here, I think:

gist.github.com

https://gist.github.com/fnichol/867550

README.md

# Why?

There is a long standing issue in Ruby where the *net/http* library by default does **not** check the validity of an SSL certificate during a TLS handshake. Rather than deal with the underlying problem (a missing certificate authority, a self-signed certificate, etc.) one tends to see [bad](http://stackoverflow.com/questions/1555006/how-do-i-tell-rubys-openssl-library-to-ignore-a-self-signed-certificate-error) [hacks](http://www.ruby-forum.com/topic/129530) [everywhere](http://www.peterkrantz.com/2007/open-uri-cert-verification/). This can lead to [problems](http://www.rubyinside.com/how-to-cure-nethttps-risky-default-https-behavior-4010.html) down the road.

From what I can see the OpenSSL library that [Rails Installer](http://railsinstaller.org) delivers has no certificate authorities defined. So, let's go fetch some from the [curl](http://curl.haxx.se/ca/) website. And since this is for ruby, why don't we download and install the file with a ruby script?

# Installation

## The Ruby Way! (Fun)

This file has been truncated. show original

win_fetch_cacerts.rb

require 'net/http'

# create a path to the file "C:\RailsInstaller\cacert.pem"
cacert_file = File.join(%w{c: RailsInstaller cacert.pem})

Net::HTTP.start("curl.haxx.se") do |http|
  resp = http.get("/ca/cacert.pem")
  if resp.code == "200"
    open(cacert_file, "wb") { |file| file.write(resp.body) }
    puts "\n\nA bundle of certificate authorities has been installed to"

This file has been truncated. show original

Luke

Nick_Stielau · February 10, 2014, 5:54pm

Look at the ‘refresh’ attribute. Set it equal to the interval to get alerts updates every run. The “occurences” attribute is the time to the first alert, whereas “refresh” is the time between updates (i.e. re-handling).

I made a PR to help with the debugging UX, but it really could be more helpful with JSON. I’ll take a look at that as well.

https://github.com/sensu/sensu-plugin/pull/62

···

On Mon, Feb 10, 2014 at 9:16 AM, Luke Tymowski ltymowski@gmail.com wrote:

–

Nick Stielau
206-245-7991

Your config looks OK to me, not sure what the issue is. You can always try piping an example JSON payload to the handler [1] (just running it directly probably won’t do much). You might try to debug the configs while your at it, i.e. ‘puts settings.inspect’ in the #room method.

Actually, my problem was with my config.

/etc/sensu/conf.d/campfire.json

{

“campfire”: {

“room”: “Alerts”,

“room_id” : “999999”

“account”: “myaccount”,

“token”: “my campfire token”

}

Notice the missing comma on the room_id line.

Saw that first thing this morning but didn’t/couldn’t see it on the weekend.

But I now have two other problems. Sensu is posting to Campfire every 15 occurrences, but my check says to notify on every 1 occurrence. The mailer handler is behaving as expected here. Is this a bug?

And I’ve got what looks like Ruby SSL errors.

{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“/opt/sensu/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect’: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (Faraday::Error::ConnectionFailed)\n”}

Fletcher talks about that problem here, I think:

https://gist.github.com/fnichol/867550

Luke

Nick_Stielau · February 10, 2014, 6:06pm

Here’s a pass at better JSON error messages:
https://github.com/sensu/sensu-plugin/pull/63

···

On Mon, Feb 10, 2014 at 9:54 AM, Nick Stielau nick.stielau@gmail.com wrote:

Look at the ‘refresh’ attribute. Set it equal to the interval to get alerts updates every run. The “occurences” attribute is the time to the first alert, whereas “refresh” is the time between updates (i.e. re-handling).

I made a PR to help with the debugging UX, but it really could be more helpful with JSON. I’ll take a look at that as well.

https://github.com/sensu/sensu-plugin/pull/62

–

Nick Stielau
206-245-7991

On Mon, Feb 10, 2014 at 9:16 AM, Luke Tymowski ltymowski@gmail.com wrote:

Nick Stielau
206-245-7991

–

Your config looks OK to me, not sure what the issue is. You can always try piping an example JSON payload to the handler [1] (just running it directly probably won’t do much). You might try to debug the configs while your at it, i.e. ‘puts settings.inspect’ in the #room method.

Actually, my problem was with my config.

/etc/sensu/conf.d/campfire.json

{

“campfire”: {

“room”: “Alerts”,

“room_id” : “999999”

“account”: “myaccount”,

“token”: “my campfire token”

}

Notice the missing comma on the room_id line.

Saw that first thing this morning but didn’t/couldn’t see it on the weekend.

But I now have two other problems. Sensu is posting to Campfire every 15 occurrences, but my check says to notify on every 1 occurrence. The mailer handler is behaving as expected here. Is this a bug?

And I’ve got what looks like Ruby SSL errors.

{“type”:“pipe”,“command”:“/etc/sensu/handlers/campfire.rb”,“name”:“campfire”},“output”:“/opt/sensu/embedded/lib/ruby/2.0.0/net/http.rb:918:in `connect’: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed (Faraday::Error::ConnectionFailed)\n”}

Fletcher talks about that problem here, I think:

https://gist.github.com/fnichol/867550

Luke

Topic		Replies	Views
Sensu / PagerDuty integration Sensu Classic (EOL)	1	415	March 6, 2015
Initial handler setup Sensu Classic (EOL)	3	396	November 22, 2018
Slack Handler not working Sensu Classic (EOL)	2	1148	November 22, 2018
How to configure sensu to send log to ELK host? Sensu Classic (EOL)	3	767	May 5, 2015
udp handler not working Sensu Classic (EOL)	3	421	November 22, 2018

Campfire handler

Related Topics