LogoLogo
StackState.comDownloadSupportExplore playground
StackState v5.1
StackState v5.1
  • Welcome to the StackState docs!
  • StackState self-hosted v5.1 docs
  • Getting Started
  • 🚀Setup
    • Install StackState
      • Requirements
      • Kubernetes / OpenShift
        • Kubernetes install
        • OpenShift install
        • Required Permissions
        • Non-high availability setup
        • Override default configuration
        • Configure storage
        • Configure Ingress
        • Install from custom image registry
        • Migrate from Linux install
      • Linux
        • Before you install
        • Download
        • Install StackState
        • Install with production configuration
        • Install with development configuration
        • Install with POC configuration
        • Set up a reverse proxy
        • Set up TLS without reverse proxy
      • Initial run guide
      • Troubleshooting
    • Upgrade StackState
      • Steps to upgrade
      • Version specific upgrade instructions
      • StackPack versions
      • StackState release notes
    • StackState Agent
      • About StackState Agent V3
      • Docker
      • Kubernetes / OpenShift
      • Linux
      • Windows
      • Advanced Agent configuration
      • Use an HTTP/HTTPS proxy
      • Agent V1 (legacy)
      • Migrate Agent V1 to Agent V2
        • Linux
        • Docker
    • StackState CLI
      • CLI: sts
      • CLI: stac (deprecated)
      • Comparison between CLIs
    • Data management
      • Backup and Restore
        • Kubernetes backup
        • Linux backup
        • Configuration backup
      • Data retention
      • Clear stored data
  • 👤Use
    • Concepts
      • The 4T data model
      • Components
      • Relations
      • Health state
      • Layers, Domains and Environments
      • Perspectives
      • Anomaly detection
      • StackState architecture
    • StackState UI
      • Explore mode
      • Filters
      • Views
        • About views
        • Configure the view health
        • Create and edit views
        • Visualization settings
      • Perspectives
        • Topology Perspective
        • Events Perspective
        • Traces Perspective
        • Metrics Perspective
      • Timeline and time travel
      • Analytics
      • Keyboard shortcuts
    • Checks and monitors
      • Checks
      • Add a health check
      • Anomaly health checks
      • Monitors
      • Manage monitors
    • Problem analysis
      • About problems
      • Problem lifecycle
      • Investigate a problem
      • Problem notifications
    • Metrics
      • Telemetry streams
      • Golden signals
      • Top metrics
      • Add a telemetry stream
      • Browse telemetry
      • Set telemetry stream priority
    • Events
      • About events
      • Event notifications
      • Manage event handlers
    • Glossary
  • 🧩StackPacks
    • About StackPacks
    • Add-ons
      • Autonomous Anomaly Detector
      • Health Forecast
    • Integrations
      • About integrations
      • 💠StackState Agent V2
      • 💠AWS
        • AWS
        • AWS ECS
        • AWS X-ray
        • StackState/Agent IAM role: EC2
        • StackState/Agent IAM role: EKS
        • Policies for AWS
        • AWS (legacy)
        • Migrate AWS (legacy) to AWS
      • 💠Dynatrace
      • 💠Kubernetes
      • 💠OpenShift
      • 💠OpenTelemetry
        • About instrumentations
        • AWS NodeJS Instrumentation
        • Manual Instrumentation
          • Prerequisites
          • Tracer and span mappings
          • Relations between components
          • Span health state
          • Merging components
          • Code examples
      • 💠ServiceNow
      • 💠Slack
      • 💠Splunk
        • Splunk
        • Splunk Events
        • Splunk Health
        • Splunk Metrics
        • Splunk Topology
      • 💠VMWare vSphere
      • Apache Tomcat
      • Azure
      • Cloudera
      • Custom Synchronization
      • DotNet APM
      • Elasticsearch
      • Humio
      • Java APM
      • JMX
      • Logz.io
      • MySQL
      • Nagios
      • OpenMetrics
      • PostgreSQL
      • Prometheus
      • SAP
      • SCOM
      • SolarWinds
      • Static Health
      • Static Topology
      • Traefik
      • WMI
      • Zabbix
    • Develop your own StackPacks
  • 🔧Configure
    • Topology
      • Component actions
      • Identifiers
      • Topology naming guide
      • Topology sources
      • Create a topology manually
      • Configure topology synchronizations
      • Enable email event notifications
      • Send topology data over HTTP
      • Set the topology filtering limit
      • Use a proxy for event handlers
      • Use tags
      • Tune topology synchronization
      • Debug topology synchronization
    • Telemetry
      • Add telemetry during topology synchronization
      • Data sources
        • Elasticsearch
        • Prometheus mirror
      • Send events over HTTP
      • Send metrics data over HTTP
      • Set the default telemetry interval
      • Debug telemetry synchronization
    • Traces
      • Set up traces
      • Advanced configuration for traces
    • Health
      • Health synchronization
      • Send health data over HTTP
        • Send health data
        • Repeat Snapshots JSON
        • Repeat States JSON
        • Transactional Increments JSON
      • Debug health synchronization
    • Anomaly Detection
      • Export anomaly feedback
      • Scale the AAD up and down
      • The AAD status UI
    • Security
      • Authentication
        • Authentication options
        • File based
        • LDAP
        • Open ID Connect (OIDC)
        • KeyCloak
        • Service tokens
      • RBAC
        • Role-based Access Control
        • Permissions
        • Roles
        • Scopes
        • Subjects
      • Secrets management
      • Self-signed certificates
      • Set up a security backend for Linux
      • Set up a security backend for Windows
    • Logging
      • Kubernetes logs
      • Linux logs
      • Enable logging for functions
  • 📖Develop
    • Developer guides
      • Agent checks
        • About Agent checks
        • Agent check API
        • Agent check state
        • How to develop Agent checks
        • Connect an Agent check to StackState
      • Custom functions and scripts
        • StackState functions
        • Check functions
        • Component actions
        • Event handler functions
        • ID extractor functions
        • Mapping functions
        • Monitor functions
        • Propagation functions
        • Template functions
        • View health state configuration functions
      • Custom Synchronization StackPack
        • About the Custom Synchronization StackPack
        • How to customize elements created by the Custom Synchronization StackPack
        • How to configure a custom synchronization
      • Integrate external services
      • Mirroring Telemetry
      • Monitors
        • Create monitors
        • Monitor STJ file format
      • StackPack development
        • How to create a StackPack
        • Packaging
        • How to get a template file
        • How to make a multi-instance StackPack
        • Prepare a multi-instance provisioning script
        • Upload a StackPack file
        • Prepare a shared template
        • Customize a StackPack
        • Prepare instance template files
        • Prepare a StackPack provisioning script
        • Resources in a StackPack
        • StackState Common Layer
      • Synchronizations and templated files
    • Reference
      • StackState OpenAPI docs
      • StackState Template JSON (STJ)
        • Using STJ
        • Template functions
      • StackState Markup Language (STML)
        • Using STML
        • STML Tags
      • StackState Query Language (STQL)
      • StackState Scripting Language (STSL)
        • Scripting in StackState
        • Script result: Async
        • Script result: Streaming
        • Time in scripts
        • Script APIs
          • Async - script API
          • Component - script API
          • HTTP - script API
          • Prediction - script API
          • StackPack - script API
          • Telemetry - script API
          • Time - script API
          • Topology - script API
          • UI - script API
          • View - script API
    • Tutorials
      • Create a simple StackPack
      • Push data to StackState from an external system
      • Send events to StackState from an external system
      • Set up a mirror to pull telemetry data from an external system
