STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

HIGH AVAILABILITY DEPLOYMENT High Availability Deployment. StackStorm has been systematically built with High availability (HA) as a goal. The exact deployment steps to achieve HA depend on the specifics of the infrastructure in which StackStorm is deployed. This guide covers a brief explanation on various StackStorm services, how they interact and the external

services

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. YAQL — STACKSTORM 3.4.0 DOCUMENTATION List to Dictionary¶. There are cases where it is easier to work with dictionaries rather than lists (e.g. random access of a value with the key). Let’s take the same list of VM records from above and convert it to a dictionary where VM name is the key and the value is the

record.

WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model.

ACTION RUNNERS

Action Runners. An action runner is the execution environment for user-implemented actions. StackStorm comes with pre-canned action runners such as a remote runner and shell runner which provide for user-implemented actions to be run remotely (via SSH) and locally. The objective is to allow the Action author to concentrate only on the HELP TO TUNE PERFORMANCE OPTIMIZATION FOR STACKSTORM Help to tune performance optimization for stackstorm. smurugu February 6, 2020, 2:35pm #1. Currently working on POC for using stackstorm. I went through the sample st2.conf and used the docker container option for deployment and conducted performance testing. Regardless of what configuration change i make for actionrunner, scheduler, workflow HOW TO CREATE SENSOR IN PYTHON FOR HTTP @winem thanks for your response could you plz describe how to trigger imap sensor. actually i have downloaded one email pack i have made one rule trigger section contain email.imap_sensor and criteria has (trigger.from contain annu@gmail.com) and action part has email.send_email. and in action part i have assign some account details actually i m new in this i IS THERE A WAY TO TRIGGER EVENT IN WORKFLOW LIKE INQUIRY Hi there, Just wondering if there is a way to trigger an event in workflow1, and such event could be inspected by rules in order to trigger workflow2? I know that this could be done by calling workflow2 directly in workflow1, but if we can trigger event we don’t need to know the workflow2. That will be asynchronous and the failure of workflow2 won’t impact workflow1. In inquiry we can STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

HIGH AVAILABILITY DEPLOYMENT High Availability Deployment. StackStorm has been systematically built with High availability (HA) as a goal. The exact deployment steps to achieve HA depend on the specifics of the infrastructure in which StackStorm is deployed. This guide covers a brief explanation on various StackStorm services, how they interact and the external

services

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. YAQL — STACKSTORM 3.4.0 DOCUMENTATION List to Dictionary¶. There are cases where it is easier to work with dictionaries rather than lists (e.g. random access of a value with the key). Let’s take the same list of VM records from above and convert it to a dictionary where VM name is the key and the value is the

record.

WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model.

ACTION RUNNERS

Action Runners. An action runner is the execution environment for user-implemented actions. StackStorm comes with pre-canned action runners such as a remote runner and shell runner which provide for user-implemented actions to be run remotely (via SSH) and locally. The objective is to allow the Action author to concentrate only on the HELP TO TUNE PERFORMANCE OPTIMIZATION FOR STACKSTORM Help to tune performance optimization for stackstorm. smurugu February 6, 2020, 2:35pm #1. Currently working on POC for using stackstorm. I went through the sample st2.conf and used the docker container option for deployment and conducted performance testing. Regardless of what configuration change i make for actionrunner, scheduler, workflow HOW TO CREATE SENSOR IN PYTHON FOR HTTP @winem thanks for your response could you plz describe how to trigger imap sensor. actually i have downloaded one email pack i have made one rule trigger section contain email.imap_sensor and criteria has (trigger.from contain annu@gmail.com) and action part has email.send_email. and in action part i have assign some account details actually i m new in this i IS THERE A WAY TO TRIGGER EVENT IN WORKFLOW LIKE INQUIRY Hi there, Just wondering if there is a way to trigger an event in workflow1, and such event could be inspected by rules in order to trigger workflow2? I know that this could be done by calling workflow2 directly in workflow1, but if we can trigger event we don’t need to know the workflow2. That will be asynchronous and the failure of workflow2 won’t impact workflow1. In inquiry we can

