Discard
Synopsis
Creates a target that discards all incoming log messages.
This target has no GUI creation wizard. Configure it directly in the target YAML file.
Schema
- name: <string>
description: <string>
type: discard
tags: <string[]>
pipelines: <pipeline[]>
status: <boolean>
Configuration
The following fields are used to define the target.
| Field | Required | Default | Description |
|---|---|---|---|
name | Y | Target name | |
description | N | - | Optional description |
type | Y | Must be discard | |
tags | N | - | Optional tags |
pipelines | N | - | Optional post-processor pipelines |
status | N | true | Enable/disable the target |
Details
This target accepts any log data, but does not store or forward it. It is useful for development, benchmarking and load testing data ingestion without storage overhead, and debugging pipeline configurations.
Data sent to this target is permanently lost and cannot be recovered.
There is nothing to troubleshoot here. The target opens no connection, has no properties, and reports no errors, so it never fails to initialize and never fails a delivery. One point is worth knowing when you read the statistics: discarded messages are counted as Events Out, so this target reports the same delivery figures as a target that kept your data. That counter is the only sign the target ran, and it is not evidence that anything was stored.
Examples
The configuration for discarding logs:
Creating a discard target... | |