ChatOps and Mobile Adoption: The Power of Teams Working Where They Are

The way we socialize, learn, shop, and receive care has changed drastically over the last 18 months. For many of us, perhaps one of the most drastic changes was the way we work. While work from home (WFH) was an option before the pandemic, NCCI states, “only 6% of the employed worked primarily from home and about three-quarters of workers had never worked from home.” Fast forward to 2021, and according to NorthOne, here’s how much things have changed.

Why ChatOps & Incident Management are the Perfect Pair

ChatOps has become an integral part of software development and IT operations, as teams rely on automated notifications to take the place of manual alerts. In the past, if there was an alert, someone would need to manually find that notification. Then, they would have contact team members to notify them one by one so they could start working on a resolution. In this complex network of communications, it was easy to lose information, duplicate work, and simply waste time coordinating the team.

What's New: Introducing Next-Gen ChatOps With PagerDuty and Slack

In this new world of digital everything, new application versions usually mean that you’re going to get bigger and better features, more capabilities, and an uplifted user experience, right? When I talk to customers, many can’t wait to upgrade the PagerDuty integrations that they depend on to test new features. If you’re a PagerDuty for Slack user, the next-generation version of our Slack integration will certainly be an exciting development.

5 workflow automations for Mattermost that we love at n8n

n8n is a fair-code licensed tool that helps you automate tasks, sync data between various sources, and react to events — all via a visual workflow editor. Our team has been using Mattermost for internal communication since the very beginning, and in time we have developed a ChatOps practice by integrating Mattermost with our workflows. In this article, we present five of our favorite use cases of n8n with Mattermost, for both work productivity and team engagement.

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 ChatOps and Runbooks Coexist

ChatOps was established by GitHub as a way to automate operations-driven tasks through a chatbot by using it to run essential scripts and commands, allowing the automation of many simple tasks. It has since evolved to include integration of operations and improvement tools, and functions as a collaborative platform allowing teams to easily communicate and manage their workflow. Using a ChatOps solution also allows you to document an easily accessible timeline of your team’s verbal exchanges.

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?