Observability

Thalassa Cloud Observability provides managed metrics and logs through workspaces. A workspace is a regional, project-scoped resource with a single identity (obsw-…) that exposes Prometheus-compatible metrics APIs and Loki-compatible log APIs, plus ruler and Alertmanager for metrics alerting.

You collect data with your own agents (Prometheus, Prometheus Operator, OpenTelemetry Collector, Promtail, Grafana Alloy, and similar). The platform stores, queries, and evaluates alerts so you do not operate Cortex or Loki yourself.

Info

Observability workspaces are currently in Private Beta. Access may be limited — contact support for early access.

General availability is planned for August 2026.

What a workspace includes

Capability	Compatibility	Typical use
Metrics	Prometheus remote write, PromQL query, OTLP metrics	Long-term storage, Grafana, recording and alert rules
Logs	Loki push API, LogQL query, OTLP logs	Centralised application and cluster logs
Alerting	Cortex/Mimir-compatible ruler and Alertmanager	Alert and recording rules; route to email, Slack, Teams, webhooks

Traces are not part of Observability workspaces at this time.

When you create a workspace, metrics and logs backends are both enabled. Retention (retentionDays) applies to all enabled backends (1–1095 days; omit to use the regional default).

Core concepts

Concept	Description
Workspace	Unified metrics + logs resource in a region and project. Identity prefix: `obsw-`.
Gateway endpoints	Regional URLs of the form `{base}/workspace/{workspaceId}/…` for ingest and query.
Control plane API	`POST/GET/PUT/DELETE /v1/observability/workspaces` — create and manage workspaces.
Data plane	Remote write, push, query, ruler, and Alertmanager against the regional gateways.
IAM	Control-plane permissions on the workspace resource; separate Prometheus and Loki data-plane permissions for ingest and query.

Older documentation referred to Prometheus tenants. That model is replaced by Observability workspaces. Use workspace endpoints and IAM policies going forward.

Documentation

Getting started

Create a workspace and send your first metrics

Workspaces

Lifecycle, endpoints, retention, and isolation

Metrics remote write

Configure Prometheus and Operator

Logs

Push and query logs with Loki APIs

Alerting

Rules, Alertmanager, and mimirtool

Best practices

Cardinality, cost, and retention

Quick start

Create a workspace in the console under Observability → Workspaces, or via POST /v1/observability/workspaces.
Wait until status is ready, then copy the remote write and push URLs from the overview.
Grant a service account Prometheus remote-write (and optionally Loki push) permissions plus the required OIDC scopes.
Point your collector at the workspace URLs (the path already includes the workspace ID).
Query metrics or logs from the console, Grafana, or the gateway APIs.

See Getting started for a full walkthrough.

Pricing and retention

Pricing is usage-based (for example metric samples and log volume). Current rates are on the pricing page. Configure retentionDays to match operational and compliance needs; longer retention increases storage cost.