Loggly output plugin v3.0.5

Getting Help

For questions about the plugin, open a topic in the Discuss forums. For bugs or feature requests, open an issue in Github.
For the list of Elastic supported plugins, please consult the Elastic Support Matrix.

Description

Got a loggly account? Use logstash to ship logs to Loggly!

This is most useful so you can use logstash to parse and structure
your logs and ship structured, json events to your account at Loggly.

To use this, you’ll need to use a Loggly input with type http
and json logging enabled.

Loggly Output Configuration Options

This plugin supports the following configuration options plus the Common Options described later.

host

The hostname to send logs to. This should target the loggly http input
server which is usually "logs-01.loggly.com" (Gen2 account).
See Loggly HTTP endpoint documentation at
https://www.loggly.com/docs/http-endpoint/

key

The loggly http customer token to use for sending.
You can find yours in "Source Setup", under "Customer Tokens".

You can use %{foo} field lookups here if you need to pull the api key from
the event. This is mainly aimed at multitenant hosting providers who want
to offer shipping a customer’s logs to that customer’s loggly account.

proxy_user

retry_count

Retry count.
It may be possible that the request may timeout due to slow Internet connection
if such condition appears, retry_count helps in retrying request for multiple times
It will try to submit request until retry_count and then halt

id

Add a unique ID to the plugin configuration. If no ID is specified, Logstash will generate one.
It is strongly recommended to set this ID in your configuration. This is particularly useful
when you have two or more plugins of the same type. For example, if you have 2 loggly outputs.
Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.