INSTALLATION

This is an opinionated installation of StackStorm. It will download and install all components, as per the single host reference deployment.It assumes that you have a PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

ORQUESTA — STACKSTORM 3.4.0 DOCUMENTATION Orquesta¶. Orquesta. Orquesta is a workflow engine designed specifically to run natively in StackStorm. It has replaced the Mistral workflow engine, and the goal is to replace ActionChain in the future. Orquesta’s workflow definition is described in YAML and contains a number of changes and improvements over its predecessors. WORKFLOWS — STACKSTORM 3.4.0 DOCUMENTATION To capture and automate these operations, StackStorm uses workflows. A workflow strings atomic actions into a higher level automation, and orchestrates their executions by calling the right action, at the right time, with the right input. It keeps state, passes data between actions, and provides reliability and transparency to the execution. CHATOPS — STACKSTORM 3.4.0 DOCUMENTATION Combining ChatOps and StackStorm is an ideal combination: from Chat users will be able to execute actions and workflows to accelerate the IT delivery pipeline. In the same way, the ChatOps/StackStorm combination also enhances user adoption of automation through transparency and consistent execution. The end result is improved

agility and

ORQUESTA WORKFLOW DEFINITION A workflow takes input, perform a set of tasks in predefined order, and returns output. The workflow model here is a directed graph where the tasks are the nodes and the transitions and their condition between tasks form the edges. The tasks that compose a workflow will be defined in the DSL as a dictionary named tasks where the key and

value

UNINSTALL — STACKSTORM 3.4.0 DOCUMENTATION The uninstallation procedure follows this outline: Stop services. Remove packages. Remove StackStorm system user. Remove databases and other dependencies. Remove repositories. Clean up any remaining logs, configurations and directories. The exact steps vary slightly between Linux distributions.

NOTIFICATIONS

Notifications¶. If you read through the What is ChatOps? section, you are familiar with notifications. Even without ChatOps, notifications can be used to post messages to external systems like Chat clients, send emails etc. Notifications require an action that is registered with StackStorm (e.g., the post_message action in the slack pack) and a notification rule to go with it. STACKSTORM K8S HELM CHART REPOSITORY INDEX helm repo add stackstorm https://helm.stackstorm.com/ helm install stackstorm/stackstorm-ha HOW TO CREATE SENSOR IN PYTHON FOR HTTP @winem thanks for your response could you plz describe how to trigger imap sensor. actually i have downloaded one email pack i have made one rule trigger section contain email.imap_sensor and criteria has (trigger.from contain annu@gmail.com) and action part has email.send_email. and in action part i have assign some account details actually i m new in this i STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. YAQL — STACKSTORM 3.4.0 DOCUMENTATION YAQL¶. YAQL (Yet Another Query Language) is an OpenStack project and allows for complex data querying and transformation. In the workflow definition, YAQL expressions are wrapped inbetween like . WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model. TRACES — STACKSTORM 3.4.0 DOCUMENTATION Traces¶. Traces. Traces are tracking entities that serve to gather all StackStorm entities like ActionExecution, TriggerInstance and Rule that originate from an event. In the StackStorm context an event could be one of the following: Events from an external system sent to StackStorm via a Sensor or Webhook. Action executed via UI, CLI or

API.

HELP TO TUNE PERFORMANCE OPTIMIZATION FOR STACKSTORM Help to tune performance optimization for stackstorm. smurugu February 6, 2020, 2:35pm #1. Currently working on POC for using stackstorm. I went through the sample st2.conf and used the docker container option for deployment and conducted performance testing. Regardless of what configuration change i make for actionrunner, scheduler, workflow HOW TO CREATE SENSOR IN PYTHON FOR HTTP hi all i want to connect my web app with stackstorm using http request what is the procedure and i also want to know how to create rule and how to trigger rule actually i have downloaded email pack from github and this is working when i’m sending email in manually but i don’t knw how to trigger it automatically i have used IMAP sensor thanks in

