What is ChatOps?

The term ‘ChatOps’ was first coined by Github to describe how their internal teams used a bot called Hubot to handle DevOps. Since then, ChatOps has been practically (and successfully) adopted by numerous organizations as an additional enabler to the DevOps framework. ChatOps is a conceptualized collaboration model that embeds DevOps processes and tools within an organization’s communication channels to aid transparency and workflow automation.


How to enable JumpCloud ChatOps with Workativ Assistant

If you’re using JumpCloud as your business’ directory-as-a-service (DaaS) solution to authenticate, authorize, and manage users, then it’s high time you made the whole process effortless for your employees. Why? Because many a time, businesses tend to invest more on the technologies that improve the customer experience and neglect to do the same for their employees.


Kubernetes Health Alerts

When a pod is unhealthy in a Kubernetes cluster, does anyone notice? Have you ever deployed a new version of an app to Kubernetes, tried to test the new feature you added or bug you fixed and found the same behavior as before? Have you ever then double-checked your code, rerun your tests, checked a few more things, only then to realize that while the deployment got updated, the new pods never replaced the old because of some misconfiguration or other mistake?


Driving Real-Time ChatOps With PagerDuty and Microsoft Teams

With over 75 million daily active users, it’s safe to say Microsoft Teams is essential to many global businesses. On top of that, Microsoft CEO Satya Nadella recently shared that Microsoft saw 200 million meeting participants in a single day this month. While Microsoft Teams’ explosive growth can be tied to recent spikes in remote work, many enterprises have relied on Teams to connect people across the globe for quite some time.


Mattermost recipe: Using Google Lighthouse and ChatOps for website auditing and performance tracking

Every web developer wants to build a website that adheres to the almost mythical “best practices” so that it is light and performant. But how exactly are developers supposed to measure performance? And what is considered to be a best practice when it comes to developing for the web?


How ChatOps Helps Us Streamline Our Work

These are unusual times. In a prior post entitled Replacing the Water Cooler, we wrote about the dramatic shift in sharing information for many people. We are a team distributed across the United States, Europe, and Australia. While we have been operating as a distributed organization for several years, the current environment feels very different. We check in with each other more often and have more live video discussions. In this post, I briefly cover how we make use of chat.


Tracking Current ChatOps Benefits and Future Trajectory

Communication and transparency across all DevOps and IT workflows – from continuous testing to incident management – are more important than ever. Hence, the use of ChatOps. ChatOps offers the ability to execute commands and scripts, automate chatbots and communicate in the same places you collaborate with teammates.

Lessons Learned Implementing ChatOps

Email overload, distributed teams and excessive meetings have caused many organizations to move their DevOps teams to messaging platforms and thus adopt ChatOps workflows. With thousands of open source installs and hundreds of customer implementations, we have a few lessons to share on interesting DevOps workflows, how incidents can be effectively communicated across distributed teams and what messaging in secure and regulated environments should look like.

How enterprise dev teams use GitLab and Mattermost ChatOps to accelerate development

There has never been more pressure on development teams to build software faster and more efficiently. The rise in popularity of DevOps has largely been the result of its promise to speed up dev cycles, increase agility, and help teams resolve issues more quickly. And while the availability and sophistication of DevOps tools have improved greatly in the last few years, simply choosing the latest and greatest tools is no guarantee of a smooth, problem-free development lifecycle.