Thalassa Cloud Thalassa Cloud
Console Sign up for free

Managed Logging

Centralised logs on a Loki-compatible backend. Push from Promtail, Grafana Alloy, Fluent Bit, or OpenTelemetry, then query with LogQL.

Open the console Documentation

Managed Logging with Loki

Every Observability workspace includes a Loki-compatible logs backend. You keep your existing agents and LogQL queries. Thalassa Cloud stores and serves the logs, in the same region and project as your metrics, under European jurisdiction.

Query logs with LogQL

Send log streams to the workspace push URL and query them with LogQL from the console, Grafana, or the gateway API. Use stable, low-cardinality labels such as app, namespace, and level. Keep high-cardinality detail in the log line.

Ingest from your collector

Any agent that speaks the Loki push API or OTLP logs can write to the workspace. Authenticate with an OIDC bearer token from a service account that has Loki push permission on that workspace.

Same workspace as Managed Prometheus

Creating a workspace enables both metrics and logs. Retention applies to both backends. IAM stays on the Thalassa Cloud identity model, with separate data-plane permissions for Loki push and query.

Ready to centralise your logs?

Create an Observability workspace, copy the Loki push URL, and point your agent at it. Query logs in the console or from Grafana without running Loki yourself.

Open the console Logging documentation

Quick start

# Grafana Alloy — push to the workspace Loki endpoint
loki.write "thalassa" {
  endpoint {
    url = "https://loki.<region>.thalassa.cloud/workspace/obsw-<id>/loki/api/v1/push"
    oauth2 {
      client_id     = env("THALASSA_CLIENT_ID")
      client_secret = env("THALASSA_CLIENT_SECRET")
      token_url     = "https://api.thalassa.cloud/oidc/token"
    }
  }
}

# Query with LogQL
curl -G -H "Authorization: Bearer $TOKEN" \
  --data-urlencode 'query={app="api"} |= "error"' \
  "https://loki.<region>.thalassa.cloud/workspace/obsw-<id>/loki/api/v1/query_range"