advanced

IS THERE A WAY TO TRIGGER EVENT IN WORKFLOW LIKE INQUIRY Hi there, Just wondering if there is a way to trigger an event in workflow1, and such event could be inspected by rules in order to trigger workflow2? I know that this could be done by calling workflow2 directly in workflow1, but if we can trigger event we don’t need to know the workflow2. That will be asynchronous and the failure of workflow2 won’t impact workflow1. In inquiry we can STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. YAQL — STACKSTORM 3.4.0 DOCUMENTATION YAQL¶. YAQL (Yet Another Query Language) is an OpenStack project and allows for complex data querying and transformation. In the workflow definition, YAQL expressions are wrapped inbetween like . WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model. TRACES — STACKSTORM 3.4.0 DOCUMENTATION Traces¶. Traces. Traces are tracking entities that serve to gather all StackStorm entities like ActionExecution, TriggerInstance and Rule that originate from an event. In the StackStorm context an event could be one of the following: Events from an external system sent to StackStorm via a Sensor or Webhook. Action executed via UI, CLI or

API.

HELP TO TUNE PERFORMANCE OPTIMIZATION FOR STACKSTORM Help to tune performance optimization for stackstorm. smurugu February 6, 2020, 2:35pm #1. Currently working on POC for using stackstorm. I went through the sample st2.conf and used the docker container option for deployment and conducted performance testing. Regardless of what configuration change i make for actionrunner, scheduler, workflow HOW TO CREATE SENSOR IN PYTHON FOR HTTP hi all i want to connect my web app with stackstorm using http request what is the procedure and i also want to know how to create rule and how to trigger rule actually i have downloaded email pack from github and this is working when i’m sending email in manually but i don’t knw how to trigger it automatically i have used IMAP sensor thanks in

advanced

IS THERE A WAY TO TRIGGER EVENT IN WORKFLOW LIKE INQUIRY Hi there, Just wondering if there is a way to trigger an event in workflow1, and such event could be inspected by rules in order to trigger workflow2? I know that this could be done by calling workflow2 directly in workflow1, but if we can trigger event we don’t need to know the workflow2. That will be asynchronous and the failure of workflow2 won’t impact workflow1. In inquiry we can PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

ORQUESTA — STACKSTORM 3.4.0 DOCUMENTATION Orquesta¶. Orquesta. Orquesta is a workflow engine designed specifically to run natively in StackStorm. It has replaced the Mistral workflow engine, and the goal is to replace ActionChain in the future. Orquesta’s workflow definition is described in YAML and contains a number of changes and improvements over its predecessors. CHATOPS — STACKSTORM 3.4.0 DOCUMENTATION Combining ChatOps and StackStorm is an ideal combination: from Chat users will be able to execute actions and workflows to accelerate the IT delivery pipeline. In the same way, the ChatOps/StackStorm combination also enhances user adoption of automation through transparency and consistent execution. The end result is improved

agility and

HIGH AVAILABILITY DEPLOYMENT High Availability Deployment. StackStorm has been systematically built with High availability (HA) as a goal. The exact deployment steps to achieve HA depend on the specifics of the infrastructure in which StackStorm is deployed. This guide covers a brief explanation on various StackStorm services, how they interact and the external

services

TRACES — STACKSTORM 3.4.0 DOCUMENTATION Traces¶. Traces. Traces are tracking entities that serve to gather all StackStorm entities like ActionExecution, TriggerInstance and Rule that originate from an event. In the StackStorm context an event could be one of the following: Events from an external system sent to StackStorm via a Sensor or Webhook. Action executed via UI, CLI or

API.

ORQUESTA WORKFLOW DEFINITION A workflow takes input, perform a set of tasks in predefined order, and returns output. The workflow model here is a directed graph where the tasks are the nodes and the transitions and their condition between tasks form the edges. The tasks that compose a workflow will be defined in the DSL as a dictionary named tasks where the key and

