Follow one event.
Understand the whole path.
Select a node, change the sample route, or step through the pipeline. The envelope shows how context changes at each boundary.
This schematic uses four sample components. The route selector changes an illustrative event locally; it does not make a network request or configure a collector.
Read the explorer guide ↗A few useful answers
Is this the APIPulse API health workflow?
This resource focuses on edge collection and transport. API-level interpretation requires the receiving system to apply its own operation contracts.
Should every request be collected?
Only when the operational need and data budget justify it. Sampling decisions should preserve important errors and remain visible in downstream analysis.
Can events contain request bodies?
Prefer a small allowlist of metadata. Request bodies can contain secrets or personal data and require a separate, justified handling policy.
What happens during a disconnect?
That depends on the chosen buffer and overflow policy. The guides explain how to make that behaviour bounded and observable.