Ent+Documentation Index
Fetch the complete documentation index at: https://docs.honeycomb.io/llms.txt
Use this file to discover all available pages before exploring further.
This feature is available as an add-on for the Honeycomb Enterprise plan.
Please contact your Honeycomb account team for details.
Filter by Field Processor
The Filter by Field processor can be used to include or exclude telemetry based on matched resource attributes, attributes, or log body fields.Supported Types
| Metrics | Logs | Traces |
|---|---|---|
| ✓ | ✓ | ✓ |
Configuration Table
| Parameter | Type | Default | Description |
|---|---|---|---|
| telemetry_types | telemetrySelector | ["Logs", "Metrics", "Traces"] | The list of telemetry types the processor will act on. |
| action | enum | exclude | Whether to include (retain) or exclude (drop) matches. |
| match_type | enum | strict | Method for matching values. Strict matching requires that ‘value’ be an exact match. Regexp matching uses re2 to match a value. |
| attributes | map | [] | Attribute key value pairs to filter on. Telemetry is filtered if all attribute, resource, and body key pairs are matched. |
| resources | map | [] | Resource key value pairs to filter on. Telemetry is filtered if all attribute, resource, and body key pairs are matched. |
| bodies | map | [] | Log body key value pairs to filter on. Log records filtered if all attribute, resource, and body key pairs are matched. |
Example Configuration
Excluding matching log records
In this example, we exclude logs that have all of the following:- A
host.nameresource attribute that equalsdev-server - An
environmentattribute that equalsdev - A
remote-iplog body field that equals127.0.0.1
Web Interface
