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
      • 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
  • Install or uninstall a StackPack
  • StackPack instances
  • Upgrade a StackPack
  • New minor StackPack version
  • New major StackPack version
  • Locked configuration items
  1. Self-hosted setup
  2. Configure SUSE Observability

Stackpacks

SUSE Observability Self-hosted v5.1.x

PreviousE-mail notificationsNextAdvanced

Last updated 7 months ago

Overview

StackPacks extend SUSE Observability functionality and offer automated integration with external systems. They can be easily installed and uninstalled from the StackPacks page in SUSE Observability.

There are two types of StackPack - Add-ons and Integrations. The available StackPack add-ons and integrations can be found on the StackPacks page in the SUSE Observability UI.

Install or uninstall a StackPack

StackPacks can be installed and uninstalled from the StackPacks page in SUSE Observability. Full instructions to install and uninstall the StackPack are provided.

Note that:

  • A StackPack may require manual installation steps or configuration of the external system. Please read the instructions provided carefully.

  • When a StackPack or StackPack instance is uninstalled, all data received via the StackPack (instance) will be removed from SUSE Observability.

  • Any (manual) configuration or installation of StackPack components in an external system may need to be uninstalled separately.

StackPack instances

Some StackPacks allow you to connect to multiple accounts on an external system. Each account is configured in a separate instance of the StackPack.

For example, the AWS StackPack can connect to multiple AWS accounts and combine information from all accounts in SUSE Observability. For each account, a separate SUSE Observability instance is configured with the information required to receive data from that AWS account.

Upgrade a StackPack

When a StackPack is upgraded, any changes made to configuration items from that StackPack will be overwritten. For details, see .

If a new StackPack version is available, an alert will be displayed on the SUSE Observability UI StackPack page and you will have the option to view the upgrade details and read the release notes. If the new release is a minor upgrade from the currently installed version, you can also upgrade the StackPack from here.

New minor StackPack version

To upgrade to a new minor version of a StackPack, click UPGRADE NOW on the StackPack page in the SUSE Observability UI.

New major StackPack version

Continue using changes made to customized StackPack configuration items after upgrade:

  1. Before you upgrade, export each customized item:

    • Go to the Settings page in the SUSE Observability UI.

    • Click Export in the ... menu for each customized item.

  2. Upgrade the StackPack (uninstall and reinstall).

  3. Change the name and identifier for each exported item:

    • Open the export file in a text editor.

    • Edit the top-level name and identifier fields.

    • Save the export.

  4. The customized configuration items will now be available in SUSE Observability and can be copied to the newly installed StackPack configuration items.

Locked configuration items

StackPacks contain configuration information for SUSE Observability that's installed when the StackPack (instance) is installed. Amongst other things, this could be component templates, functions, component actions and views. When a StackPack is upgraded, the configuration items installed by the previous version of the StackPack will be overwritten by those from the newer StackPack. This means that any manual change made to these configuration items will be overwritten when the StackPack is upgraded.

To prevent a user from making changes to configuration items installed by a StackPack that will be overwritten on upgrade, these configuration items are locked by default. This means that they're protected from being changed by the user and must explicitly be unlocked before they can be changed.

Note that all StackPack configuration items will be overwritten when you upgrade. To continue using any changes made to these, choose to KEEP the existing configuration when you upgrade the StackPack. For details, see .

When a StackPack is upgraded, any changes made to configuration items from that StackPack will be overwritten. For details, see .

To upgrade to a new major version of a StackPack, the StackPack.

the updated export file(s).

You can . Note that the lock status of configuration items won't be exported as part of a configuration backup.

🚀
make a back-up of configuration items
locked configuration items
locked configuration items
locked configuration items
uninstall and reinstall
Import