To tłumaczenie zostało wygenerowane maszynowo i oczekuje na weryfikację.Przełącz na angielski

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.

WHAT IS PLANNED

Planned capabilities

These items describe the design direction. None of them is a commitment on scope or date.

  • Traces, metrics and logs

    The intake is planned to accept OpenTelemetry traces, metrics and logs over HTTP and gRPC. Release markers would show which deployment a change belongs to.

  • Linked to browser sessions

    Standard W3C trace context would let a browser session point to the backend trace behind a slow page load.

  • Keys and tenant scoping

    An operator would issue a telemetry key for the tenant in the console. Trace context would link data but would not decide which tenant it belongs to.

PLANNED APPROACH

Planned approach

These steps describe the intended design, not a released workflow.

  1. Console

    Issue a telemetry key

    An operator would create a telemetry key for the tenant in the Noxtica console.

    In development

  2. 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

  3. Console

    Review beside browser sessions

    Backend telemetry

    Operators would read traces, metrics, logs and releases next to browser session data.

    In development

Planned approach: a telemetry key, OpenTelemetry data from your services, then console viewsIllustration of the planned design. Nothing here is a commitment on scope or timing.
  1. Issue a telemetry key

    An operator would create a telemetry key for the tenant in the Noxtica console.

  2. Send OpenTelemetry data

    Services that already emit OpenTelemetry data would send traces, metrics and logs to the Noxtica intake with that key.

  3. Review in the console

    Operators would read traces, metrics, logs and releases in the console, next to browser session data.

WHERE IT WOULD FIT

Questions it is planned to help answer

Fit depends on what the finished scope turns out to be.

  • Slow page, unclear cause

    Teams could follow a slow page load to the backend request behind it.

  • Behavior after a deployment

    Release markers could help teams compare behavior before and after a deployment.

  • Session and server data together

    Teams that already use Noxtica for browser monitoring could review backend telemetry beside it.

HOW TEAMS WOULD CONNECT IT

Planned connection model

Nothing here is a supported setup today.

  1. Teams with services that already emit OpenTelemetry data would point them at a Noxtica intake with a console-issued key.
  2. Browser sessions collected by the Noxtica browser script could be linked to backend traces through standard trace context headers.
  3. Results would be read in the Noxtica console, in views for traces, metrics, logs and releases.

LIMITS

Status and boundaries

Read this page as a description of intent.

  • APM is in development and is not generally available. 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. Any such claim would need measurement before publication.
  • Traces and logs can carry personal data. Customers would remain responsible for notice, consent, retention and what their services send.

FAQ

Questions about APM

Can I use APM today?

No. It is in development and not generally available. You can ask about early access.

Which standards is it planned to use?

The design uses OpenTelemetry transports and W3C trace context. Details could change before any release.

Will it replace other monitoring tools?

That is not the planned focus. The aim is to connect backend telemetry to browser sessions.

APM

Ask about early access

Early access, if offered, would be agreed directly with Noxtica. Contact the team to ask about APM and describe your use case.