value

ACTION RUNNERS

Action Runners. An action runner is the execution environment for user-implemented actions. StackStorm comes with pre-canned action runners such as a remote runner and shell runner which provide for user-implemented actions to be run remotely (via SSH) and locally. The objective is to allow the Action author to concentrate only on the

NOTIFICATIONS

Notifications¶. If you read through the What is ChatOps? section, you are familiar with notifications. Even without ChatOps, notifications can be used to post messages to external systems like Chat clients, send emails etc. Notifications require an action that is registered with StackStorm (e.g., the post_message action in the slack pack) and a notification rule to go with it. STACKSTORM K8S HELM CHART REPOSITORY INDEX helm repo add stackstorm https://helm.stackstorm.com/ helm install stackstorm/stackstorm-ha WORKAROUND FOR ACCESSING CONFIG_CONTEXT IN A MISTRAL Reference Problem Currently in a Mistral Workflow you can not access the config_context described here: Actions — StackStorm 2.10.1 documentation StackStorm currently doesn’t pass this context into Mistral or provide a Jinja filter to access it. Workaround To access the config context information in a Mistral workflow, you can simply create a new parameter in the StackStorm action STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

STACKSTORM DOCUMENTATION StackStorm Documentation — StackStorm 3.4.0 documentation. Note. The documentation you're currently reading is for version 3.4.0. Click here to view documentation for the latest stable version.

INSTALLATION

This is an opinionated installation of StackStorm. It will download and install all components, as per the single host reference deployment.It assumes that you have a RULES — STACKSTORM 3.4.0 DOCUMENTATIONSTACKSTORM ANSIBLESTACKSTORM DOWNLOADSTACKSTORM EXCHANGESTACKSTORM EXCHANGESTACKSTORM GITHUBSTACKSTORM GITHUB type specifies which criteria comparison operator to use and pattern specifies a pattern which gets passed to the operator function.. In the regex case, pattern is a regular expression pattern which the trigger value needs to match.. A list of all the available criteria operators is described below. If the criteria key contains any special characters (like -) then use the dictionary lookup SENSORS AND TRIGGERS Sensors are pieces of Python code that either periodically poll some external system, or passively wait for inbound events. They then inject triggers into StackStorm, which can be matched by rules, for potential action execution. Sensors are written in Python, and must

follow the

PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

HIGH AVAILABILITY DEPLOYMENT High Availability Deployment. StackStorm has been systematically built with High availability (HA) as a goal. The exact deployment steps to achieve HA depend on the specifics of the infrastructure in which StackStorm is deployed. This guide covers a brief explanation on various StackStorm services, how they interact and the external

services

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model. STACKSTORM - STACKSTORMFEATURESCOMMUNITYDOCSBLOGDONATESTACKSTORM

THOUGHT LEADERS

StackStorm is used by people just like you, solving real-world problems. StackStorm hasn’t yet unlocked its full potential, so the more people that bring their use cases to the community, the more it can evolve and grow. Chris Jackson Director of Cloud Platforms at

Pearson.

STACKSTORM DOCUMENTATION StackStorm Documentation — StackStorm 3.4.0 documentation. Note. The documentation you're currently reading is for version 3.4.0. Click here to view documentation for the latest stable version.

INSTALLATION

This is an opinionated installation of StackStorm. It will download and install all components, as per the single host reference deployment.It assumes that you have a RULES — STACKSTORM 3.4.0 DOCUMENTATIONSTACKSTORM ANSIBLESTACKSTORM DOWNLOADSTACKSTORM EXCHANGESTACKSTORM EXCHANGESTACKSTORM GITHUBSTACKSTORM GITHUB type specifies which criteria comparison operator to use and pattern specifies a pattern which gets passed to the operator function.. In the regex case, pattern is a regular expression pattern which the trigger value needs to match.. A list of all the available criteria operators is described below. If the criteria key contains any special characters (like -) then use the dictionary lookup SENSORS AND TRIGGERS Sensors are pieces of Python code that either periodically poll some external system, or passively wait for inbound events. They then inject triggers into StackStorm, which can be matched by rules, for potential action execution. Sensors are written in Python, and must

