jamesr2323 / nr-heroku-logs

Application to send logs from Heroku to New Relic

Heroku forwarder for New Relic

This is a Heroku application which can forward logs to New Relic, it is based on fluentd. This application accepts logs from HTTPS drains and forward the logs to New Relic logs collector using NR logs APIs.

This application is using 3 components:

• Fluentd: data collection software.
• Fleuntd-Heroku input plugin: accepts and process Heroku HTTPS log drains.
• Fluentd-NewRelic output plugin: output plugin that sends logs to New Relic.

This application uses the request PATH to specify the fluentd tag to use for routing.

Setup

Heroku doesn't allow users to install separate processes within a single dyno. You will thus need to setup Fluentd as a separate Heroku application. This will become your central log aggregation server.

Follow the steps below to create Fluentd and NR plugin as a Heroku application.

# Get the code
$ git clone git://github.com/aminoz007/NR-Heroku-Logs.git
$ cd NR-Heroku-Logs
$ rm -rf .git
$ git init
$ git add .
$ git commit -m 'initial commit'

# Login to Heroku, then create the app
$ heroku apps:create YOUR-LOGGING-APP-NAME (i.e NR-logs-forwarder)

# Next, configure your API key
$ heroku config:set NR_API_KEY=YOUR-NR-INSERT-API-KEY -a YOUR-LOGGING-APP-NAME

# Deploy
$ git push heroku master

Once the logging apllication is up and running. You can configure Heroku HTTPS log drains to publish logs to this application.

$ heroku drains:add https://YOUR-LOGGING-APP-NAME/newrelic.YOUR-SOURCE-APP-NAME -a YOUR-SOURCE-APP-NAME

PS: You may need to add ".herokuapp.com" to the logging app name depending on the URL of your logging app.

• Example:
  • URL of logging app: https://NR-logs-forwarder.herokuapp.com/
  • App from where logs should be collected: my-cool-app
  • Command: $ heroku drains:add https://NR-logs-forwarder.herokuapp.com/newrelic.my-cool-app -a my-cool-app

Logs should now be flowing from your service to New Relic 😉.

Troubleshoot

This application supports sending incoming events to STDOUT using a debug tag prefix.

# debug using curl
$ curl "https://YOUR-LOGGING-APP-NAME/debug.YOUR-SOURCE-APP-NAME" -d "60 <13>1 time host app web.1 - myMessage"