Skip to content
Universal event notification broker/manager
Python Shell TSQL Dockerfile
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin xparams clear between commands Sep 30, 2019
data docker Feb 18, 2019
etc db fixes Feb 26, 2019
lib/roboger allow attach Aug 29, 2019
sbin icli Sep 30, 2019
Dockerfile tables migrated to rapidtables Aug 29, 2019
LICENSE license Feb 17, 2019
docker-compose.yml docker Feb 18, 2019
endpoints.txt fmt May 11, 2018 perm Feb 18, 2019
roboger-mysql.sql sqlite support Feb 17, 2019
roboger-sqlite.sql sqlite support Feb 17, 2019

What is Roboger?

  • Do you like the old good "echo alarm | sendmail me@mydomain" trick in crontab?
  • Does your software or servers send you mail/sms alerts when something is wrong?
  • Tired of getting emails from robots?

Then Roboger is definitely for you!

Actually nowadays the majority of emails are sent from robots and people don't need to reply. People eventually use emails much less, preferring messengers and alternative apps. And we made Roboger - a new generation messenger designed specifically for robots.

How Roboger works

What can Roboger do?

  • It can get notifications and forward them to specified endpoints
  • It supports endpoint types: email, http/post, http/json, Slack, Telegram and Roboger Smartphone App (only via
  • This software actually allows you to run your own Roboger server, in case you don't want to use, want to have a backup alternative or want to use custom http web hooks.

Real life example

You get information messages from your server to Slack, warnings to Slack and Telegram, errors to messengers and by mail and on critical events you want to additionally hook API of your PBX to call you on mobile.

In the past you would have needed to write a code, call APIs, manage event routing and finish in a script hell without any idea what and where notifies you.

Now you can use Roboger, where everything is already coded, organized and can be set up with a couple of commands.

How to use

Firstly - set up Roboger server, create address, endpoints and subscriptions with ./bin/roboger-cmd

Then use Roboger API to send event notifications:

POST http://your-roboger-host:7719/push < JSON
    'addr': 'towhere',
    'sender': 'from (e.g. from robot1)',
    'location': 'where something is happened',
    'keywords': 'comma, separated, eg, serverfail, alarm, achtung',
    'subject': 'what we are talking about',
    'msg': 'message body',
    'level': 'alarm level (debug, info, warning, error or critical)',
    'media': 'base64-encoded binary eg. photo from surveillance camera')
(all fields except address are optional, default level is "info")

Or, for old machines (you can't send binary data with GET):

GET http://your-roboger-host:7719/push?r=&s=&l=&k=&s=&m=&l=

Or with roboger-push console client in the old good crontab or any other software/scripts:

echo Everything's down!!! | roboger-push

roboger-push app is written in pure bash, so it will run almost everywhere, addresses are defined in /usr/local/etc/roboger_push.ini.

Note: if you want to send media attachments with roboger-push, you should have local openssl CLI installed (it's actually installed everywhere by default, we just warn you about that)

Python client module

Client module for Python 3: The module can be installed with pip3:

pip3 install pyrpush

Usage example:

from pyrpush import Client as RPushClient

r = RPushClient()
r.sender = 'bot1'
r.location = 'lab'
r.push('test message')
r.push(msg='sending you image', media_file='1.jpg', level='warning')

The module requires roboger-push client installed (uses its config only, you can remove roboger-push script after the installation)


  • until the launch of, stability is very limited, management API can be changed at any time. Use at your own risk


  • put roboger to /opt/roboger (recommended)
  • install realpath and pip3
  • python3 module python3-cryptography has problems installing via pip3, install it rather manually
  • run to make required dirs and install missing python3 mods
  • use sqlite database (default) or:
    • install pymysql module (pip3 install pymysql)
    • create mysql database 'roboger' (or set any other name you wish)
    • create mysql user for roboger db
    • run mysql roboger < roboger-mysql.sql
  • copy etc/roboger.ini.dist to etc/roboger.ini, edit required fields
  • obtain Telegram bot token for your private bot if you plan to use Telegram endpoints and put it to roboger.ini as well
  • run ./sbin/roboger-control start
  • test it: ./bin/roboger-cmd test
  • append '/opt/roboger/sbin/roboger-control start' to /etc/rc.local or any other startup place (or use supervisord, see below)
  • copy ./etc/logrotate.d/roboger to /etc/logrotate.d/roboger (not required if you run roboger with supervisord)
  • that's it :)

Installing roboger-push only

Docker image

Launching with supervisord

(if working with supervisord, log rotation is not required because roboger prints everything to stdout)

  • install superlance httpok (pip install superlance)

  • copy etc/supervisor/conf.d/roboger.conf to /etc/supervisor/conf.d

  • put a string to etc/roboger.ini [server] section:

    supervisord_program = roboger

Endpoint types

  • email sends email notifications. Config: rcpt=mail_address (requires SMTP server on localhost or point to the right one in ./etc/roboger.ini)
  • http/post sends HTTP/POST request. Config: url=url, params=request variables (JSON string)
  • http/json sends HTTP/POST request with JSON body. Config: url=url, params=request_variables (JSON string)
  • slack sends notification in Slack. Config: url=slack_webhook_url, fmt=rich (for rich text notifications)
  • telegram sends notifications in Telegram. Config: chat_id=your_chat_id

How it works with Telegram

  • Firstly you need to register your own bot and obtain bot token (
  • Put bot token to etc/roboger.ini and restart roboger server
  • Find your bot in Telegram and write something to chat
  • Bot will instantly report you your Chat ID. Use it for chat_id=chat_id config param when creating endpoint.

Note: roboger Chat ID is different from integer Telegram Chat ID. Actually it's encrypted with your bot token to avoid people brute forcing chat IDs of shared bots.

Configuration deployment

./bin/roboger-cmd does the job, but if you want to deploy in batch, use roboger-cmd deploy file.yml command. Look sample-deploy.yml for deployment example.

You can’t perform that action at this time.