SUSE Observability Self-Hosted

Commercial observability platform installed by Helm into a dedicated customer Kubernetes cluster.

  • AWS
  • Azure
  • Google Cloud
  • Alibaba Cloud
Customer-operated Servers / containers Commercial Only

6 sources checked by an editor on · Product website ↗

Deployment terms: BYOC · control plane · data plane · private offer

· Open requirements shortlist · Estimate operating costs

Compare this listing with another →

What lands where

  1. Supplied by

    Vendor or project

    SUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration

  2. Operated by

    Your team

    Customer manages the Kubernetes cluster, persistent storage, sizing, ingress, certificates, backups, upgrades and monitored-system access.

Deployment boundaries by provider

Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.

Install methodSUSE Observability server Helm chart on EKS, AKS, GKE or Alibaba ACK, with provider-specific storage configuration
InfrastructureServers / containers
SUSE Observability runs persistent stateful services on a dedicated Kubernetes cluster with durable storage and substantial capacity requirements.
Licensing modelCommercial Only
The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.
LicenseCommercial SUSE Observability self-hosted subscription and license key required.

Buyer diligence

Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.

How to read these facts

Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.

12 of 12 fields researched (100%) · 7 documented · 5 unresolved. Evidence coverage is not a feature score.

Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery

The reviewed server guide supplies a licensed Helm repository, not a cloud-provider billing offer. A current Marketplace offer for this self-hosted server was not established.

Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility

The self-hosted SUSE subscription and Helm installation do not establish an eligible offer or contract-specific cloud commitment treatment.

Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Single sign-on
AvailableEvidence and scope for Single sign-on

The server supports OIDC, including Rancher and Keycloak configurations, or LDAP as the selected authentication mechanism. Only one mechanism is configured at a time; map external groups to the intended server roles.

SUSE Observability server authentication · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

SCIM provisioning
Not confirmedEvidence and scope for SCIM provisioning

The server supports selected OIDC/LDAP authentication and role mappings, but a SCIM provisioning endpoint and lifecycle operations were not established.

Reviewed public evidence for SUSE Observability Self-Hosted; unresolved within this edition/deployment · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Compliance attestations
Not confirmedEvidence and scope for Compliance attestations

The reviewed SUSE Observability Self-Hosted material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage.

Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited · Source ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Security controls
DocumentedEvidence and scope for Security controls

The default shared administrator password is explicitly not production-ready. Configure an external identity method, limit administrator roles and review RBAC before production use.

Server identity and role hardening; not monitored-cluster agent settings · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Air-gapped operation
AvailableEvidence and scope for Air-gapped operation

SUSE supplies an air-gapped server installation workflow: download the charts/images, transfer them to the isolated network, load a private registry and apply the licensed Helm configuration. Configure registry credentials and preserve the chosen sizing profile.

Licensed self-hosted Observability server, not agents only · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC

The server installer uses the SUSE Observability Helm repository, licence key and a selected sizing profile. It provisions the Observability backend on EKS/AKS/GKE; agent installation is a separate workflow.

Self-hosted server Helm installation · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing

The smallest HA profile (150-ha) requests 49.8 CPU and 130.7 GiB RAM across at least three workers, with 2,595 GiB default storage. It is based on observed default-node capacity, not users; spare rolling-update capacity is additional.

Observability 150-ha resource requests, not CPU limits or physical-node counts · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

License pricing
DocumentedEvidence and scope for License pricing

The self-hosted SUSE Observability product requires a commercial subscription and license key. SUSE Cloud Observability is a separate hosted offering.

SUSE Observability Self-Hosted: software entitlement and edition boundary; infrastructure and operating costs are separate · Source ↗ · Reviewed 2026-11-17

Documented · Editor reviewed.

Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate

Illustrative priced infrastructure subtotal: USD 3,656.44/month. Three 32-vCPU/128-GiB workers price the minimum 150-ha profile, plus its 2,595 GiB default PVC request and 150 GB boot allowance. For this illustration each requested GiB is budgeted as one EBS billing GB. This is not a complete operating-cost estimate or a validated capacity/SLA claim.

