Presented at Open Source 101 2023 - Charlotte Presented by Eric D Schabell, Chronosphere Title: Observability For You and Me with openTelemetry Abstract: Are you interested in dipping your toes in the cloud native observability waters, but as an engineer you are not sure where to get started with tracing problems through your microservices and application landscapes on Kubernetes? Then this is the session for you, where we take you on your first steps in an active open-source project that offers a buffet of languages, challenges, and opportunities for getting started with telemetry data. The project is called openTelemetry, but before diving into the specifics, we’ll start with de-mystifying key concepts and terms such as observability, telemetry, instrumentation, cardinality, percentile to lay a foundation. After understanding the nuts and bolts of observability and distributed traces, we’ll explore the openTelemetry community; its Special Interest Groups (SIGs), repositories, and how to become not only an end-user, but possibly a contributor.We will wrap up with an overview of the components in this project, such as the Collector, the OpenTelemetry protocol (OTLP), its APIs, and its SDKs. Attendees will leave with an understanding of key observability concepts, become grounded in distributed tracing terminology, be aware of the components of openTelemetry, and know how to take their first steps to an open-source contribution! To find more talks by Eric D Schabell: https://www.slideshare.net/eschabell

1. chronosphere.io

2. chronosphere.io
Cloud Native O11y (at scale)
Nuts & Bolts of OpenTelemetry
Getting
Your Feet Wet

3. chronosphere.io
Cloud Native Observability at Scale

4. chronosphere.io
Cloud Native

5. chronosphere.io
Data complexity
Experiment:
- Hello World app on 4 node
Kubernetes cluster with Tracing,
End User Metrics (EUM), Logs,
Metrics (containers / nodes)
- 30 days == +450 GB

6. chronosphere.io

7. chronosphere.io
Cloud Native at Scale

8. chronosphere.io
Simple O11y

9. chronosphere.io
O11y at Scale (over time…)

10. chronosphere.io
“It’s remarkable how common this
situation is, where an organization
is paying more for their
observability data, than they do
for their production
infrastructure.”

11. chronosphere.io
O11y at Scale (need)

12. chronosphere.io
Telemetry is automatically collecting, transmitting
and measuring data from remote sources. It
transmits data back to a central location and
analyzes to monitor and control remote systems.

13. chronosphere.io
Nuts & Bolts of
OpenTelemetry

14. chronosphere.io
https://opentelemetry.io

15. chronosphere.io
OpenTelemetry is not an
observability back-end.

16. chronosphere.io
Traces give us the big picture and understanding
the full path a request takes in your application.
Spans represents a unit of work or operation and
are building blocks of traces.

17. chronosphere.io

18. chronosphere.io
Applications (Java)
OTel Auto Instrumentation (libraries)
OTel API
OTel SDK
OTel Collector
OTLP
OTLP
OTLP
(Auto) instrumentation

19. chronosphere.io
Host
Observability Backend
(Prometheus, Jaeger, Fluent Bit, etc.),
Applications
OTel Auto Instrumentation
OTel API
OTel SDK
OTel Collector Agent
OTLP
OTLP
OTLP
OTLP
OTLP
Collector (agent)

20. chronosphere.io
Host
Host
Host
Observability Backend
(Prometheus, Jaeger, Fluent Bit, etc.),
Applications
OTel Auto Instrumentation
OTel API
OTel SDK
OTel Collector Agent
OTLP
OTLP
OTLP
OTLP
Collector (gateway)
OTel Collector Gateway

21. chronosphere.io
Observability Backend
(Prometheus, Jaeger, Fluent Bit, etc.),
OTel Collector
OTLP
Telemetry
(Spans)
Collector (internals)
Receiver Processor Exporter

22. chronosphere.io
Spans and Traces

23. chronosphere.io
Kubernetes Operator

24. chronosphere.io
Getting Your Feet Wet

25. chronosphere.io
CNCF - cloud-native.slack.com

26. chronosphere.io
Special Interest Groups

27. chronosphere.io
CNCF - End User Community

28. Questions?
Eric D. Schabell
Director Evangelism
@ericschabell{@fosstodon.org}