My Profile Photo

Fabio Pitino

full stack software developer & code crafter, musician & food lover

Introducing ElasticNotifier

ElasticNotifier is a gem that provides a simple API to send error notifications to an ElasticSearch server.

As you rescue errors in your application you can send them to an ElasticSearch index to be used later for analytics, reports and dashboards.

Alternatively, ElasticNotifier is also compatible with exception_notification gem as a Notifier plug-in. ExceptionNotification is a Rack middleware that intercepts any unhandled errors from Rails (Sinatra or any other Rack-based) applications and sends notifications using various configurable notifiers.

Getting started

Add the gem to your application’s Gemfile and run bundle command.

Configure the notifier:

  url: "", # default is http://localhost:9200
  index: "my_custom_index",        # default is :elastic_notifier
  type: "my_document_type"         # default is :signals

For Rails applications you can add the code above to config/initializers/elastic_notifier.rb so it will be available throughout the app.

Then send error notifications as you rescue errors:

  # some code that raises an exception
rescue => error

How can I use it with ExceptionNotification gem?

In config/initializers/elastic_notifier.rb, after initializing the notifier object as described above, you need to register it as documented here:

notifier = "")
ExceptionNotifier.add_notifier :elastic_search, notifier

Now any unhandled failures from your app will result in a document sent to ElasticSearch.

For background processes, you can leverage all registered notifiers (email, Elastic Search, Slack, etc.) with a single command!

  # some code that raises an exception
rescue => exception

What information is being sent?

At the time the notifier is invoked it collects some information from the environment, serializes it together with the exception details and sends it to the Elastic instance.

  severity: "error",
  timestamp: "2017-12-31 23:59:59",
  program_name: "my_app.rb",
  pid: 1345,
  hostname: "myservicename",
  ip: "",
  data: {
    name: "NoMethodError",
    message: "undefined method `test` for nil:NilClass",
    backtrace: [...]

It is possible to override parameters such as program_name which will remain static for the notifier instance.

notifier = "", program_name: "custom_name")

Do you fancy contributing?

Please get in touch! Bug reports and PR as well as simple feedback are very welcome! The code is available on GitHub and the gem is officially deployed to

comments powered by Disqus