Smallest documented HA profile, not a conversion from 100 users/1 TB into monitored-node capacity. It exceeds a 1 TB storage allowance before boot volumes. 96 vCPU/384 GiB fleet leaves nominal CPU/memory capacity after one worker loss; scheduling, AZ/storage failover and rolling updates still need validation. · Source ↗ · Product topology/sizing basis ↗ · Current AWS documentation: us-east-1 gp3 capacity example ↗ · EBS performance and charging qualifications ↗ · EKS standard versus extended support pricing ↗ · Reviewed 2026-11-17

Sources checked — unresolved · Editor reviewed.

Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence

The self-hosted Helm chart v2.13.0 release notes are dated November 12, 2026. They list SUSE Observability 2.13.0, Values helper chart 1.4.13 (deprecated since 2.8.0), Agent 1.7.64 and CLI 3.9.0. Component versions are separate; apply every version-specific upgrade step from the installed version through 2.13.0, including the changed scheduling precedence.

Dated SUSE Observability self-hosted Helm release snapshot; the deprecated Values helper chart is not a universal installation requirement · Source ↗ · Reviewed 2026-11-18

Documented · Editor reviewed.

Scope & considerations

This entry covers the self-hosted server product, not SUSE Cloud Observability SaaS. Installation requires a license key, compatible Helm and Kubernetes versions, persistent storage and dedicated sizing. High-availability and non-high-availability profiles are not interchangeable after installation, so choose the production topology before deployment. SUSE Observability 2.13.0 includes authentication, disk, and backup fixes and requires the documented sequential upgrade path. Version 2.10 reached end of support on November 12, 2026; move through supported intermediate releases as required.

Category fit

Observability
Collects, correlates and visualizes Kubernetes topology, metrics, events and related operational signals in a customer-operated deployment.

Compare within Observability

  • AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
    • AWS
    Customer-operated · Commercial Only
  • Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
    • Google Cloud
    Customer-operated · Open Source / Open Core
  • Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
    • AWS
    • Azure
    • Google Cloud
    • Oracle Cloud
    Customer-operated · Open Source / Open Core
  • Datadog BYOC LogsDatadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · vendor control plane · Commercial Only
  • Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Commercial Only
  • Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
    • AWS
    • Azure
    • Google Cloud
    Customer-operated · Source Available
  • Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
    • AWS
    Customer-operated · Open Source / Open Core
  • Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
    • AWS
    • Azure
    • Google Cloud
    • Railway
    • Render
    Customer-operated · Open Source / Open Core

Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →

Installation outline

  1. Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
  2. Review the vendor's installation documentation, required permissions and outbound data flows.
  3. Deploy to a non-production environment; configure identity, networking and monitoring.
  4. Test backup recovery and upgrades before promoting to production.

Watch this listing with RSS

Evidence trail

Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.

  1. Deployment sourcesChecked
  2. Cloud deployment evidenceChecked

    The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.

    • SUSE Observability on EKS, AKS and GKE ↗ · AWS, Azure, Google Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      The server-installation guide explicitly covers the Observability server on EKS, AKS and GKE and supplies the Helm installation. The customer operates the dedicated server cluster, default storage class, persistent volumes and ingress; monitored-cluster agent integrations are separate.

    • SUSE Observability server installation on Alibaba ACK ↗ · Alibaba Cloud

      Vendor / upstream documentation · Reviewed 2026-11-17. Vendor support commitment: not assessed; confirm the selected release and contract.

      The server guide supplies ACK-specific Helm values for stateful backend PVCs, each at least 20 GiB. This is server deployment evidence, distinct from monitoring an ACK cluster with an agent. Apply the selected HA sizing profile and provider storage requirements.

  3. Infrastructure evidenceChecked
  4. Licensing evidenceChecked

Suggest a correction · Back to directory