APM
Planned: link slow pages to the server work behind them
Noxtica is building an OpenTelemetry-compatible intake for backend traces, metrics and logs. It is planned to connect that telemetry to browser sessions in the console.
Planned capabilities
These items describe the design direction. None of them is a commitment on scope or date.
In development
Browser session
A slow page load
Collected by the Noxtica browser script.
Standard W3C trace context headers
Would let a browser session point to the backend trace behind it.
Backend trace
The server work behind that page load
From services that already emit OpenTelemetry data.
Traces, metrics and logs
Linked to browser sessions
Keys and tenant scoping
Planned approach
Console
Issue a telemetry key
An operator would create a telemetry key for the tenant in the Noxtica console.
In development
Your services
Send OpenTelemetry data
Traces, metrics and logs
Services that already emit OpenTelemetry data would send it to the Noxtica intake with that key.
In development
Console
Review beside browser sessions
Backend telemetry
Operators would read traces, metrics, logs and releases next to browser session data.
In development
Issue a telemetry key
Send OpenTelemetry data
Review in the console
Status and boundaries
- APM is in development. Nothing on this page is a commitment on scope or date.
- The planned focus would be linking telemetry to browser sessions, not infrastructure monitoring, general log management or continuous profiling.
- No performance or capacity claims are made on this page.
- Traces and logs can carry personal data. Customers would remain responsible for notice, consent, retention and what their services send.
Monitoring and replay must follow your notices, consent and masking settings, and our acceptable use rules.Read the acceptable use policy