Powered by GitBook
LogoLogo

Legal notices

  • Privacy
  • Cookies
  • Responsible disclosure
  • SOC 2/SOC 3
On this page
  • Overview
  • Setup
  • Prerequisites
  • Install
  • Configure
  • Status
  • Upgrade
  • Integration details
  • REST API endpoints
  • Data retrieved
  • StackState views
  • Component actions
  • Open source
  • Troubleshooting
  • Uninstall
  • Release notes
  • See also
  1. StackPacks
  2. Integrations

SolarWinds

StackState Self-hosted v5.1.x

PreviousSCOMNextStatic Health

Last updated 1 year ago

Overview

The SolarWinds StackPack allows near real time synchronization between SolarWinds Orion (SolarWinds) and StackState. When the integration is enabled, SolarWinds nodes, interfaces and connections will be added to the StackState topology as components and relations. In addition, health status is applied to the components in StackState.

SolarWinds is a .

  • Nodes, interfaces and connections are retrieved from the SolarWinds instance.

  • Node and interface Health status is retrieved from the SolarWinds instance and translated to StackState values.

  • StackState translates incoming nodes, interfaces and connections into topology components and relations.

Setup

Prerequisites

To set up the SolarWinds integration you will need to have:

    • The lowest access level is sufficient.

    • The user must not have any account limitations set that block access to nodes intended to be retrieved.

  • A SolarWinds administrator needs to be available to add custom node properties.

