Operations | Monitoring | ITSM | DevOps | Cloud

OpenTelemetry is the go-to open-source standard for observability, but when it comes to tracking frontend performance and user interactions, things get a little tricky. Unlike backend services, browsers introduce challenges like CORS restrictions, asynchronous execution, and limited access to certain telemetry data. This guide covers everything you need to know about using OpenTelemetry in the browser, from setup to best practices, advanced configurations, and real-world debugging techniques.

Aerospike is a high-performance, real-time NoSQL database built for speed, scale, and low-latency transactions—think millions of reads/writes per second without breaking a sweat. When you're dealing with high-throughput applications, keeping an eye on Aerospike’s performance isn't just a good idea—it's mission-critical to avoid bottlenecks, connection issues, or unexpected slowdowns.

OpenTelemetry (often abbreviated as OTel) is the golden standard observability framework, allowing users to collect, process, and export telemetry data from their systems. OpenTelemetry’s framework is organized into distinct signals, each offering an aspect of observability. Among these signals, OpenTelemetry metrics are crucial in helping engineers understand their systems.

Modern applications are becoming increasingly complex, and debugging distributed systems can feel like searching for a needle in a haystack. This is where OpenTelemetry (OTel) comes in. If you're using NestJS, integrating OpenTelemetry can provide deep insights into your application's behavior, helping you track performance, troubleshoot issues, and understand service interactions.

Logs play a critical role in observability, but they do come with their own challenges. Grafana Loki, our horizontally scalable, highly available, multi-tenant log aggregation system, addresses these challenges head on, giving you an open source tool that’s both cost effective and easy to operate.

OpenTelemetry is an open-source observability framework designed to instrument, generate, collect, and export telemetry data, including traces, metrics, and logs. It is vendor-agnostic, allowing developers to send data to multiple backend services like Last9, Prometheus, Datadog, or Jaeger without vendor lock-in. For Next.js applications, OpenTelemetry is particularly useful due to the framework’s hybrid rendering approach.

OpenTelemetry is a big, big project. It’s so big, in fact, that it can be hard to know what part you’re talking about when you’re talking about it! One particular critique I’ve seen going around recently, though, is about how OpenTelemetry is just ‘three pillars’ all over again. Reader, this could not be further from the truth, and I want to spend some time on why.

Snowflake is a powerful, cloud-based data platform designed for high-performance analytics. Whether you're running massive analytical queries, managing structured and semi-structured data, or optimizing data pipelines, visibility into your Snowflake instance is essential. Performance bottlenecks, query execution delays, and unexpected cost spikes can quickly become issues without proper monitoring.

If you've ever tried to set up OpenTelemetry visualization, you know it can be a bit overwhelming. But don't worry—in this guide, we'll break it all down step by step. Whether you're just getting started or looking to fine-tune your existing setup, this walkthrough will help you get the most out of your telemetry data.

If you’ve ever struggled with understanding distributed traces, managing metrics, or debugging complex applications, OpenTelemetry is your best friend. But what about the OpenTelemetry UI? How do you visualize and interact with all that telemetry data? In this guide, we’ll explore the best ways to use OpenTelemetry’s UI options, from setting up a proper observability stack to choosing the right front-end visualization tools.