loggly
For more info on Batch-Processor in Apache APISIX please refer to: Batch-Processor
Attributes
To generate a Customer Token, head over to <your assigned subdomain>/loggly.com/tokens
or navigate to Logs > Source Setup > Customer Tokens
to generate a new token.
Name | Type | Requirement | Default | Valid | Description |
---|---|---|---|---|---|
host | string | optional | “logs-01.loggly.com” | The host address endpoint where logs are being sent. | |
port | integer | optional | 514 | Loggly port (for “syslog” protocol only) to make a connection request. | |
timeout | integer | optional | 5000 | Loggly send data request timeout in milliseconds. | |
protocol | string | optional | “syslog” | [ “syslog” , “http”, “https” ] | Protocol through which the logs are sent to Loggly from APISIX (currently supported protocol : “syslog”, “http”, “https”) |
log_format | object | optional | nil | Log format declared as key value pair in JSON format. Only string is supported in the part. If the value starts with $ , it means to get APISIX variables or . If it is nil or empty object, APISIX generates full log info. |
How To Enable
The following is an example of how to enable the loggly
for a specific route.
Minimal configuration
- Login to Loggly Dashboard to search and view
Disable Plugin
Disabling the loggly
plugin is very simple, just remove the JSON
configuration corresponding to . APISIX plugins are hot loaded, so no need to restart APISIX.