OpenTelemetry

Filtering and parsing data with the OpenTelemetry Collector: a beginner's guide. Not all data comes out perfect from OpenTelemetry instrumentation, but rather than mucking with it in your datastore, the collector can can filter, sort, compress, and parse data before it's sent. Nočnica shows you how to do basic log and metrics transformations within the collector. #opentelemetry #observability #otel

Component(s) extension/storage/redisstorage What happened? Description Empty otlp messages are emitted when the otlp exporter is configured with the sending queue enabled and the redis storage exte...

Build resilient pipeline, without overkill of streaming to kafka. Checkout how it is done!

Having now used Datadog and Honeycomb for a while I have realized that Datadog is like an encyclopedia. All of your data gets dumped in to this platform with… | 18 comments on LinkedIn

IBM Community is a platform where IBM users converge to solve, share, and do more.

Since there is no fix for helm/helm#12879 yet, this provides an alternate way to provide configuration with the collector. This new field should really only be used when the collector is used as a ...

I recently set up the OpenTelemetry Collector (HostMetrics) to send data to Prometheus/Mimir and are using the following Grafana dashboard (https://grafana.com/grafana/dashboards/20376-opentelemetry-

Contrib repository for the OpenTelemetry Collector - open-telemetry/opentelemetry-collector-contrib

Hello. This follows issue #591 After doing more investigation, it looks like the datadog agent is sometime (depending on where you are hosted) taking more than 1 minute to initialize. blocking the ...

Introduction The OpenTelemetry Collector is an important tool for monitoring a Kubernetes cluster and all the services that in within. To facilitate installation and management of a collector deployment in a Kubernetes the OpenTelemetry community created the OpenTelemetry Collector Helm Chart. This helm chart can be used to install a collector as a Deployment, Daemonset, or Statefulset. Installing the Chart To install the chart with the release name my-opentelemetry-collector, run the following commands:

Status: Development This document provides a placeholder for specifying an OTLP exporter capable of exporting to either a file or stdout. Currently, it only describes the serialization of OpenTelemetry data to the OTLP JSON format. Table of Contents Use Cases Exporter configuration Programmatic configuration JSON File serialization File storage requirements JSON lines file Streaming appending Telemetry data requirements Examples Use Cases Why do we need a file exporter - why not just use the OTLP exporter?

The OpenTelemetry Collector supports many different receivers and processors to facilitate monitoring Kubernetes. This section covers the components that are most important for collecting Kubernetes data and enhancing it. Components covered in this page: Kubernetes Attributes Processor: adds Kubernetes metadata to incoming application telemetry. Kubeletstats Receiver: pulls node, pod, and container metrics from the API server on a kubelet. Filelog Receiver: collects Kubernetes logs and application logs written to stdout/stderr. Kubernetes Cluster Receiver: collects cluster-level metrics and entity events. Kubernetes Objects Receiver: collects objects, such as events, from the Kubernetes API server. Prometheus Receiver: receives metrics in Prometheus format. Host Metrics Receiver: scrapes host metrics from Kubernetes nodes. For application traces, metrics, or logs, we recommend the OTLP receiver, but any receiver that fits your data is appropriate.

Learn how the OpenTelemetry Operator works and follow a step-by-step guide on how to use it to instrument your applications.

Here are five OpenTelemetry best practices based on lessons learned during a roundtable we hosted. Read the blog or watch the webinar.

How can one test if Honeycomb and OpenTelemetry are right for their organization? Kyle provides a four week plan to properly find out.

In this blog, Mike Terhar talks about how to use the Headers Setter extension to work around header setting issues.

OpenTelemetry offers a variety of options to manage data residency concerns, like where to route telemetry data & ways to filter/redact it.

In this guest post, Chris Lasher shares how to send OTel data from AWS Lambda to Honeycomb in a step-by-step tutorial with code blocks.

In part 3 of this OpenTelemetry Best Practices series, Martin Thwaites goes over the Transform processor and redacting sensitive data.

In part 2 of this OpenTelemetry Best Practices series, Martin Thwaites goes over agents, the Collector, coded instrumentation, & more.

In part 1 of this OpenTelemetry Best Practices series, Martin Thwaites goes over naming, where consistency and standardization are key.

The recommended approach to deploying Collectors in K8s doesn’t work in AKS. Martin walks you through the adjustments you need to make.

A terminal OpenTelemetry viewer inspired by otel-desktop-viewer - ymtdzzz/otel-tui

desktop-collector. Contribute to CtrlSpice/otel-desktop-viewer development by creating an account on GitHub.

A free & open-source OpenTelemetry dashboard for deep insights into your apps on your local development machine.Aspire Dashboard for OpenTelemetry

OpenTelemetry backend in a Docker image. Contribute to grafana/docker-otel-lgtm development by creating an account on GitHub.

OpenTelemetry Helm Charts. Contribute to open-telemetry/opentelemetry-helm-charts development by creating an account on GitHub.

OpenTelemetry Helm Charts. Contribute to open-telemetry/opentelemetry-helm-charts development by creating an account on GitHub.

Contribute to signalfx/splunk-otel-collector development by creating an account on GitHub.

Example of how to setup an OTLP exporter for metrics - MrAlias/otel-otlp-metric-example