Thalassa Prometheus Service
Thalassa Prometheus Service is a fully managed, serverless Prometheus compatible monitoring solution that provides a remote write endpoint, PromQL-compatible query API, and integrated Alertmanager. Install your own Prometheus (or Prometheus Operator) to collect metrics and forward them to our remote write endpoint for long-term storage, querying, and alerting.
The service includes a PromQL-compatible Query API that works with Grafana and other Prometheus-compatible visualization tools. For alerting, the integrated Ruler engine evaluates alert and recording rules using Prometheus-compatible APIs, while Alertmanager handles alert routing to notification channels including SMTP, webhooks, Slack, and Microsoft Teams.
You can manage rules and Alertmanager configuration through multiple methods: the Thalassa Cloud console, Mimirtool command-line interface, or directly via Prometheus-compatible APIs. This flexibility allows you to integrate with existing workflows and tools.
Info
Thalassa Prometheus Service is currently in Private Beta. Access may be limited—contact support for early access. The documentation is already made available to iterate upon during the private beta phase.
Thalassa Prometheus Service will be made Available in GA in January 2026.
Core Concepts
| Concept | Description |
|---|---|
| Remote Write | Endpoint that accepts metrics from Prometheus instances via the Prometheus remote write protocol. Your Prometheus instances forward collected metrics to this endpoint. |
| Query API | PromQL-compatible API for querying stored metrics. Compatible with Grafana and other Prometheus-compatible tools. |
| Alertmanager | Integrated Alertmanager service for routing alerts to notification channels (SMTP, webhooks, Slack, Teams). |
| Ruler | Alerting and recording rules engine that evaluates PromQL expressions and triggers alerts. |
| Retention | Configurable data retention period for stored metrics. |
| Samples | Pricing is based on the number of metric samples ingested (per 1,000 samples). |
Security
Security is built into the service with OIDC authentication integrated with Thalassa Cloud IAM, ensuring secure access to your metrics and alerting configuration. You can further restrict access by configuring IP ACLs to limit remote write requests to specific IP addresses or CIDR blocks. Rate limiting controls help manage throughput and prevent overload, while advanced conditional processing allows you to filter and transform metrics before they are stored.
Data Retention
Data retention is configurable, allowing you to store metrics for extended periods based on your compliance and analysis needs. The service uses a pay-per-use pricing model based on the number of metric samples ingested, calculated per 1,000 samples.
Documentation
Use Cases
Kubernetes Observability
Thalassa Prometheus Service is well-suited for organisations running Kubernetes clusters who want to use Prometheus Operator to collect cluster metrics and forward them to a managed remote write endpoint. The service also supports infrastructure observability use cases where you deploy Prometheus to collect metrics from virtual machines, network components, and storage systems.
Long term Storage
For application monitoring, you can forward application metrics from any Prometheus-compatible collector, enabling consistent metric collection across your entire stack. The service excels at centralized monitoring scenarios where you need to aggregate metrics from multiple Prometheus instances into a single queryable endpoint, simplifying metric management and reducing operational overhead.
The service provides long-term storage capabilities that extend beyond typical local Prometheus retention limits, making it ideal for compliance requirements, historical analysis, and capacity planning. By offloading storage and querying to the managed service, you can reduce the resource requirements of your local Prometheus instances while maintaining full access to historical metrics.
HA Alerting
High-availability (HA) alerting allows you to be alerted even if your own infrastructure becomes unavailable, or when one Availability zone is lost. Thalassa Prometheus Service supports HA remote write and deduplication, making it easy to implement resilient monitoring across distributed environments without losing alert coverage during upgrades or disruptions.
Quick Start
To get started with Thalassa Prometheus Service, create a Prometheus Tenant in your organisation through the Thalassa Cloud console (Observability -> Prometheus -> Create Tenant). Once enabled, retrieve the remote write endpoint URL and configure authentication credentials, which can be service account credentials or personal access tokens. Next, configure your Prometheus instance to forward metrics to the remote write endpoint by updating your Prometheus configuration file.
See our Getting Started page for detailed information.
Service Integrations
Thalassa Prometheus Service integrates with Thalassa Cloud IAM, using OIDC-based authentication to provide secure access to your metrics and alerting configuration. The service works particularly well with Kubernetes deployments using Prometheus Operator, as well as the OpenTelemetry Collector.
The service is compatible with any Prometheus instance via the standard Prometheus remote write protocol, allowing you to forward metrics from existing Prometheus deployments without requiring changes to your collection infrastructure.
References
- Prometheus Documentation — Official Prometheus documentation
- PromQL Guide — Prometheus Query Language reference
- Kubernetes Monitoring — Monitor Kubernetes clusters