LogoLogo
StackState.comDownloadSupportExplore playground
SUSE Observability
SUSE Observability
  • SUSE Observability docs!
  • Docs for all SUSE Observability products
  • 🚀Get started
    • Quick start guide
    • SUSE Observability walk-through
    • SUSE Rancher Prime
      • Air-gapped
      • Agent Air-gapped
    • SUSE Cloud Observability
  • 🦮Guided troubleshooting
    • What is guided troubleshooting?
    • YAML Configuration
    • Changes
    • Logs
  • 🚨Monitors and alerts
    • Monitors
    • Out of the box monitors for Kubernetes
    • Notifications
      • Configure notifications
      • Notification channels
        • Slack
        • Teams
        • Webhook
        • Opsgenie
      • Troubleshooting
    • Customize
      • Add a monitor using the CLI
      • Derived State monitor
      • Dynamic Threshold monitor
      • Override monitor arguments
      • Write a remediation guide
  • 📈Metrics
    • Explore Metrics
    • Custom charts
      • Adding custom charts to components
      • Writing PromQL queries for representative charts
      • Troubleshooting custom charts
    • Advanced Metrics
      • Grafana Datasource
      • Prometheus remote_write
      • OpenMetrics
  • 📑Logs
    • Explore Logs
    • Log Shipping
  • 🔭Traces
    • Explore Traces
  • 📖Health
    • Health synchronization
    • Send health data over HTTP
      • Send health data
      • Repeat Snapshots JSON
      • Transactional Increments JSON
    • Debug health synchronization
  • 🔍Views
    • Kubernetes views
    • Custom views
    • Component views
    • Explore views
    • View structure
      • Overview perspective
      • Highlights perspective
      • Topology perspective
      • Events perspective
      • Metrics perspective
      • Traces perspective
      • Filters
      • Keyboard shortcuts
    • Timeline and time travel
  • 🕵️Agent
    • Network configuration
      • Proxy Configuration
    • Using a custom registry
    • Custom Secret Management
      • Custom Secret Management (Deprecated)
    • Request tracing
      • Certificates for sidecar injection
  • 🔭Open Telemetry
    • Overview
    • Getting started
      • Concepts
      • Kubernetes
      • Kubernetes Operator
      • Linux
      • AWS Lambda
    • Open telemetry collector
      • Sampling
      • SUSE Observability OTLP APIs
    • Instrumentation
      • Java
      • Node.js
        • Auto-instrumentation of Lambdas
      • .NET
      • SDK Exporter configuration
    • Troubleshooting
  • CLI
    • SUSE Observability CLI
  • 🚀Self-hosted setup
    • Install SUSE Observability
      • Requirements
      • Kubernetes / OpenShift
        • Kubernetes install
        • OpenShift install
        • Alibaba Cloud ACK install
        • Required Permissions
        • Override default configuration
        • Configure storage
        • Exposing SUSE Observability outside of the cluster
      • Initial run guide
      • Troubleshooting
        • Advanced Troubleshooting
        • Support Package (Logs)
    • Configure SUSE Observability
      • Slack notifications
      • E-mail notifications
      • Stackpacks
      • Advanced
        • Analytics
    • Release Notes
      • v2.0.0 - 11/Sep/2024
      • v2.0.1 - 18/Sep/2024
      • v2.0.2 - 01/Oct/2024
      • v2.1.0 - 29/Oct/2024
      • v2.2.0 - 09/Dec/2024
      • v2.2.1 - 10/Dec/2024
      • v2.3.0 - 30/Jan/2025
      • v2.3.1 - 17/Mar/2025
      • v2.3.2 - 22/Apr/2025
      • v2.3.3 - 07/May/2025
    • Upgrade SUSE Observability
      • Migration from StackState
      • Steps to upgrade
      • Version-specific upgrade instructions
    • Uninstall SUSE Observability
    • Air-gapped
      • SUSE Observability air-gapped
      • SUSE Observability Kubernetes Agent air-gapped
    • Data management
      • Backup and Restore
        • Kubernetes backup
        • Configuration backup
      • Data retention
      • Clear stored data
    • Security
      • Authentication
        • Authentication options
        • Single password
        • File-based
        • LDAP
        • Open ID Connect (OIDC)
          • Microsoft Entra ID
        • KeyCloak
        • Service tokens
        • Troubleshooting
      • RBAC
        • Role-based Access Control
        • Permissions
        • Roles
        • Scopes
      • Self-signed certificates
      • External secrets
  • 🔐Security
    • Service Tokens
    • API Keys
  • ☁️SaaS
    • User Management
  • Reference
    • SUSE Observability Query Language (STQL)
    • Chart units
    • Topology Identifiers
Powered by GitBook
LogoLogo

Legal notices

  • Privacy
  • Cookies
  • Responsible disclosure
  • SOC 2/SOC 3
