Operations | Monitoring | ITSM | DevOps | Cloud

Metrics are the cornerstone of an observable system – they tell you a system’s measured outputs, granting visibility into what your customers are experiencing and when there’s a problem. However, not all methods for recording and saving metrics from a system’s output are alike. The best method for shipping your system’s metrics to Grafana Cloud depends on many factors, varying from the source of your metrics data to your familiarity with observability tools.

GitOps takes DevOps best practices used for application development (such as version control and CI/CD) and applies them to infrastructure automation. In GitOps, the Git repository serves as the source of truth and the CD pipeline is responsible for building, testing, and deploying the application code and the underlying infrastructure. Nowadays, an application is not just code running on infrastructure that you own and operate.

Mattermost v7.3 is generally available today. The following new features are included.

Public cloud can deliver significant business value across infrastructure cost savings, team productivity, service elasticity, and DevOps agility. Yet, up to 70% of organizations are regularly overshooting their cloud budgets, minimizing the gap between cloud costs and the revenue cloud investments can drive.

DORA metrics are becoming the industry standard for measuring engineering efficiency, but where did they come from? ‍ We talk a lot about DORA metrics here at Sleuth — what they are and how to measure them. But we haven’t shared much about the context of DORA metrics — their history and why we use them. So let’s do that. This article provides a summary.

If done right, retrospectives can help you inspect past actions, help adapt to future requirements and guide teams towards continuous improvement. However, organizations find it difficult to adopt the right mindset to execute retrospectives effectively. This blog will help you understand what retrospectives are and provide valuable tips to make your retrospectives meaningful. This blog will cover,

In an ideal world, developers would be able to release new products and features from development environments into production extremely fast while also not having to stress about breaking prod. Achieving this combination of development speed while also maintaining software reliability requires having the right toolchain and automation in place.

Git is a version control system (VCS) that allows you to track the development of a project over time. At the time of Git’s inception in 2005, developers had to use the command line interface (CLI) to manage Git. Learning and using the command line however is often an extremely difficult task for many developers and in some cases represents a significant barrier of entry for those seeking to leverage the power of Git. Enter the graphical user interface (GUI), also referred to as a Git Client.