Operations | Monitoring | ITSM | DevOps | Cloud

In the previous article, we talked about Distributed Tracing with MuleSoft APIs using OpenTelemetry. In this post, we’ll go through the process of integrating Distributed Tracing with MuleSoft APIs using OpenTelemetry via a proxy server. The purpose of this article is to demonstrate how we can instrument a legacy mule app with open telemetry without making changes to the existing app. Here, we’re showing an example of getting data from a header as well as a query parameter.

What is OpenTelemetry Collector, Architecture, Deployment and Getting started.

Core Web Vitals (CWV) are Google's preferred metrics for measuring the quality of the user experience for browser web apps. Currently, Core Web Vitals measure loading performance, interactivity, and visual stability. These are the main indicators of what a user’s experience will be while using a web page.

Elastic APM supports OpenTelemetry on multiple levels. One easy-to understand scenario, which we previously blogged about, is the direct OpenTelemetry Protocol (OTLP) support in APM Server. This means that you can connect any OpenTelemetry agent to an Elastic APM Server and the APM Server will happily take that data, ingest it into Elasticsearch®, and you can view that OpenTelemetry data in the APM app in Kibana®.

I recently read this thread in the CNCF slack from someone wanting to send metrics and traces directly to Postgres. Reasonable enough right? After all once your data is in postgres you can query it to your heart’s content. And isn’t the general culture of OpenTelemetry that you should be able to do all of Observability without resorting to SaaS tools? The thread, however, is pretty universally opposed to this approach; and I have to say that I agree.

Distributed tracing enhances observability by providing detailed insights into the performance, behavior, and dependencies of your distributed system. It empowers you to proactively identify and resolve issues, optimize performance, and deliver a reliable and high-performing application.

OpenTelemetry (OTel) is an open source, vendor-neutral observability framework that supplies APIs, SDKs, and tools for the instrumentation of applications and services. As part of our ongoing commitment to OTel, we are excited to announce support for the ingestion and visualization of runtime metrics from OTel-instrumented applications in Java, .NET, and Go.

Since ServiceNow launched the Service Graph Connector for OpenTelemetry in the Innovation Lab in April 2023, we’ve seen customers use it in pre-production environments. Today, I’m excited to announce that the Service Graph Connector for OpenTelemetry is generally available for production. Service Graph Connectors allow customers to load large volumes of data quickly and easily into their configuration management database (CMDB).

OpenTelemetry and OpenTracing are two related open source projects that aim to provide observability in modern distributed systems. While they have similar goals, there are some differences between them. Let's explore each project and their characteristics.

Insightful proof-of-concepts with a tool can be difficult to undertake due to the demands on valuable resources: time, energy, and people. With a task as grand as observability, how could one truly test if Honeycomb and OpenTelemetry are right for their organization and meet their requirements? For this thought experiment, here’s a comprehensive description of the ideal product evaluation over the course of four weeks, given unlimited resources.