On this page
  • Overview
  • Kubernetes and OpenShift
  • Supported versions
  • Resource requirements
  • Storage
  • Ingress
  • Namespace resource limits
  • Client (browser)
  1. Self-hosted setup
  2. Install SUSE Observability

Requirements

SUSE Observability Self-hosted

PreviousInstall SUSE ObservabilityNextKubernetes / OpenShift

Last updated 1 month ago

Overview

Requirements for can be found at the bottom of the page.

Kubernetes and OpenShift

Supported versions

SUSE Observability can be installed on a Kubernetes or OpenShift cluster using the Helm charts provided by SUSE Observability. These Helm charts require Helm v3.x to install and are supported on:

  • Kubernetes: 1.21 to 1.30

  • OpenShift: 4.9 to 4.14

Resource requirements

There are different installation options available for SUSE Observability. It is possible to install SUSE Observability either in a High-Availability (HA) or single instance (non-HA) setup. The non-HA setup is recommended for testing purposes only. For production environments, it is recommended to install SUSE Observability in a HA setup. For a standard, production, deployment, the SUSE Observability Helm chart will deploy many services in a redundant setup with 3 instances of each service.

In the table below you can find the resource requirements for the different installation options. For the HA setup you can find different installation profiles depending on the size of the environment being observed. An observed node in this sizing table is taken to be 4 vCPUs and 16GB of memory, our default node size. If nodes in your observed cluster are bigger, they can count for multiple default nodes, so a node of 12vCPU and 48GB counts as 3 default nodes under observation when picking a profile.

trial
10 non-HA
20 non-HA
50 non-HA
100 non-HA
150 HA
250 HA
500 HA
4000 HA

CPU Requests

7.5

7.5

10.5

15

25

49

62

86.5

210

CPU Limits

16

16

21.5

30.5

50

103

128

176

278

Memory Requests

25.5Gi

25.5Gi

31Gi

35Gi

54Gi

129Gi

146Gi

164.5Gi

259Gi

Memory Limits

26Gi

26Gi

31.5Gi

36Gi

54Gi

133.5Gi

150Gi

168.5Gi

320Gi

The requirement shown for profile represent the total amount of resources needed to run the Suse Observability server. To ensure that all different services of Suse Observability server can be allocated:

  • For non-HA installations the recommended node size is 4VCPU, 8GB

  • For HA installations up to 500 nodes the min recommended node size is 8VCPU, 16GB

  • For 4000 nodes HA installations the min recommended node size is 16VCPU, 32GB

These are just the upper and lower bounds of the resources that can be consumed by SUSE Observability in the different installation options. The actual resource usage will depend on the features used, configured resource limits and dynamic usage patterns, such as Deployment or DaemonSet scaling. For our Self-hosted customers, we recommend to start with the default requirements and monitor the resource usage of the SUSE Observability components.

The minimum requirements do not include spare CPU/Memory capacity to ensure smooth application rolling updates.

For installation of SUSE Observability please follow the installation instructions provided below:

Storage

SUSE Observability uses persistent volume claims for the services that need to store data. The default storage class for the cluster will be used for all services unless this is overridden by values specified on the command line or in a values.yaml file. All services come with a pre-configured volume size that should be good to get you started, but can be customized later using variables as required.

For production environments, NFS is not recommended and supported for storage provisioning in SUSE Observability due to the potential risk of data corruption.

For our different installation profiles, the following are the defaulted storage requirements:

trial
10 non-HA
20 non-HA
50 non-HA
100 non-HA
150 HA
250 HA
500 HA
4000 HA

Retention (days)

3

30

30

30

30

30

30

30

30

Storage requirement

125GB

280GB

420GB

420GB

600GB

2TB

2TB

2.5TB

5.5TB

The storage estimates presented take into account a default of 14 days of retention for NONHA and 1 month for HA installations. For short lived test instances the storage sizes can be further reduced.

Ingress

By default, the SUSE Observability Helm chart will deploy a router pod and service. This service's port 8080 is the only entry point that needs to be exposed via Ingress. You can access SUSE Observability without configuring Ingress by forwarding this port:

kubectl port-forward service/<helm-release-name>-stackstate-k8s-router 8080:8080 --namespace stackstate

When configuring Ingress, make sure to allow for large request body sizes (50MB) that may be sent occasionally by data sources like the SUSE Observability Agent or the AWS integration.

Namespace resource limits

It isn't recommended to set a ResourceQuota as this can interfere with resource requests. The resources required by SUSE Observability will vary according to the features used, configured resource limits and dynamic usage patterns, such as Deployment or DaemonSet scaling.

Client (browser)

To use the SUSE Observability GUI, you must use one of the following web browsers:

  • Chrome

  • Firefox

For more details on the defaults used, see the page .

For more details on configuring Ingress, have a look at the page .

If it's necessary to set a ResourceQuota for your implementation, the namespace resource limit should be set to match the node .

🚀
Kubernetes
OpenShift
Configure storage
Configure Ingress docs
SUSE Observability client (browser)
sizing requirements