MyObservability

🟦 OpenTelemetry (OTel)

OpenTelemetry (also referred to as OTel) is an open-source observability framework made up of a collection of tools, APIs, and SDKs. Otel enables IT teams to instrument, generate, collect, and export telemetry data for analysis and to understand software performance and behavior.

OTel Provides:

• A single, vendor-agnostic instrumentation library per language with support for both automatic and manual instrumentation.
• A single vendor-neutral collector binary that can be deployed in a variety of ways.
• An end-to-end implementation to generate, emit, collect, process and export telemetry data.
• Full control of your data with the ability to send data to multiple destinations in parallel through configuration.
• Open-standard semantic conventions to ensure vendor-agnostic data collection
• The ability to support multiple context propagation formats in parallel to assist with migrating as standards evolve.
• A path forward no matter where you are on your observability journey.

🟥 OpenTelemetry Specifications

• OpenTelemetry Protocol (OTLP): OTLP defines how telemetry data is encoded, transported, and delivered between various entities.
• OpenTelemetry APIs: Used to instrument code to generate telemetry data (traces, metrics, and logs)
• OpenTelemetry SDKs: OTel SDK is an implementation of the OpenTelemetry API
• OpenTelemetry Exporter: Configured to send data to the collector or directly to the backend observability tool.
• OpenTelemetry Collector: configure how telemetry data received, processed, and exported to a backend observability
  • Receiver: Takes in data generated from the service.
  • Processor: processing the received data through tail sampling, normalizing data, adding resource attributes, and more.

---

🟥 OpenTelemetry Types

Types:

• Generic
• Vendor specific

Generic OTel A standard, vendor-neutral agent provided by the OpenTelemetry project, often built using the OpenTelemetry Collector. This is supported by CNCF

• Full control
• Multi-vendor support
• Sending data to multiple destinations
• Vendor agnostic
• Flexible.

⚠️ Generic OpenTelmetry is more complex to manage.

Vendor specific OpenTelemetry a customized OpenTelemetry distribution from a vendor, often including the OpenTelemetry Collector or SDK wrapped with:

• Custom processors/exporters
• Pre-configured settings
• Integrated identity, security, enrichment, or discovery features

It is

• Easy setup
• Tuned performance for that vendor’s platform
• SLAs, enterprise support
• May include auto-instrumentation enhancements

⚠️ Might not support all generic processors/exporters. Might be vendor dependent.

🟥 Tutorial

OpenTelemetry (Generic)

1. Introduction
2. Recommended Setup
3. Architecture
4. Demo Application
5. OpenTelemetry Specification
6. Instrumentation
   • Automatic Instrumentation
   • Instrumentation Libraries
   • Manual Instrumentation
     • Traces
     • Metrics
     • Logs
7. Collector
8. Sampling
9. Step by Step Guide
10. Setup your own Telemetry
11. Platform - Kubernetes

OpenTelemetry (Vendor Specific)

1. Dynatrace
2. Grafana
3. Splunk
4. NewRelic

---

My Contact Information

👉 LinkedIn GitHub My Page

My Other sites
👉 My Observability My AIOps My A.I. My Architecture

---