Send events to Riemann (http://riemann.io) when FlowFiles pass through this processor. You can use events to notify Riemann that a FlowFile passed through, or you can attach a more meaningful metric, such as, the time a FlowFile took to get to this processor. All attributes attached to events support the NiFi Expression Language.
riemann, monitoring, 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 |
|---|---|---|---|---|
| Riemann Address | Riemann Address | Hostname of Riemann server | ||
| Riemann Port | Riemann Port | 5555 | Port that Riemann is listening on | |
| Transport Protocol | Transport Protocol | TCP |
| Transport protocol to speak to Riemann in |
| Timeout | Timeout | 1000 | Timeout in milliseconds when writing events to Riemann | |
| Batch Size | Batch Size | 100 | Batch size for incoming FlowFiles | |
| Description | Description | Description associated to the event Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Service | Service | Name of service associated to this event (e.g. FTP File Fetched) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| State | State | State of service associated to this event in string form (e.g. ok, warning, foo) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Metric | Metric | Floating point number associated to this event Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| TTL | TTL | Floating point value in seconds until Riemann considers this event as "expired" Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Tags | Tags | Comma separated list of tags associated to the event Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | ||
| Host | Host | ${hostname()} | A hostname associated to this event (e.g. nifi-app1) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) | |
| Time | Time | Time of event in unix epoch seconds (long), default: (current time) Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
Supports Sensitive Dynamic Properties: No
Dynamic Properties allow the user to specify both the name and value of a property.
| Name | Value | Description |
|---|---|---|
| Custom Event Attribute | Any value or expression | These values will be attached to the Riemann event as a custom attribute Supports Expression Language: true (will be evaluated using flow file attributes and variable registry) |
| Name | Description |
|---|---|
| success | Metrics successfully written to Riemann |
| failure | Metrics which failed to write to Riemann |