﻿---
title: Datadog output plugin v3.0.3
description: Plugin version: v3.0.3, Released on: 2017-08-16, Changelog. For other versions, see the overview list. To learn more about Logstash, see the Logstash...
url: https://docs-v3-preview.elastic.dev/elastic/logstash-docs-md/tree/main/vpr/v3-0-3-plugins-outputs-datadog
---

# Datadog output plugin v3.0.3
- Plugin version: v3.0.3
- Released on: 2017-08-16
- [Changelog](https://github.com/logstash-plugins/logstash-output-datadog/blob/v3.0.3/CHANGELOG.md)

For other versions, see the [overview list](https://docs-v3-preview.elastic.dev/elastic/logstash-docs-md/tree/main/vpr/output-datadog-index).
To learn more about Logstash, see the [Logstash Reference](https://www.elastic.co/guide/en/logstash/current/index.html).

## Getting help

For questions about the plugin, open a topic in the [Discuss](http://discuss.elastic.co) forums. For bugs or feature requests, open an issue in [Github](https://github.com/logstash-plugins/logstash-output-datadog). For the list of Elastic supported plugins, please consult the [Elastic Support Matrix](https://www.elastic.co/support/matrix#matrix_logstash_plugins).

## Description

This output sends events to DataDogHQ based on Logstash events.
Note that since Logstash maintains no state these will be one-shot events

## Datadog Output Configuration Options

This plugin supports the following configuration options plus the [Common options](#v3.0.3-plugins-outputs-datadog-common-options) described later.

| Setting                                                                                  | Input type                                                                                                                                                                                                    | Required |
|------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------|
| [`alert_type`](#v3.0.3-plugins-outputs-datadog-alert_type)`alert_type`                   | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string, one of `["info", "error", "warning", "success"]`                                                                                  | No       |
| [`api_key`](#v3.0.3-plugins-outputs-datadog-api_key)`api_key`                            | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string                                                                                                                                    | Yes      |
| [`date_happened`](#v3.0.3-plugins-outputs-datadog-date_happened)`date_happened`          | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string                                                                                                                                    | No       |
| [`dd_tags`](#v3.0.3-plugins-outputs-datadog-dd_tags)`dd_tags`                            | [array](/elastic/logstash-docs-md/tree/main/lsr/value-types#array)array                                                                                                                                       | No       |
| [`priority`](#v3.0.3-plugins-outputs-datadog-priority)`priority`                         | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string, one of `["normal", "low"]`                                                                                                        | No       |
| [`source_type_name`](#v3.0.3-plugins-outputs-datadog-source_type_name)`source_type_name` | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string, one of `["nagios", "hudson", "jenkins", "user", "my apps", "feed", "chef", "puppet", "git", "bitbucket", "fabric", "capistrano"]` | No       |
| [`text`](#v3.0.3-plugins-outputs-datadog-text)`text`                                     | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string                                                                                                                                    | No       |
| [`title`](#v3.0.3-plugins-outputs-datadog-title)`title`                                  | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string                                                                                                                                    | No       |

Also see [Common options](#v3.0.3-plugins-outputs-datadog-common-options) for a list of options supported by all output plugins.

### `alert_type`

- Value can be any of: `info`, `error`, `warning`, `success`
- There is no default value for this setting.

Alert type

### `api_key`

- This is a required setting.
- Value type is [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)
- There is no default value for this setting.

Your DatadogHQ API key

### `date_happened`

- Value type is [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)
- There is no default value for this setting.

Date Happened

### `dd_tags`

- Value type is [array](/elastic/logstash-docs-md/tree/main/lsr/value-types#array)
- There is no default value for this setting.

Tags Set any custom tags for this event Default are the Logstash tags if any

### `priority`

- Value can be any of: `normal`, `low`
- There is no default value for this setting.

Priority

### `source_type_name`

- Value can be any of: `nagios`, `hudson`, `jenkins`, `user`, `my apps`, `feed`, `chef`, `puppet`, `git`, `bitbucket`, `fabric`, `capistrano`
- Default value is `"my apps"`

Source type name

### `text`

- Value type is [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)
- Default value is `"%{message}"`

Text

### `title`

- Value type is [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)
- Default value is `"Logstash event for %{host}"`

Title

## Common options

These configuration options are supported by all output plugins:

| Setting                                                                         | Input type                                                                    | Required |
|---------------------------------------------------------------------------------|-------------------------------------------------------------------------------|----------|
| [`codec`](#v3.0.3-plugins-outputs-datadog-codec)`codec`                         | [codec](/elastic/logstash-docs-md/tree/main/lsr/value-types#codec)codec       | No       |
| [`enable_metric`](#v3.0.3-plugins-outputs-datadog-enable_metric)`enable_metric` | [boolean](/elastic/logstash-docs-md/tree/main/lsr/value-types#boolean)boolean | No       |
| [`id`](#v3.0.3-plugins-outputs-datadog-id)`id`                                  | [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)string    | No       |


### `codec`

- Value type is [codec](/elastic/logstash-docs-md/tree/main/lsr/value-types#codec)
- Default value is `"plain"`

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.

### `enable_metric`

- Value type is [boolean](/elastic/logstash-docs-md/tree/main/lsr/value-types#boolean)
- Default value is `true`

Disable or enable metric logging for this specific plugin instance. By default we record all the metrics we can, but you can disable metrics collection for a specific plugin.

### `id`

- Value type is [string](/elastic/logstash-docs-md/tree/main/lsr/value-types#string)
- There is no default value for this setting.

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 datadog outputs. Adding a named ID in this case will help in monitoring Logstash when using the monitoring APIs.
```
output {
  datadog {
    id => "my_plugin_id"
  }
}
```