Operations | Monitoring | ITSM | DevOps | Cloud

First of all, don’t ask this! Instead of asking what to log, we should start by asking “what questions do we want to answer?” Then, we can determine which data needs to be logged in order to best answer these questions. Once a question comes up, we can answer it using only the data and knowledge that we have on hand. In emergent situations such as an unforeseen system failure, we cannot change the system to log new data to answer questions about the current state of the system.

The ASP.NET Core framework provides cross-platform support for web development, giving you greater control over how you build and deploy your.NET applications. With the ability to run.NET applications on more platforms, you need to ensure that you have visibility into application performance, regardless of where your applications are hosted. In previous posts, we looked at instrumenting and monitoring a.NET application deployed via Docker and AWS Fargate.

At Spike.sh , we are obsessed with making incident management more accessible to dev teams everywhere. With this goal in mind, we are always looking for ways to reduce the friction while setting up the Spike.sh platform. When we saw customers asking our advice for creating effective on-call schedules and escalations, we knew we had to do more than just good documentation - we needed a way to share best practices with our customers in the product itself.

Grafana Tempo 1.1 has been released, and like our major version suggests, there are no breaking changes. If you’d like, please check out the release notes . But if you find that release notes can sometimes be difficult to decode, fret not! All the highlights are below.

Providing an effective service – especially in a world with constantly evolving needs – goes beyond standard operating hours. Imagine if a bank only kept your investments secure while they were ‘open’ during their hours of standard operation? Issues can arise at any time and having effective service delivery monitoring and support for enterprise’s IT teams and managed service providers is critical.

It sounds like a wild claim, considering that billion dollar companies like Splunk, Datadog, New Relic, and Solarwinds are consistently making national headlines, for both good and bad reasons. Observability leaders are anything but invisible, so how can the perfect solution be different? Are they that far off?

This tutorial is a follow-up to TurboCharging your Android Gradle builds using build cache . The key focus of this post is the remote build cache, a build speed acceleration technology that can be implemented for both local and CI builds. This is a technology worth knowing about because: Gradle provides a build cache node available as a Docker image. You can host this image in a number of ways.

On this day in 1955, the first edition of the “Guinness Book of Records” was published in London.

The year 2020 proved that we need to “adapt” to the unknown, the “new normal” and the constant transformation of what would become a new state of living — one that meant being “displaced” and personally disconnected. If the global Covid-19 pandemic taught us a lesson, it was that we could incorporate new ways of living by self-isolating yet maintaining social integration via a digital presence.

HTTP/2 (originally named HTTP/2.0) was a major revision of the HTTP network protocol used by the World Wide Web published in 2015. Indeed, those in the Citrix/EUC ecosystem may remember Marius Sandbu investigating the benefits of HTTP/2 for NetScaler, Microsoft IIS, and Storefront users back in 2015/6. HTTP/2 was the first new version of HTTP since HTTP/1.1, which itself was standardized in RFC 2068 in 1997.