This reporting task is deprecated and will be removed in NiFi 2.x.
Please consider using one the following alternatives: No alternative components suggested.
Publishes metrics from NiFi to datadog. For accurate and informative reporting, components should have unique names.
reporting, datadog, metrics
In the list below, the names of required properties appear in bold. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the NiFi Expression Language.
| Display Name | API Name | Default Value | Allowable Values | Description |
|---|---|---|---|---|
| Metrics prefix | Metrics prefix | nifi | Prefix to be added before every metric Supports Expression Language: true (will be evaluated using variable registry only) | |
| Environment | Environment | dev | Environment, dataflow is running in. This property will be included as metrics tag. Supports Expression Language: true (will be evaluated using variable registry only) | |
| API key | API key | Datadog API key. If specified value is 'agent', local Datadog agent will be used. Sensitive Property: true | ||
| Datadog transport | Datadog transport | Datadog HTTP |
| Transport through which metrics will be sent to Datadog |