Pre-req reading:
Nagios customization: Alerting via SMS, or anything you like!
Making the bird tweet using python
or
Update twitter in a single line
This entry will cover how to send nagios alerts to twitter, in the examples to follow curl will be used however you can choose to use the python example (link above) in place of this.
Firstly edit /usr/local/nagios/etc/objects/commands.cfg
And add the two following commands.
UPDATE 24/03/2011 Twitter no longer supports basic auth, use my oAuth updater here
1 2 3 4 5 6 7 8 9
| define command {
command_name notify-by-twitter
command_line /usr/bin/curl --basic --user "twitteruser:twitterpassword" --data-ascii "status=[Nagios] $NOTIFICATIONTYPE$ $HOSTALIAS$/$SERVICEDESC$ is $SERVICESTATE$" http://twitter.com/statuses/update.json
}
define command {
command_name host-notify-by-twitter
command_line /usr/bin/curl --basic --user "twitteruser:twitterpassword" --data-ascii "status=[Nagios] $HOSTSTATE$ alert for $HOSTNAME$" http://twitter.com/statuses/update.json
} |
Now define a contact for this twitter service
/usr/local/nagios/etc/objects/contacts.cfg
1 2 3 4 5 6 7 8 9
| define contact{
contact_name twitter
service_notification_commands notify-by-twitter
host_notification_commands host-notify-by-twitter
service_notification_period 24x7
host_notification_period 24x7
service_notification_options a
host_notification_options a
} |
Choose your own notification options, for my feed I only choose alerts, I also have this send updated to a ‘private feed’ which I then follow.
Add this contact into your existing contact groups, i.e.
1 2 3 4 5
| define contactgroup{
contactgroup_name admins
alias Nagios Administrators
members nagiosadmin,sms_alert,twitter
} |
Then run a nagios-verify to ensure you have no syntax errors, and restart nagios.
Trigger an alert by manually switching a monitored service off or entering a manual result to test.
Tags:
alert,
Nagios,
sms,
text,
twitter
4 Comments »
Some two months after the fact, I thought it may well be time to post a blog on this little code snippet.
As some of you have noticed every commit message to my subversion repository is infact updating my twitter.
This code was uploaded to subversion on 10/06/2009, so sorry for the late write up!
Requirements
Python 2.5 or higher
Subversion server
Installation
- svn co http://svn.saiweb.co.uk/branches/python/svn_tweeter.py /usr/bin/svn_tweeter
- chmod +x /usr/bin/svn_tweeter
- cd /path/to/svn/hooks
- Edit post-commit with your favorite text editor
1
| /usr/bin/python /usr/bin/svn_tweeter -u twitterusername -p twitterpassword -r $REV -s $REPOS |
Now try a commit, and check your syslog for entries from the script.
Aug 24 11:36:26 132 python: SVN_TWEETER: http://twitter.com/statuses/update.json query complete
UPDATE 24/03/2011 Twitter has removed basic authentication, you must use oauth (admittedly it has been like this for a fair while now) use this nagios_bot instead
Tags:
hooks,
post-commit,
Subversion,
svn,
twitter
No Comments »
Posted by Buzz in python
After taking another look at Python I am quickly coming to love it, as an “exercise” in re-learning python I decided to write a very simple command line “tweeter” this uses the Twitter API to update your twitter status, extending from the “update twitter in a single line”
You can grab a copy of the script from here: http://svn.saiweb.co.uk/branches/python/tweet.py
UPDATE 24/03/2011:Oauth version here
Example usage:
1
| ./tweet.py -u username -p password -t your tweet goes here |
If you want to parse the JSON data normally returned after submitting a new tweet simply add the -j flag.
If you are prompted for a username and password when running this script the username and password supplied using the -u and -p flags was incorrect.
Tags:
python,
twitter
3 Comments »
Posted by Buzz in Linux
As it turns out twitter account can be updated in a single line, this makes writing “bots” just that little bit easier.
1
| /usr/bin/curl --basic --user "username:password" --data-ascii "your tweet" http://twitter.com/statuses/update.json |
This also returns JSON should you want to parse the reply data.
i.e.
1
| {"in_reply_to_screen_name":null,"in_reply_to_status_id":null,"truncated":false,"user":{"profile_image_url":"http:\/\/static.twitter.com\/images\/default_profile_normal.png","description":"","followers_count":0,"screen_name":"user","url":null,"name":"user","protected":true,"location":"","id":12345678},"text":"your tweet","favorited":false,"created_at":"Fri Mar 20 11:38:44 +0000 2009","in_reply_to_user_id":null,"id":1359757870,"source":"web"} |
At the moment I am looking at hooking this into Nagios, from there the feed will be passed into a ‘service status page’.
But in theory this single line could be used for any purpose.
Tags:
twitter
2 Comments »