How to install StackStorm on Ubuntu?

Use the provided installer script: curl -sSL https://stackstorm.com/packages/install.sh | bash -s -- --user=st2admin --password=Ch@ngeMe. Ensure you have a clean 64-bit Linux box meeting the system requirements outlined in the documentation.

StackStorm vs Ansible: which is better for automation?

StackStorm excels at event-driven orchestration and ChatOps for operational tasks like incident response, while Ansible is stronger for configuration management and ad-hoc executions. StackStorm can integrate Ansible actions within its workflows for hybrid use cases.

How to create a custom workflow in StackStorm?

Define workflows using YAML or Python in a pack, specifying action sequences, conditions, and data passing. The README mentions workflow orchestration as a key feature, and documentation provides examples for stitching actions together.

What tools does StackStorm integrate with for monitoring?

StackStorm has integration packs for monitoring tools like Nagios, Sensu, and New Relic, allowing triggers from alerts to initiate automated troubleshooting or remediation workflows, as noted in the examples.

Can StackStorm handle real-time automation without delay?

It's designed for event-driven automation, but the microservices architecture and message bus communication might introduce some latency. For ultra-low latency needs, consider the overhead and optimize component deployment.

How to scale StackStorm for high availability?

Leverage its horizontal scalability by deploying microservices components across multiple nodes, using a clustered message bus like RabbitMQ, and ensuring database and caching layers are redundant, as per the architecture diagram.

Is StackStorm good for small DevOps teams?

It can be beneficial if the team needs advanced, event-driven automation, but the complexity and resource requirements might be excessive for small teams with only basic scripting needs. Simpler tools could be more appropriate.

Open-Awesome

StackStorm (.4k)

Apache-2.0Pythonv3.9.0Self-Hosted

Event-driven automation platform for DevOps and SREs, enabling auto-remediation, incident response, and workflow orchestration across tools.

Visit Website GitHub

6.4k stars781 forks0 contributors

What is StackStorm (.4k)?

StackStorm is an event-driven automation platform designed for DevOps and SRE teams to automate operational tasks like auto-remediation, incident response, troubleshooting, and deployments. It connects various tools and services through a rules engine and workflows, enabling automated actions based on triggers from external events. Often described as "IFTTT for Ops," it helps reduce manual intervention and improve operational efficiency.

Target Audience

DevOps engineers, Site Reliability Engineers (SREs), and operations teams who need to automate complex, multi-step processes across their infrastructure and application stack. It is also suitable for organizations integrating monitoring, chat, and cloud platforms into cohesive automation workflows.

Value Proposition

Developers choose StackStorm for its extensive library of pre-built integration packs, flexible workflow orchestration, and ability to treat automation as code for collaboration. Its event-driven architecture and support for ChatOps provide a scalable, programmable approach to operational automation that reduces manual toil and accelerates incident response.

Overview

