This output lets you send metrics to DataDogHQ based on Logstash events. Default queue_size and timeframe are low in order to provide near realtime alerting. If you do not use Datadog for alerting, consider raising these thresholds.
output {
datadog_metrics {
api_key => ... # string (required)
codec => ... # codec (optional), default: "plain"
dd_tags => ... # array (optional)
device => ... # string (optional), default: "%{metric_device}"
host => ... # string (optional), default: "%{host}"
metric_name => ... # string (optional), default: "%{metric_name}"
metric_type => ... # string, one of ["gauge", "counter", "%{metric_type}"] (optional), default: "%{metric_type}"
metric_value => ... # (optional), default: "%{metric_value}"
queue_size => ... # number (optional), default: 10
timeframe => ... # number (optional), default: 10
workers => ... # number (optional), default: 1
}
}
Your DatadogHQ API key. https://app.datadoghq.com/account/settings#api
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.
Set any custom tags for this event, default are the Logstash tags if any.
The name of the device that produced the metric.
Only handle events without any of these tags. Note this check is additional to type and tags.
The name of the host that produced the metric.
The name of the time series.
The type of the metric.
The value.
How many events to queue before flushing to Datadog prior to schedule set in @timeframe
Only handle events with all of these tags. Note that if you specify a type, the event must also match that type. Optional.
How often (in seconds) to flush queued events to Datadog
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.