The Collector is one of many tools that the OpenTelemetry project provides end users to use in their observability journey. It is a powerful mechanism that can help you collect telemetry in your infrastructure and it is a key component of a telemetry pipeline. The Collector helps you better understand what your systems are doing—but who watches the Collector?
Monitoring a homelab shouldn’t require a PhD in observability pipelines. Yet somehow, we all end up with a rat’s nest of exporters, agents, and databases that barely talk to each other. After years of fighting this complexity, I’ve landed on the OpenTelemetry Collector as the single tool that ties everything together.
ClickHouse is the other piece of the puzzle here. I’m definitely biased since I work with ClickHouse daily at my job, but if you look under the hood of just about any modern observability platform from the last few years, you’ll probably find a little ClickHouse in there. For me, it provides a unified platform that can store all of my telemetry signals alongside other types of events - a one-stop shop for “real-time” analytics.
Scrubbing Sensitive Data from OpenTelemetry Logs, Traces & Metrics · Dash0
Learn how to redact sensitive data from telemetry using the OpenTelemetry Collector with practical examples for attributes redaction and transform processors
"Why is the site slow?" hits differently when metrics look fine, but users are still frustrated.
Julia’s new guide on #WebsiteMonitoring shows how #OpenTelemetry + Dash0 make #RUM visible - so you can see the full story of real user behavior.
Read it here: https://dash0.link/website-monitoring
You can inspect the health of any OpenTelemetry Collector instance by checking its own internal telemetry. Read on to learn about this telemetry and how to configure it to help you monitor and troubleshoot the Collector.
Warning The Collector uses the OpenTelemetry SDK declarative configuration schema for configuring how to export its internal telemetry. This schema is still under development and may undergo breaking changes in future releases. We intend to keep supporting older schemas until a 1.0 schema release is available, and offer a transition period for users to update their configurations before dropping pre-1.0 schemas. For details and to track progress see issue #10808.
swi-k8s-opentelemetry-collector/deploy/helm/node-collector-config.yaml at aca1372f5210aeacab08e2e16e9a0b8c8a60a5f8 · gantrior/swi-k8s-opentelemetry-collector
Kubernetes infrastructure monitoring. Contribute to gantrior/swi-k8s-opentelemetry-collector development by creating an account on GitHub.
Collecting Prometheus Metrics with the OpenTelemetry Collector · Dash0
Bring Prometheus metrics into OpenTelemetry with ease This guide explains how to set up scale and optimize the Prometheus Receiver for observability pipelines
Tools such as Prometheus and OpenTelemetry help us monitor the health, performance, and availability of our complex distributed systems. Both are open source projects under the Cloud Native Computing Foundation (CNCF) umbrella – but what role does each play in observability?
OpenTelemetry (OTel for short), is a vendor-neutral open standard for instrumenting, generating, collecting, and exporting telemetry data. Prometheus is a fixture of the observability landscape, widely relied upon for monitoring and alerting within organizations.
Kubernetes annotation-based discovery for the OpenTelemetry Collector
In the world of containers and Kubernetes, observability is crucial. Users need to know the status of their workloads at any given time. In other words, they need observability into moving objects.
This is where the OpenTelemetry Collector and its receiver creator component come in handy. Users can set up fairly complex monitoring scenarios with a self-service approach, following the principle of least privilege at the cluster level.
The self-service approach is great, but how much self-service can it actually be? In this blog post, we will explore a newly added feature of the Collector that makes dynamic workload discovery even easier, providing a seamless experience for both administrators and users.
