Observability

SiteQwality’s observability suite has five pillars. They share the same time picker, dashboards, and alerting fabric, so once you know one you know the others.

Pillar	Stores	Best for
Metrics	Numeric time-series with tags	Counters, gauges, histograms, anything chart-able
Logs	Structured + unstructured events	Error context, audit trails, full-text search
Traces	Span trees following one request	Why a request was slow, what services it touched
RUM	Browser-side telemetry from real users	Web vitals, JS errors, user actions
Replay	Pixel playback of user sessions	”What did the user actually do?” debugging

How they relate

       (numeric ↑↓)              (events)              (request shape)
        Metrics    ←────→         Logs       ←────→        Traces
         "what?"               "why?"                  "where?"

                                    │
                                    │ correlates via trace_id
                                    │
                                    ▼
                                  RUM            ←────→     Replay
                                "from the user's side"

A trace can pull in logs for any of its spans (look for trace_id in your logs).
RUM session events include the trace IDs of XHR/fetch requests, letting you jump from a user’s experience to the back-end trace.
Metrics are derived from logs/traces at ingest time (count of errors, p99 latency) and can be alerted on.

When to reach for which

Question	Tool
”How many errors in the last hour?”	Metrics. Alertable, fast, cheap.
”What was the error message at 14:32?”	Logs. The full payload is there.
”Why was that one request slow?”	Traces. See the call graph.
”What was the LCP for users in Brazil?”	RUM. Geographically segmented.
”What did the user click before the error?”	Replay. Watch them.

If you find yourself reaching for logs to answer “how many”, that’s a metric. Emit one. If you reach for metrics to answer “what was the actual value”, that’s a log. Cross-emit.

Ingestion

Pillar	Endpoint	Auth
Metrics	`POST https://metrics.siteqwality.com/metrics`	API key
Logs	`POST https://logs.siteqwality.com/v1/ingest`	API key
Traces	`POST https://traces.siteqwality.com/v1/traces` (OTLP-compatible)	API key
RUM	Auto via SDK	Client token (per-app, public)
Replay	Auto via SDK	Client token (per-app, public)

Backends:

Postgres for transactional data (configs, accounts, dashboards).
ClickHouse for time-series storage (metrics, logs, traces, RUM events).
S3 for blobs (HAR files, video, replay segments).

Pricing

The observability pillars are paid features beyond the included free tier. Pricing is based on seats and ingestion volume. See Settings → Billing → Plans.