https://github.com/kivra/lager_loggly

Loggly backend for lager
https://github.com/kivra/lager_loggly

Last synced: 3 months ago
JSON representation

Loggly backend for lager

• Host: GitHub
• URL: https://github.com/kivra/lager_loggly
• Owner: kivra
• License: mit
• Created: 2012-08-31T08:14:47.000Z (about 12 years ago)
• Default Branch: master
• Last Pushed: 2016-10-26T22:18:45.000Z (about 8 years ago)
• Last Synced: 2024-06-21T18:04:45.767Z (5 months ago)
• Language: Erlang
• Size: 589 KB
• Stars: 16
• Watchers: 11
• Forks: 5
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-erlang - lager_loggly - Loggly backend for lager. (Logging)

README

        
Overview

============

This is a Loggly backend for lager which lets you send lager logs to your Loggly account.

##Configuration

Configure a Lager handler like the following:

	{lager_loggly_backend, [Level, MaxRetries, RetryInterval, LogglyUrl]}

* Level - The lager level at which the  backend accepts messages (eg. using ‘info’ would send all messages at info level or above into syslog)

* MaxRetries - The maximum number of retries the backend will do before giving up on Loggly

* RetryInterval - The interval at which each retry is performed. i.e. Retries 5 and Interval 3 means that it will try a maximum of 5 times with 3 seconds apart

* LogglyUrl - This is your unique Loggly URL for a given Input, including your application specific identity tag

An example might look something like this:

	{lager_loggly_backend, [info, 5, 3, "https://logs-01.loggly.com/inputs/1c6b53a4-972b-4c69-83ea-037de24c9bb2/tag/my_id/"]}

Refer to Lager’s documentation for further information on configuring handlers.

##Upgrade notes

Since the identity tag should be appended directly to the `LogglyUrl` while accessing the current Loggly API, the previous configuration option `Identity` was removed.