Additionally, for some optional features you will need:

  • To see relations between components, a layer 3 network device is required.

Install

Install the SolarWinds StackPack from the StackState UI StackPacks > Integrations screen. You will need to enter the following details:

  • SolarWinds Instance URL: The SolarWinds instance URL from which topology data will be collected.

  • SolarWinds Instance Name: The user-defined name of the SolarWinds account shown in configurations such as views.

Configure

To enable the SolarWinds check and begin collecting data from SolarWinds, add the following configuration to StackState Agent V3:

  1. Edit the Agent integration configuration file /etc/stackstate-agent/conf.d/solarwinds.d/conf.yaml to include details of your SolarWinds instance:

    • url - the REST API URL, uses HTTPS protocol for communication. This should be a hostname or IP, it should not include the prefix https://.

    init_config:
    
    instances:
      - url: <instance_name.solarwinds.localdomain>
        username: <instance_username>
        password: <instance_password>
        solarwinds_domain: <instance_domain>  # A SolarWinds custom property
        solarwinds_domain_values:  # A list of values used by the solarwinds_domain
          - <instance_domain_value_1>
          - <instance_domain_value_2>
          - <instance_domain_value_n>
        # min_collection_interval: 30 # use in place of collection_interval for Agent V2.14.x or earlier 
        collection_interval: 30
  2. Set the following filters:

    • solarwinds_domain - The name of a SolarWinds custom property that will be used to select nodes from SolarWinds to include in the StackState dataset.

    • solarwinds_domain_values - A list of values used by the SolarWinds custom property specified in solarwinds_domain. Used to select the correct nodes for inclusion. Any node in SolarWinds that has one of these values set will be included in the data collection. Each value in this list will be represented as a separate domain in StackState.

  3. Once the Agent has restarted, wait for data to be collected from SolarWinds and sent to StackState.

Status

To check the status of the SolarWinds integration, run the status subcommand and look for SolarWinds under Running Checks:

sudo stackstate-agent status

Upgrade

Integration details

REST API endpoints

The SolarWinds user configured in StackState must have read access to the SolarWinds API (default for all user accounts). No additional authorization needs to be set for this account in the SolarWinds system.

Data retrieved

Events

The SolarWinds check doesn't retrieve any event data.

Metrics

The SolarWinds check doesn't retrieve any metrics data.

Topology

The SolarWinds server can contain different modules suitable for data retrieval by the StackState SolarWinds integration.

  • Network Performance Monitor (NPM) module - provides information about nodes, interfaces and layer-2 topology information for network devices. Layer-2 topology information for non-network devices is only available when the User Device Tracker (UDT) SolarWinds module is installed.

  • User Device Tracker (UDT) module - provides layer-2 topology information for non-network devices in the form of MAC-address tables from routers, switches and firewalls. This is added to the data retrieved from NPM, resulting in a complete topology for all SolarWinds nodes.

