Microsoft Azure offers a choice of relational and non-relational database services to support a wide range of application needs and demands. Built-in intelligence helps automate management tasks like high availability, scaling, and query performance tuning to provide users with services that ensure applications are always available and performant. Many services offer essentially limitless database scale and SLAs (Service Level Agreements) usually range between 99.9-99.999% availability.

What is the hidden potential of OpenTelemetry? It goes a lot further than the (awesome) application of tracing and monitoring your software. The OpenTelemetry project is an attempt to standardize how performance is reported and how trace data is passed around your microservice architecture. This context propagation is a superpower for those who adopt OpenTelemetry tracing.

OpenTelemetry is a Cloud Native Computing Foundation(CNCF) incubating project aimed at standardizing the way we instrument applications for generating telemetry data(logs, metrics, and traces). OpenTelemetry aims to provide a vendor-agnostic observability framework that provides a set of tools, APIs, and SDKs to instrument applications.

In today’s digital world, performance and agility are essential for running a successful business, and in the technology arena, there is no exception. Over the past few years, there has been a significant rise in the use of cloud computing technology as more companies prefer scalability of resources, flexibility in experimenting with new technologies, reducing cost by eliminating the need to invest in on-premises hardware, etc.

Both Jaeger and Prometheus are popular open-source application performance monitoring tools. While Jaeger is an end-to-end distributed tracing tool, Prometheus is used as a time-series database for monitoring metrics. Let's dive in to explore their key features and differences. Application performance monitoring is the key to keep your system's health in check. In today's digital economy, no business can afford to have failed or delayed completion of user requests.

OpenTelemetry libraries can be used to monitor MongoDB interactions. In this tutorial, we will learn how we can monitor MongoDB with OpenTelemetry libraries to analyze query execution and identify performance bottlenecks. Most modern applications have distributed architecture thanks to cloud and containerization. In cloud-native applications, it is necessary to track user requests across services and components like databases.

OpenTelemetry can be used for generating and collecting telemetry signals like logs, metrics, and traces. The advantage of using OpenTelemetry for observability is that it is open-source and frees you from vendor lock-in. You can use OpenTelemetry for multiple use cases OpenTelemetry is an open-source project which has emerged as the standard for achieving comprehensive observability in modern applications.

For Azure Virtual Desktop (AVD) sessions, Microsoft exposes a set of user experience and graphics performance counters that eG Enterprise monitors out-of-the-box. These performance counters for Azure Virtual Desktop and Remote Desktop Protocol (RDP) / RemoteFX sessions can be used to troubleshoot AVD problems.

On a recent thread on the CNCF Slack’s OTel Collector channel, a user asked a question that shone a light on a topic I don't think has been effectively discussed elsewhere.

In a recent reddit thread, I got into a conversation about justifying the cost of observability. It got to a really basic question about running a tech company: how do you know that any cost is justified? While a small number of expenses have clear and direct business values, a bunch of other costs, I would even say most costs, just aren’t that clear cut.