Operations | Monitoring | ITSM | DevOps | Cloud

In this digital era, applications are used on a daily basis to make our life easier. A lot of software applications are launched every day, continuously increasing competition in the market. There are thousands of applications available for a task. But, the success of any application highly depends on its performance. A good-performing application provides a flawless user experience to the customers. Ultimately, making performance a crucial metric for benefitting the company owning the software product.

Stanza is a robust log agent. GCP users can use Stanza for ingesting large volumes of log data. Before we dive into the configuration steps, here’s a matrix detailing the functional differences between all the common log agents used by GCP users. Stanza was built as a modernized version of FluentD, Fluentbit, and Logstash. GCP users now have the ability to install Stanza to their VMs/ GKE clusters to ingest logs and route them to GCP log explorer.

Implementing SLAs, SLIs, and SLOs in an observability suite is now business-critical. Over time, a company’s decision-makers can add a burdensome number of KPIs that force servers and other IT assets to devote excessive processing time to business intelligence. Eventually, the burden becomes so great that employees, managers, and executives start to complain about the system’s sluggishness. Developers know that they need to strike a balance between business needs and IT processes.

First, I’d like to say that pager duty isn’t something we should treat like chronic pain or diabetes, where you just constantly manage symptoms and tend to flare-ups day and night. Being paged out of hours is as serious as a fucking heart attack. It should be RARE and taken SERIOUSLY. Resources should be mustered, product cycles should be reassigned, until the problem is fixed.