follow the

PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

CODE STRUCTURE

StackStorm/st2 Repo¶. StackStorm is made up of individual services: st2auth, st2api, st2rulesengine , st2sensorcontainer, st2actionrunner, st2notifier. StackStorm also has a CLI and client library. Code for all these services and components are laid out in different folders in

the repo root.

HIGH AVAILABILITY DEPLOYMENT High Availability Deployment. StackStorm has been systematically built with High availability (HA) as a goal. The exact deployment steps to achieve HA depend on the specifics of the infrastructure in which StackStorm is deployed. This guide covers a brief explanation on various StackStorm services, how they interact and the external

services

SYSTEM MONITORING

The StackStorm audit logs record all executed actions, execution time and result. These logs should be stored in a system like Splunk or Elasticsearch that allows for extraction of average run time and execution count. Interesting metrics to monitor: See below for more details on logfile monitoring. WORKFLOW RUNTIME CONTEXT Workflow Runtime Context. At runtime, the workflow execution maintain a context dictionary that manages assigned variables. In the workflow definition, there are several location where variables can be assigned into the context. These locations are input, vars, and output in the workflow model and publish in the task transition model.

INSTALLATION

This is an opinionated installation of StackStorm. It will download and install all components, as per the single host reference deployment.It assumes that you have a

STACKSTORM OVERVIEW

StackStorm is a service with modular architecture. It comprises loosely coupled service components that communicate over the message bus, and scales horizontally to deliver automation at scale. StackStorm has a Web UI, a CLI client, and of course a full REST API. We also ship Python client bindings to make life easier for

developers.

PACKS — STACKSTORM 3.4.0 DOCUMENTATION A “pack” is the unit of deployment for integrations and automations that extend StackStorm. Typically a pack is organized along service or product boundaries e.g. AWS, Docker, Sensu etc. A pack can contain Actions, Workflows, Rules , Sensors, and Aliases. StackStorm content is always part of a pack, so it’s important to

understand how to

STACKSTORM HA CLUSTER IN KUBERNETES StackStorm HA Cluster in Kubernetes - BETA¶. This document provides an installation blueprint for a Highly Available StackStorm cluster based on Kubernetes, a container orchestration platform at planet scale.. The cluster deploys a minimum of 2 replicas for each component of StackStorm microservices for redundancy and reliability.

CLI REFERENCE

Re-running an Action¶. To re-run a particular action, you can use the st2 execution re-run command.. By default, this command re-runs an action with the same set of input parameters which were used with the

original action.

UBUNTU XENIAL (16.04) Ubuntu Xenial (16.04)¶ If you’re just looking for a quick “one-liner” installation, check the top-level install guide.If you need a customised installation, use this guide for step-by-step instructions for installing StackStorm on a single system as per the Reference deployment. WEBHOOKS — STACKSTORM 3.4.0 DOCUMENTATION Using a Generic Webhook¶. By default, a special-purpose webhook with the name st2 is already registered. Instead of using core.st2.webhook, it allows you to specify any trigger that is known to StackStorm (either by default or from custom sensors and triggers in packs), so you can use it to trigger rules that aren’t explicitly set up to be triggered by webhooks.

NOTIFICATIONS

Notifications¶. If you read through the What is ChatOps? section, you are familiar with notifications. Even without ChatOps, notifications can be used to post messages to external systems like Chat clients, send emails etc. Notifications require an action that is registered with StackStorm (e.g., the post_message action in the slack pack) and a notification rule to go with it. STACKSTORM K8S HELM CHART REPOSITORY INDEX helm repo add stackstorm https://helm.stackstorm.com/ helm install stackstorm/stackstorm-ha RUNNING SELF-VERIFICATION Running Self-Verification¶. StackStorm includes a script for verifying the system installation. The script covers the following aspects of StackStorm:

* Features

* Community

* Docs

* Exchange

* Blog

* Donate

STACKSTORM CONNECTS ALL YOUR APPS, SERVICES, AND WORKFLOWS. __ Why StackStorm? Get Started OPEN SOURCE AND TRUSTED BY THE ENTERPRISE ROBUST AUTOMATION ENGINE From simple if/then rules to complicated workflows, StackStorm lets you automate DevOps your way.

steps-vertical

See More Features... INTEGRATES WITH YOUR EXISTING INFRASTRUCTURE No need to change your existing processes or workflows, StackStorm connects what you already have. See More Integrations... JOIN OUR OPEN SOURCE COMMUNITY ON SLACK Community is what makes a good product great. StackStorm is used by a lot of people around the world, and you can always count on getting answers to your questions. __Join Our Slack Community * More ways to get help:

* __Forums

* __Github

* __Email

__

USED BY YOUR PEERS

StackStorm is used by people just like you, solving real-world

problems.

> StackStorm hasn’t yet unlocked its full potential, so the more > people that bring their use cases to the community, the more it can > evolve and grow.

>

>  Chris Jackson Director of Cloud Platforms at Pearson

>  Read More...

> StackStorm has changed how we approach automation, allowing us to > compartmentalize small specific tasks which can be orchestrated into > larger macro tasks. We can share the small pieces between teams and > collectively improve on them over time.

>

>  Mick McGrath Lead Engineer at Bitovi

>  Read More...

> The capabilities of StackStorm are truly only limited by your > imagination. Its overall simplicity truly makes it a fantastic tool > for just about any situation requiring automation.

>

>  Luke Marty Lead Technical Architect for Cloud Security at Target

>  Read More...

> Choosing StackStorm allowed us to quickly bootstrap without > reinventing the wheel. This allowed us to focus on Netflix specific > features and integrations and reduced our time to market

> significantly.

>

>  Sayli Karmarkar & Vinay Shah Netflix Diagnostics & Remediation > Engineering team

>  Read More...

Read More Stories... LIMITLESS BUSINESS APPLICATIONS Stackstorm can be used to automate and streamline nearly any part of your business. Here are some of the most common applications. AUTOMATED REMEDIATION When failures happen, StackStorm can act as Tier 1 support: It troubleshoots, fixes known problems, and escalates to humans when

needed.

CONTINUOUS DEPLOYMENT Continuous deployment can get complex, beyond Jenkins or other specialized opinionated tools. Automate advanced CI/CD pipelines your

way.

CHATOPS OPTIMIZATION ChatOps brings automation and collaboration together; transforming devops teams to get things done better, faster, and with style. AUTOMATED SECURITY RESPONSE Security issues are serious and need to be addressed quickly. Stackstorm can ensure that your response is consistent, always on, and

faster than ever.

Get Started

NETFLIX USED STACKSTORM TO BUILD WINSTON, AN EVENT DRIVEN DIAGNOSTIC AND REMEDIATION PLATFORM Learn how Netflix used Stackstorm as their underlying engine to host and execute their runbooks. __ View Presentation __ Read Article on Medium

Documentation

GitHub

Community

Security

Blog

Events

Video Gallery

Privacy Policy

Contact

__ __

__

__

__

� 2021 StackStorm a Series of LF Projects, LLC. All rights reserved. For web site terms of use, trademark policy and other project policies please see https://lfprojects.org/. For a list of trademarks of The Linux Foundation, please see our

Trademark Usage

page. Linux is a registered trademark of Linus Torvalds. Privacy Policy and Terms of Use

.

We use cookies for traffic analytics and ad and content personalization. By clicking on any of the content or interacting with any section of this website, you are agreeing to this use of cookies in the manner described in our Privacy Policy close Privacy & Cookies Policy

Close

PRIVACY OVERVIEW

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the ...

Necessary

Necessary Always Enabled Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.

Non-necessary

Non-necessary

Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.

SAVE & ACCEPT