StackStorm (aka "IFTTT for Ops") is event-driven automation for auto-remediation, incident responses, troubleshooting, deployments, and more for DevOps and SREs. Includes rules engine, workflow, 160 integration packs with 6000+ actions (see https://exchange.stackstorm.org) and ChatOps. Installer at https://docs.stackstorm.com/install/index.html

Use Cases

Best For

Automating incident response and remediation workflows triggered by monitoring alerts
Orchestrating multi-step deployment pipelines across cloud and on-premise environments
Integrating ChatOps for executing commands and automations via Slack or similar platforms
Building custom automation rules that connect disparate tools like Jenkins, AWS, and JIRA
Creating audit trails and logging for automated actions to support compliance and debugging
Scaling operational automation with a microservices-based, horizontally scalable architecture

Not Ideal For

Small teams with only basic cron jobs and no event-driven automation needs
Projects requiring vendor-supported SLAs and enterprise-grade support contracts
Environments where all automation is handled by configuration management tools like Ansible or Terraform
Organizations prioritizing quick, out-of-the-box solutions over customizable, code-based automation

Pros & Cons

Pros

Extensive Integration Library

Includes 160+ packs with over 6000 actions for tools like AWS, Docker, and Slack, available via StackStorm Exchange, reducing the need for custom code.

Flexible Workflow Orchestration

Allows stitching multiple actions into sequences with conditional logic and context passing, enabling complex automations for incident response and deployments.

ChatOps Enablement

Integrates with chat platforms like Slack for executing and interacting with automations directly from conversations, as highlighted in the key features.

Comprehensive Audit Trail

Records all action executions with full context and results, supporting integration with logging tools such as Splunk or statsd for compliance and debugging.

Scalable Microservices Design

Features a loosely coupled architecture that communicates over a message bus, allowing horizontal scalability for large operational environments.

Cons

Steep Initial Setup

Requires a dedicated 64-bit Linux environment with specific system prerequisites, making deployment more involved than lightweight automation tools.

Complex Learning Curve

Involves mastering concepts like sensors, triggers, rules, and workflows, which can be daunting for teams new to event-driven automation platforms.

Resource Intensive Architecture

The microservices-based design, while scalable, can consume significant system resources and introduce latency, potentially overkill for simple use cases.

Limited Commercial Support

As an open-source project, it lacks the enterprise-grade support and SLAs that some organizations might require for critical, production-level automation.

Frequently Asked Questions

Related Projects

Airflow

Apache Airflow - A platform to programmatically author, schedule, and monitor workflows

Prefect is a workflow orchestration framework for building resilient data pipelines in Python.

Temporal service

Workflow Engine for Kubernetes

Stars16,638

Forks3,507

Last commit1 day ago

Community-curated · Updated weekly · 100% open source

Found a gem we're missing?

Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.

Submit a project Star on GitHub

StackStorm (.4k)

Apache-2.0Pythonv3.9.0Self-Hosted

Event-driven automation platform for DevOps and SREs, enabling auto-remediation, incident response, and workflow orchestration across tools.

Visit Website GitHub

6.4k stars781 forks0 contributors

What is StackStorm (.4k)?

Target Audience

Value Proposition

Overview

Use Cases

Best For

Automating incident response and remediation workflows triggered by monitoring alerts
Orchestrating multi-step deployment pipelines across cloud and on-premise environments
Integrating ChatOps for executing commands and automations via Slack or similar platforms
Building custom automation rules that connect disparate tools like Jenkins, AWS, and JIRA
Creating audit trails and logging for automated actions to support compliance and debugging
Scaling operational automation with a microservices-based, horizontally scalable architecture

Not Ideal For

Small teams with only basic cron jobs and no event-driven automation needs
Projects requiring vendor-supported SLAs and enterprise-grade support contracts
Environments where all automation is handled by configuration management tools like Ansible or Terraform
Organizations prioritizing quick, out-of-the-box solutions over customizable, code-based automation

Pros & Cons

Pros

Extensive Integration Library

Includes 160+ packs with over 6000 actions for tools like AWS, Docker, and Slack, available via StackStorm Exchange, reducing the need for custom code.

Flexible Workflow Orchestration

Allows stitching multiple actions into sequences with conditional logic and context passing, enabling complex automations for incident response and deployments.

ChatOps Enablement

Integrates with chat platforms like Slack for executing and interacting with automations directly from conversations, as highlighted in the key features.

Comprehensive Audit Trail

Records all action executions with full context and results, supporting integration with logging tools such as Splunk or statsd for compliance and debugging.

Scalable Microservices Design

Features a loosely coupled architecture that communicates over a message bus, allowing horizontal scalability for large operational environments.

Cons

Steep Initial Setup

Requires a dedicated 64-bit Linux environment with specific system prerequisites, making deployment more involved than lightweight automation tools.

Complex Learning Curve

Involves mastering concepts like sensors, triggers, rules, and workflows, which can be daunting for teams new to event-driven automation platforms.

Resource Intensive Architecture

The microservices-based design, while scalable, can consume significant system resources and introduce latency, potentially overkill for simple use cases.

Limited Commercial Support

As an open-source project, it lacks the enterprise-grade support and SLAs that some organizations might require for critical, production-level automation.