A telemetry forwarder is a component that receives logs, metrics, traces or events from one system and relays them to another destination. It often buffers, filters, enriches or transforms records before delivery, and is used in observability pipelines to move operational data between applications, agents and analysis platforms.
What a telemetry forwarder does in an observability pipeline
A telemetry forwarder is not the analysis engine itself. It sits between sources and destinations, accepting logs, metrics, traces or events and relaying them onward so operational data can be moved consistently across tools, environments and teams. That makes it a routing and handling component, not just a pass-through.
In practice, the forwarder often becomes the first shared control point for telemetry in an organisation. It may normalise record formats, batch traffic to reduce overhead, or apply basic enrichment so downstream platforms receive data in a shape they can use. Those functions make it central to how observability data is prepared and delivered.
How forwarding differs from collection, processing and storage
Telemetry collection is about receiving data from the source. Forwarding is about relaying that data to another place, often after light processing. Storage and analytics then happen later, in a log platform, metrics backend, trace system or security tool. Keeping those roles distinct matters because the forwarder usually has narrower responsibilities than a full observability backend.
This distinction is useful when designing pipelines. A forwarder can buffer transient bursts, filter obvious noise, or transform fields before delivery, but it should not be assumed to provide durable retention, full search, or long-term analysis. If those functions are needed, they belong in downstream systems rather than in the forwarding layer.
Why buffering, filtering and transformation matter
The value of a telemetry forwarder is often in what it does around delivery. Buffering helps absorb spikes and temporary destination unavailability. Filtering can remove low-value data before it consumes bandwidth or storage. Transformation can align source-specific records with the schema expected by the receiving platform. Those capabilities improve reliability and reduce waste, but they also increase the importance of correct configuration.
Because the forwarder handles operational data in transit, it may need to preserve ordering, avoid duplicate delivery where possible, and handle backpressure gracefully. The more it modifies telemetry, the more carefully teams need to validate that security-relevant fields, timestamps and context are not lost or distorted.
Where telemetry forwarders fit in an observability architecture
Telemetry forwarders are common in distributed systems because they decouple producers from consumers. Applications can emit data without knowing which analysis stack will receive it, and platforms can change independently as long as the forwarder still speaks the expected transport or format. That flexibility is useful in multi-cloud, hybrid and high-change environments.
Forwarders also become a practical place to centralise policy for telemetry handling. Organisations may use them to decide which data classes may leave a network segment, which fields should be removed or redacted, and which destinations are permitted. For that reason, a forwarder is often part of the security boundary for operational data, not merely an infrastructure convenience.
Risk and Threat Considerations
Telemetry forwarders can expose sensitive operational content if they are misconfigured, over-privileged or trusted too broadly. Because they sit on the path between production systems and analysis destinations, compromise or misuse of the forwarder can affect visibility, integrity and confidentiality at the same time.
Failure mechanism: Attackers or insiders may abuse the forwarder to intercept, suppress, tamper with or reroute telemetry, especially if it accepts broad inbound sources or forwards to multiple destinations without strong control.
Impact: A compromised forwarder can hide attacker activity, distort incident data, leak sensitive logs or traces, and degrade detection by corrupting the data that monitoring and response tools depend on.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5, CIS Controls v8 and NIST CSF 2.0 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AU-2 — Event Logging | Telemetry forwarders move audit and operational events that AU-2 governs. |
| AU-6 — Audit Record Review, Analysis, and Reporting | Forwarded telemetry feeds downstream review and anomaly analysis. | |
| SC-8 — Transmission Confidentiality and Integrity | Forwarders relay telemetry in transit, where confidentiality and integrity matter. | |
| Recommendation — Define which events the forwarder must relay and preserve for auditability. Ensure forwarded telemetry remains usable for review and correlation. Protect telemetry in transit between producers, forwarders and destinations. | ||
| CIS Controls v8 | CIS-8 — Audit Log Management | Telemetry forwarding is a core audit-log handling function in CIS safeguards. |
| Recommendation — Centralise and protect log forwarding so audit data remains reliable. | ||
| NIST CSF 2.0 | DE.CM-01 — The network is monitored to detect potential cybersecurity events | Forwarded telemetry is the raw material for continuous monitoring. |
| Recommendation — Route telemetry so monitoring pipelines can detect events consistently. | ||
Practitioner Guidance
Why practitioners should care: Treat the forwarder as part of the telemetry trust chain, not a neutral plumbing component. Its configuration determines which data is collected, how it is shaped, and where it is allowed to go.
What to watch for: Pay attention to broad source acceptance, unauthorised destination changes, unexpected filtering rules, and pipeline outages that create blind spots or force telemetry to be dropped. Those are often the first signs that the forwarding layer has become a control weakness.
Practitioner takeaway: The safest design is one where the forwarder has the minimum handling scope needed for delivery, with clear ownership for its configuration, policy and monitoring.
Related resources from NHI Mgmt Group
- When should organisations treat runtime telemetry as a primary control?
- Should organisations require security telemetry before adopting SaaS tools?
- Who should own trust telemetry when reporting spans NHI and cryptography controls?
- What should organisations control before exposing identity telemetry to AI assistants?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 16, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org