output {
librato {
account_id => ... # string (required)
annotation => ... # hash (optional), default: {}
api_token => ... # string (required)
batch_size => ... # string (optional), default: "10"
codec => ... # codec (optional), default: "plain"
counter => ... # hash (optional), default: {}
gauge => ... # hash (optional), default: {}
workers => ... # number (optional), default: 1
}
}
This output lets you send metrics, annotations and alerts to Librato based on Logstash events
This is VERY experimental and inefficient right now. Your Librato account usually an email address
Annotations
Registers an annotation with Librato
The only required field is title
and name
.
start_time
and end_time
will be set to event["@timestamp"].to_i
You can add any other optional annotation values as well.
All values will be passed through event.sprintf
Example: [“title”:”Logstash event on %{host}”, “name”:”logstash_stream”] or [“title”:”Logstash event”, “description”:”%{message}”, “name”:”logstash_stream”]
Your Librato API Token
Batch size Number of events to batch up before sending to Librato.
The codec used for output data. Output codecs are a convenient method for encoding your data before it leaves the output, without needing a separate filter in your Logstash pipeline.
Counters Send data to Librato as a counter
Example:
[“value”, “1”, “source”, “%{host}”, “name”, “messages_received”]
Additionally, you can override the measure_time
for the event. Must be a unix timestamp:
[“value”, “1”, “source”, “%{host}”, “name”, “messages_received”, “measure_time”, “%{my_unixtime_field}”]
Default is to use the event’s timestamp
Only handle events without any of these tags. Note this check is additional to type and tags.
Gauges Send data to Librato as a gauge
Example:
[“value”, “%{bytes_recieved}”, “source”, “%{host}”, “name”, “apache_bytes”]
Additionally, you can override the measure_time
for the event. Must be a unix timestamp:
[“value”, “%{bytes_recieved}”, “source”, “%{host}”, “name”, “apache_bytes”,”measure_time”, “%{my_unixtime_field}]
Default is to use the event’s timestamp
Only handle events with all of these tags. Note that if you specify a type, the event must also match that type. Optional.
The type to act on. If a type is given, then this output will only act on messages with the same type. See any input plugin’s “type” attribute for more. Optional.
The number of workers to use for this output. Note that this setting may not be useful for all outputs.