Operations | Monitoring | ITSM | DevOps | Cloud

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.

Are you looking for an OpenTelemetry alternative? Then you've come to the right place. There are no good alternatives to OpenTelemetry if your use case involves generating different types of telemetry signals like logs, metrics, and traces and their collection. In certain use cases, like monitoring only metrics or time-series data, you can use a tool like Prometheus. If you’re sure you want an OpenTelemetry alternative, then let me point you to these three here.