The snapshot processor is used in custom distributions of the collector to provide snapshot functionality in Bindplane. It is not currently included in the official bindplane-agent.
- Logs
- Metrics
- Traces
- The user configures the processor in one or more pipelines.
- Whenever telemetry passes through the processor, it is copied and stored temporarily in an internal buffer.
- An OpAMP server is able to use a custom message to request the contents of the internal buffer, in order to view a snapshot of the telemetry flowing through the collector.
| Field | Type | Default | Required | Description |
|---|---|---|---|---|
| enabled | bool | true |
false |
Whether the snapshot processor is enabled or not. |
| opamp | string | opamp |
true |
Specifies the name of the opamp extension for sending custom messages. |
The snapshot processor may be used in a pipeline in order to temporarily catch telemetry data in a buffer, which an opamp server may request:
receivers:
file_log:
include: [/var/log/logfile.txt]
processors:
snapshotprocessor:
enabled: true
opamp: opamp
exporters:
nop:
extensions:
bindplane:
labels: "labelA=valueA,labelB=valueB"
opamp:
endpoint: "https://localhost:3001/v1/opamp"
service:
extensions: [bindplane, opamp]
pipelines:
logs:
receivers: [file_log]
processors: [snapshotprocessor]
exporters: [nop]In this instance, the OpAMP server can now request a snapshot using the com.bindplane.snapshot capability (see request.go for more information on the payload).