Issue
There is a lack of documentation anywhere on the exporter delegate chain. We could benefit from some documentation somewhere that explains that the default delegate chain.
Notes
Taken from @LikeTheSalad (CNCF Slack):
The current delegate order is:
BufferDelegating -> DiskBuffering -> OtlpHttp[Span | LogRecord]Exporter
- BufferDelegating is an in-memory exporter set to collect telemetry before the agent is fully initialized, which is only used for that time window. See this PR for more details.
- DiskBuffering is the first in the chain, so that everything is stored in disk first.
- OtlpHttp*Exporter is the one where the actual export happens eventually in one of the disk read operations.
Additionally, people can add their own exporter layers using the add*ExporterCustomizer builder methods. In which case they decide what's the last exporter in the chain, as DiskBuffering will be on top of whatever is added this way.
Issue
There is a lack of documentation anywhere on the exporter delegate chain. We could benefit from some documentation somewhere that explains that the default delegate chain.
Notes
Taken from @LikeTheSalad (CNCF Slack):
The current delegate order is:
Additionally, people can add their own exporter layers using the
add*ExporterCustomizerbuilder methods. In which case they decide what's the last exporter in the chain, as DiskBuffering will be on top of whatever is added this way.