Introduce Telemetry Processor #987
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
12.0.0releaseTelemetry Processorby defaultTelemetry Processorusing a new option calledtelemetry_processor_categories- I'll add those in separate PRs13.0.0we replace sender with telemetry processorSummary
Introduce the TelemetryProcessor — an OTP Supervisor that buffers, batches, and ships log events to Sentry asynchronously, implementing the Backend Telemetry Processor spec.
This is step 1 and currently only the
:logcategory is routed through it. Errors, transactions, and check-ins continue using existing transport paths.Architecture
spawn_monitoradd/2andflush/0Data flow
flowchart TD L["Logger"] --> LB["LogsBackend"] LB --> TP["TelemetryProcessor.add/2"] TP -->|cast| B["Buffer (1000 items)"] TP -->|cast| S["Scheduler"] S -->|poll| B B -->|batch| S S -->|spawn_monitor| HTTP["HTTP POST to Sentry"]