StackState architecture
StackState Self-hosted v5.1.x
StackState is built for scale and runs on Kubernetes in your cloud or data center.
In most cases, a single Host Agent is installed on the StackState server to provide Agent-less integration with APIs from multiple sources. Data is gathered and received by one or more Agents and delivered at the Receiver API. From there, all data is put on Kafka. The data is processed by microservices and ends up as Topology in our versioned graph database, called StackGraph. Traces, and some telemetry data, are temporarily stored in Elasticsearch.
A Script and Query Language provides access to all dimensions of the 4T Data Model. They're also used by our own AI Microservices to interface with the 4T Data Model.
REST APIs are available for external services and are also used by our Command Line Interface. Every user interface is kept up to date by WebSocket APIs.
Notifications, tickets, webhooks, and API calls are just a few examples of output data sources to let you respond to situations you observe in StackState.
StackState architecture and data flow
StackState integrates with external systems to retrieve data. Integrations use StackState Agent or an associated integration StackPack.
StackState configuration and topology data are stored in the StackGraph database.
The StackState User Interface visualizes all collected data in perspectives. You can also customize your instance of StackState here by adding automation steps, such as event handlers and output to external systems.
You can optionally install the StackState CLI to control your StackState instance directly from the command line.
StackState Agent V2 is open source and available on GitHub:
The StackPacks listed below are open source and available on GitHub:
Last modified 1mo ago