Simple otelcontribcol Configuration

Configuration of the collector is broken down into FIVE Parts:

• Services
  • Binds Receivers and Exporters
• Receivers
  • Receiver or Scrape Data
  • A receiver is how data gets into the OpenTelemetry Collector. Generally, a receiver accepts data in a specified format, translates it into the internal format and passes it to processors and exporters defined in the applicable pipelines.
• Processors
  • Update Data
• Exporters
  • Send Data Downstream
• Extensions
  • Utilities for the Collector
  • Typically,has an HTTP interface
• Connectors
  • A connector is both an exporter and receiver. As the name suggests a Connector connects two pipelines: it consumes data as an exporter at the end of one pipeline and emits data as a receiver at the start of another pipeline. It may consume and emit data of the same data type, or of different data types. A connector may generate and emit data to summarize the consumed data, or it may simply replicate or route data.

Name	opentelemetry-collector	opentelemetry-collector-contrib
Service	Default	N/A
Exporter	Default	Default
Receiver	Default	Default
Extensions	Default	Default
Processor	Default	Default
Connector	Default	Default
Examples	Default	Default

## Services

https://github.com/open-telemetry/opentelemetry-collector/tree/main/service https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/service

Receivers

There are many receivers alreay built for capturing data from an enterprise resources.
The default receivers in the opentelemetry-collector There are receviers for virtually everything.

Exporters

Exporters many exporters alreay built for pushing data to collection points

The Default exporters in the opentelemetry-collector

Processors

Ther are two default

https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor

Extensions :

https://github.com/open-telemetry/opentelemetry-collector/tree/main/extension https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension

Performance Profiler

Performance Profiler : Performance Profiler extension enables the golang net/http/pprof endpoint. This is typically used by developers to collect performance profiles and investigate issues with the service.

http://localhost:1777/debug/pprof/

Health Check

Heath Check: http://localhost:13133

Returns :

{"status":"Server available","upSince":"2024-03-25T15:27:25.183526-04:00","uptime":"17m49.470455792s"}

zPages

http://localhost:55679/debug/servicez