Observability
Site Qwality connects server telemetry with browser experience and monitoring. Start with the setup guides: create an ingest key, pick your language or platform and send data.
| Area | Use it for |
|---|---|
| Logs | Search events, extract fields, analyze volume and follow a request’s context. |
| Metrics | Query gauges, counters and distributions, compare periods and evaluate formulas. |
| Traces | Follow a request through services, inspect spans and find correlated logs. |
| Services | Service and endpoint RED, versions, deployment markers and dependencies. |
| Errors | Group backend exceptions and browser issues with lifecycle and ownership. |
| Alerts and SLOs | Evaluate thresholds, ratios, distributions and error budgets with explicit missing-data states. |
| RUM | Browser performance, resources and JavaScript errors. |
| Session replay | Inspect recorded user interactions subject to consent, sampling and access. |
Send, verify, explore
Section titled “Send, verify, explore”The OTLP/HTTP origin is https://otlp.siteqwality.com, with /v1/logs, /v1/traces and /v1/metrics. JSON, remote-write and platform adapters have their own routes and contracts.
Use stable service.name, deployment.environment.name and service.version: resource identity joins related signals. Logs need actual trace and span IDs to link to a request. Correlation explains browser opt-in and CORS.
Control data and cost
Section titled “Control data and cost”Logs and traces are metered in decimal GB and metrics in active series; allowances, retention and limits are in billing and retention.
Configure processing pipelines before expanding collection. Review access, exports and erasure and keep ingest keys on servers. Telemetry read restrictions apply across explorers, saved views, exports and correlation.