Home / Companies / New Relic / Blog / Post Details
Content Deep Dive

Use the OpenTelemetry Collector and visualize your data

Blog post from New Relic

Post Details
Company
Date Published
Author
Jack Berg, New Relic Engineer, OpenTelemetry Java Maintainer
Word Count
1,163
Company Posts That Month
18
Language
English
Hacker News Points
-
Post removed?
No
Summary

The OpenTelemetry Collector is a powerful tool for building telemetry data pipelines, allowing users to collect, process, and export data from various sources in a highly configurable and extensible manner. It can accept different formats of telemetry data, such as Prometheus, Jaeger, Kafka, and Zipkin, and apply common processing before exporting it to a backend observability platform. The Collector has two main deployment methods: agent and gateway. An agent is a program that collects telemetry data from a host and forwards it to a collector, while a gateway receives data from multiple agents and sends it to configured backends. The OpenTelemetry Collector can also be used as an agent on every host, enriching the data with host metadata before forwarding it on. It is highly configurable and extensible, allowing users to adapt it to their environment and add custom exporters as needed. The collector has two main deployment methods: agent and gateway. An agent is a program that collects telemetry data from a host and forwards it to a collector, while a gateway receives data from multiple agents and sends it to configured backends. The OpenTelemetry Collector can also be used as an agent on every host, enriching the data with host metadata before forwarding it on. It is highly configurable and extensible, allowing users to adapt it to their environment and add custom exporters as needed.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
OpenTelemetry 36 326 16 7 -13%
Observability 3 696 111 38 +86%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.