The SolarWinds check retrieves the following topology data from SolarWinds:

Data
Description

Components

Nodes and interfaces. In some cases, a SolarWinds node won't show any interfaces in the SolarWinds system. If UDT detects that such a node is connected to a device, a 'ghost' interface will be created in StackState to show the full topology.

Relations

NPM: Layer-2 topology information from network devices. UDT: Layer-2 topology information connecting generic nodes to network devices

Health

The SolarWinds check retrieves the health status from nodes and interfaces and translates these statuses to StackState statuses:

SolarWinds Health status
StackState Health state

Up

CLEAR

External

CLEAR

Unmanaged

CLEAR

Unreachable

CLEAR

Shutdown

CLEAR

Warning

DEVIATING

Unknown

DEVIATING

Down

CRITICAL

Critical

CRITICAL

Traces

The SolarWinds check doesn't retrieve any trace data.

StackState views

When the SolarWinds integration is enabled, the following SolarWinds specific views are available in StackState:

  • Node Details

  • Interface Details

Component actions

To support component actions from StackState, the SolarWinds server needs to be accessible from the user's browser.

Open source

The code for the StackState SolarWinds StackPack and check are open source and available on GitHub:

Troubleshooting

Uninstall

To uninstall the SolarWinds StackPack and disable the Dynatrace check:

  1. Go to the StackState UI StackPacks > Integrations > SolarWinds screen and click UNINSTALL.

    • All SolarWinds specific configuration will be removed from StackState.

  2. Remove or rename the Agent integration configuration file, for example:

     mv solarwinds.d/conf.yaml solarwinds.d/conf.yaml.bak

Release notes

See also

Agent V3 connects to the configured (default via TCP port 17778).

Agent V3 pushes to StackState.

installed on a machine that can connect to both SolarWinds (default via TCP port 17778) and StackState.

A running SolarWinds instance with correctly configured Network Performance Monitor (NPM) and User Device Tracker (UDT) modules. For details see .

A SolarWinds user with access to the required .

To support from StackState, the SolarWinds server needs to be accessible from the user's browser.

user - a SolarWinds user with access to the required .

password - use to store passwords outside the configuration file.

to apply the configuration changes.

When a new version of the SolarWinds StackPack is available in your instance of StackState, you will be prompted to upgrade in the StackState UI on the page StackPacks > Integrations > SolarWinds. For an overview of recent StackPack updates, check the shipped with each StackState release.

For considerations and instructions on upgrading a StackPack, see .

Refer to the SolarWinds product documentation for details on how to .

The configured collection_interval will be used as the . Make sure that the value set for the collection_interval matches the time that the check will take to run.

Links to SolarWinds detail dashboards are created as attached to SolarWinds components. This allows users to easily access more information from SolarWinds when needed.

SolarWinds StackPack:

SolarWinds check:

Troubleshooting steps for any known issues can be found in the .

to apply the configuration changes.

The are available on GitHub.

🧩
StackState Agent V3
secrets management
StackPack versions
Manage Orion Web Console user accounts in the Orion Platform (documentation.solarwinds.com)
https://github.com/StackVista/stackpack-solarwinds
https://github.com/StackVista/stackstate-agent-integrations/tree/master/solarwinds
StackState support Knowledge base
SolarWinds StackPack release notes
StackState
Secrets management
SolarWinds StackPack (github.com)
StackState Agent integrations - SolarWinds (github.com)
Manage Orion Web Console user accounts in the Orion Platform (documentation.solarwinds.com)
SolarWinds API
retrieved data
retrieved topology data
API endpoints
component actions
SolarWinds API endpoints
how to upgrade a StackPack
component actions
Restart StackState Agent V3
Restart StackState
StackState curated integration
repeat_interval for the health synchronization
Data flow