Operations | Monitoring | ITSM | DevOps | Cloud

Last week, we spent some time talking to Gergely Orosz about our thoughts on what happens when an incident is over, and you're looking back on how things went. If you haven't read it already, grab a coffee, get comfortable, and read Gergely's full post Postmortem Best Practices here. But before you do that, here's some bonus material on some of our points.

With the trend towards smaller but more frequent software releases, your binaries and artifacts keep accumulating faster. Our enterprise customers each maintain an average of 20 million unique artifacts, adding 130% more each year. Eventually, a clutter of outdated binaries forms, and fInding the binaries you need becomes unwieldy, difficult, and confusing. Over time, your artifact repository’s performance can suffer from degradation.

Successful SaaS companies know that they can't rely on gut feelings alone to make business decisions. Data helps them uncover patterns, trends, opportunities, and potential gaps in their strategy that can give them a competitive advantage. Yet, simply collecting metrics can often give you a lot of data to analyze with little insight into what to do next.

The fintech ecosystem is flourishing and exciting things are happening these days at the intersection of digital technology and financial services – thanks in part to an infusion of global fintech investment that reached US$98 billion across 2,456 deals in H1’21. This far outpaces last year’s annual total of $121.5 billion across 3,520 deals.

The role and responsibilities of a site reliability engineer (SRE) may vary depending on the size of the organization. For the most part, a site reliability engineer is focused on multiple tasks and projects at one time, so for most SREs, the various tools they use reflect their eve-evolving responsibilities. A typical SRE is busy automating, cleaning up code, upgrading servers, and continually monitoring dashboards for performance, etc., so they are going to see more tools in that toolbelt.

I’ve been leading software teams for more than 20 years and one thing I’ve learned about metrics is that leaders tend to put too much emphasis on engineering metrics alone, without considering the bigger picture. After speaking to a range of engineering industry leaders, and poring over millions of jobs processed from software teams worldwide, we found that the most insightful and relevant metrics fall into three categories: What metrics are meaningful for your team to measure?

Sit down with Ana and Jason for this week's show with Leonardo (Leo) Murillo, principal partner solutions architect at Weaveworks, and former DJ, who joins us from Costa Rica. Leo shares his take on GitOps, offers a lot of excellent resources to check out, and shares his thoughts on automating reliability. He also defines how to account for the “DJ variable” and “party parameters” alongside some fun anecdotes on DevOps.

This post outlines the quickest path available for a developer to use a basic Mattermost app on a local setup. It makes use of Docker containers, a Node.js app, and — of course — a Mattermost instance! When you’re ready to get started with the Mattermost App Framework, here are the steps that you will need to take.