June 25, 2015 (Updated: February 21, 2017)
Contribution by Integration Developer Eugen
ChatOps brings the context of work you are already doing into the conversations you are already having. @jfryman
ChatOps is still a fresh and uncommon thing in the DevOps world, where work is brought into a shared chat room. You can run commands directly from chat and everyone in the chatroom can see the history of work being done, do the same, interact with each other and even learn. The information and process is owned by the entire team which brings a lot of benefits.
June 12, 2015
by James Fryman
With our recent announcement of our ChatOps integration and of our commercial support for ChatOps and ChatOps related dev ops professional services, we thought it would be fun to take a moment and share our insights into the design decisions that we made while developing this feature. Several core platform changes were introduced, including Action-Aliases and Notifications, to enable ChatOps. So, grab some popcorn, get cozy, and we let’s dive in!
June 11, 2015
Guest post by Prashant Deva, Chief Dripper and CTO of Chronon Systems, parent company of DripStat. Earlier this year, Prashant demonstrated automated responses to OutofMemory exceptions and high GC pause times with StackStorm. Â
A common request among users of the DripStat APM is to get their alerts inside PagerDuty. Today we will show how using StackStorm, one can connect DripStat to PagerDuty. Â So why bother using StackStorm? Well, StackStorm gives you thousands of integrations plus the ability to tie them together with a rules engine, workflow, audit, a GUI and CLI, API, and more.
StackStorm is like an “If This, Then That” but for your operating environment.
Once DripStat informs you that something has gone wrong with the system, you can use StackStorm to automate more and more of your responses to such events and conditions. Thus making a self healing data center.
June 10, 2015
by Evan Powell
Last Friday we released full ChatOps support for StackStorm.
So how is this different than the countless other solutions that have announced, “you can Slack us”?  Slack has a huge ecosystem of integrations already.  And so does HuBot.  Why add StackStorm?
Because with StackStorm based ChatOps you’ll:
June 8, 2015
by James Fryman
I am pleased to announce the availability of our new platform feature, ChatOps.
It’s true, yes. We have had ChatOps support for quite some time. However, a while back after receiving user feedback, we decided to give what we had built a good once over. To that end, ChatOps is dead. Long Live ChatOps! What we are releasing today is the result of these efforts.
ChatOps is a new operational paradigm where work that is already happening in the background today is brought into a common chatroom. In doing so, you are unifying the communication about what work should get done with actual history of the work being done. Deploying code from chat, viewing graphs from a TSDB or logging tool, or creating new Jira tickets are all examples of tasks that can be done via ChatOps.
June 5, 2015
Contribution by Integration Developer Eugen
We’re always happy when the number of integrations to StackStorm increases, creating bridges between more DevOps tools and extending possible use cases.  Our IFTTT for Ops approach – or Event Driven Automation – becomes more valuable the more ways to control and listen to your environment come pre-integrated, “batteries included.”
Recently, an Ansible integration pack was added to StackStorm Exchange, giving users the possibility to use Ansible as an underlying remote change and configuration management tool in conjunction with StackStorm.
There are approaches StackStorm and Ansible have in common:
June 2, 2015
by Evan Powell
Your stories – and your ingenuity in wiring your environments together – have inspired us to build something truly different with StackStorm in order to help us all wire our environments together without incurring the massive technical debt of purely home built solutions. In the months since open-sourcing StackStorm late last year, the response has been almost overwhelming with downloads now in the tens of thousands per month, and recently doubling month over month over month.
May 27, 2015
by Lakshmi Kannan
In this blog post, we cover CI part of CICD with Docker as an example. At a high level, this blog post will demonstrate how to create a docker image and push it to a registry on every commit to a github repo. You have probably read our own James Fryman’s excellent blog post on continuous delivery with StackStorm in a more traditional environment. If not, I highly recommend reading it. Also, this recent blog post from docker is a great introduction to using docker in continuous delivery. Before diving into the details, below is some motivation for switching to container based immutable infrastructure.
As Michael Dehaan of Ansible fame notes, immutable infrastructure is the way of the future. Containers (especially, Docker) facilitate this by offering users a way to define their infrastructure through simple files (Dockerfile, for example). The role of orchestration tools changes when dealing with immutable infrastructure. A relevant quote from Michael Dehaan’s blog:
“To keep up, I view orchestration systems as needing to embrace workflow, merging with build systems, producing images, and perhaps attempting to provide those higher “cluster level” APIs prior to clouds more natively doing this.”