Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on Distributed Tracing and related technologies.

Troubleshooting CORS Errors in Offsite API Calls

You may have wrestled with a web application attempting to call an offsite web service, such as an OpenTelemetry Collector, and gotten an odd error with the word CORS in it. Something like: Or, maybe you got a generic thrown error from your fetch statement that states Error: Failed to fetch …and you wondered, “What’s the problem, and how can I fix it?” These kinds of errors are called CORS errors, and they can be a bit confusing.

Critical Context: Adding Trace Quickview to Logz.io's Explore

Complexity rules the day within the world of data systems and pipelines. A goal for any observability practice is to help reduce complexity and give users and administrators a clear view of what’s happening in any system. This is the path to unified observability, a mature system where monitoring and troubleshooting are streamlined. This has been difficult to achieve for many organizations.

Monitoring your Express application using OpenTelemetry

Nodejs is a popular Javascript runtime environment that executes Javascript code outside of a web browser. Express is the most popular web frameworks that sits on top of Nodejs and adds functionalities like middleware, routing, etc. to Nodejs. You can monitor your express application using OpenTelemetry and a tracing backend of your choice.

Implementing OpenTelemetry in a Rust application for performance monitoring

OpenTelemetry can be used to trace Rust applications for performance issues and bugs. OpenTelemetry is an open-source project under the Cloud Native Computing Foundation (CNCF) that aims to standardize the generation and collection of telemetry data. Telemetry data includes logs, metrics, and traces. Rust is a multi-paradigm, general-purpose programming language designed for performance and safety, especially safe concurrency.