Detailed text description: Request browser architecture
This page describes the request browser architecture graphic.
Overview
The graphic shows the request-observability path from incoming application traffic to indexed request traces shown in the Request Browser.
Main stages
- Request entry:
- Incoming HTTP traffic reaches platform routing and target services.
- Trace and metric capture:
- Request metadata is captured, including timestamp, method, path, status code, and duration.
- Correlation identifiers can be attached for traceability.
- Processing pipeline:
- Captured request data is sent through observability ingestion.
- Data is normalized and indexed for querying.
- Storage and retention:
- Request records are retained for a fixed period and subject to storage quotas.
- Browser interface:
- Users inspect request events in the Request Browser.
- Filters allow narrowing by service, status, method, resource path, and time range.
Key takeaway
The architecture enables end-to-end request visibility from traffic ingestion to queryable observability views.