Skip to content
Products
Platform
Developer Tools
Portal

Observability

STACKIT Observability is a fully managed monitoring and analysis service that brings together metrics, logs and traces in one place. Based on leading open-source tools like Grafana, Prometheus, Thanos, Loki and Tempo, it enables you to visualize, analyze and alert on telemetry data effortlessly.

Getting Started

Content

Basics

Understand the basic architecture of STACKIT Observability, learn about key features and how to use Observability effectively.

Getting started

Create your first Observability instance. Follow the guides to build a working setup and connect in minutes.

How-tos

Manage instances, users, and backups. Connect with various tools such as Cloud Foundry and Terraform.

Reference

Find API documentation, CLI commands and an overview of service plans.

FAQ

Quickly find answers to frequently asked questions about STACKIT Observability.

Release notes

Discover what's new in Observability, including added features, bug fixes and deprication notices.

Release notes

Section titled “Release notes”
  • deprecated

    Default Grafana admin deprecation

    Section titled “Default Grafana admin deprecation”

    We would like to inform you that the Observability default Grafana admin user, created during instance provisioning, is now deprecated and will be removed on January 11, 2027, if the credentials have not been changed. From this date on, also the creation of a default admin user for new instances will no longer be supported.

    For security reasons, we recommend removing this default user right now and using STACKIT SSO (or your own SSO provider) instead. More information about Grafana SSO can be found in the Configure Grafana Access documentation. To remove this default user, we have introduced a new attribute in the Observability API instance update endpoint and a new button in the Portal.

    Additionally, you can already decide whether the default admin user should be created during provisioning. We have added a corresponding attribute in the Observability API instance creation endpoint as well as a new dialog in the Portal provisioning flow.

    Please be aware that once the default admin user is removed or the creation of it is skipped, it cannot be recreated via the API or the Portal. However, it will still be possible to manually create Basic Authentication users in the Grafana UI.

    Another benefit of removing the default admin is that it frees up a user slot. This allows you to utilize the full user limit defined in your plan (e.g. all 5 slots of the smallest plan) for real users via SSO.

  • announcement

    Grafana Administrative Access via SSO

    Section titled “Grafana Administrative Access via SSO”

    We would like to inform you that it is now possible to gain full administrative access to Grafana through Role-Based Access Control (RBAC) via Single Sign-On (SSO). Previously, this was only possible via a Basic Authentication admin user created during instance provisioning.

    To use this new administrative access, you have two options:

    • STACKIT SSO (enabled by default): We introduced a new permission: argus.grafana.server-administrate. This permission is included in the Observability Grafana Server Admin and Owner roles.

    • Custom SSO: If you wish to configure Grafana Server admin privileges through your own SSO provider, we have introduced a new attribute, allowAssignGrafanaAdmin, to the Observability API grafana-config endpoint to handle this configuration. For detailed information on the API itself, see the Observability API documentation .

    More information about the default Grafana admin, Grafana SSO and other access methods can be found in the Configure Grafana Access documentation.

  • announcement

    Alertmanager now supports Google Chat webhooks

    Section titled “Alertmanager now supports Google Chat webhooks”

    We are happy to announce that our Observability Alertmanager now supports sending notifications to Google Chat spaces via webhooks.

    The integration can be configured through the Observability API. For an example on how to set it up, refer to the Observability documentation. For detailed information on the API itself, see the Observability API documentation .

Observability Release notes