Copy of OTel Me All About OpenTelemetry The Current & Future State, Navigating the Project, and Getting Involved (2).pdf

OTel Me All About
OpenTelemetry
The Current & Future State,
Navigating the Project, and
Getting Involved
Reese Lee, New Relic

AGENDA
● Introductions
● Current & Future State
● Navigating the Project
● Getting Involved
● Q&A

INTRODUCTIONS
Reese Lee
Developer Relations Engineer
OpenTelemetry Community
Team, New Relic
Is also into: the paranormal, stand-up comedy, and all the
foods

INTRODUCTIONS
What is purpose of this webinar?
● To help end users navigate the community and project
● To encourage contributions

INTRODUCTIONS
What is the OpenTelemetry project?
● A collection of tools, APIs, and SDKs
● To help you analyze your software’s
performance and behavior
● Merging of OpenTracing and
OpenCensus in 2019

INTRODUCTIONS
What is OpenTelemetry not?
● OpenTelemetry != backend or
storage solution

CURRENT & FUTURE STATE
● What’s the current state of the project?
● What’s new and upcoming?

What’s the current state of the project?

opentelemetry.io/status

Data Model GA (2020) GA (2021) GA (2022)
API Spec GA (2021) GA (2022) In progress
SDK Spec GA (2021) GA (2022) In progress
Protocol GA (2021) GA (2022) GA (2022)
Implementations 8 GA, 4 in progress 0 GA, 5 RC, 7 in
progress
0 GA, 0 RC,
Collector usable in
prod
Traces Metrics Logs

What’s new and upcoming?
● Metrics RC and GA releases
● Proﬁles being added as a
new signal
● Logging GA targeted for 2023
● Instrumentation availability and quality
● Community demo application SIG
● End user discussion group

NAVIGATING THE PROJECT
● Concepts & Components
● Community
○ SIGs
○ Governance Committee
○ Technical Committee
● Documentation
● Bonus: OTEPs

What are some of the various OpenTelemetry concepts and components?
● API
● SDK
● Semantic conventions
● Speciﬁcation
● Collector
● OTLP

● API
● SDK
● Speciﬁcation
● Collector
● OTLP
Provides a standard way to collect
instrumentation data

● API
● SDK
● Speciﬁcation
● Collector
● OTLP
Provides standard ways to conﬁgure what
we want to do with the instrumentation
data collected by the API

● API
● SDK
● Speciﬁcation
● Collector
● OTLP
Conventional attributes that
describe common software
operations

● API
● SDK
● Speciﬁcation
● Collector
● OTLP
Provides blueprints for all of the
above to bring standardization
across all languages

● API
● SDK
● Speciﬁcation
● Collector
● OTLP
A highly conﬁgurable system for
processing telemetry data

● API
● SDK
● Speciﬁcation
● Collector
● OTLP How each data signal should be
encoded and transferred over
OpenTelemetry’s exchange protocol

What are the SIGs?
● Special Interest Groups
● Improve workﬂow, manage project efﬁciently
● Each SIG meets regularly, meeting notes and recordings are
available (check public calendar)
● Examples: Communications, Ruby, Collector

What is the Governance Committee?
● Role: “to be a live, responsive body that can refactor and reform
as necessary to adapt to a changing project and community”
What is the Technical Committee?
● Role: “responsible for all technical development within the
OpenTelemetry project”

What about documentation?
● opentelemetry.io/docs
● Communications SIG
● Some languages have more
comprehensive documentation than
others
● Standardization and improvements
under way

Bonus: What are OTEPs?
● OpenTelemetry Enhancement
Proposal
● OTEP process for proposing changes to
the speciﬁcation
● Cross-cutting changes that “introduce
new behaviour, change desired
behaviour, or otherwise modify
requirements”

GETTING INVOLVED
● How do I get help with using OpenTelemetry?
● What areas need help, and why should/how can I contribute?

GETTING INVOLVED
How do I get help with using OpenTelemetry?
● CNCF Slack
○ General (#opentelemetry)
○ Component-speciﬁc (#otel-___)
○ Vendor-speciﬁc or #otel-vendor
● Github

GETTING INVOLVED
How do I get help with using OpenTelemetry?
● End user discussion meeting (incoming)
○ #otel-endusers (invite required -
Rynn Mancuso or myself))
○ Look for updates or reach out to us
in #otel-user-research

GETTING INVOLVED
What areas need help, and why should/how can I contribute?

GETTING INVOLVED
● Honestly, everything
● But particularly:
○ Documentation
○ PHP
○ Instrumentation (deﬁning semantic conventions and
maintaining contributed instrumentation)

GETTING INVOLVED
Implementers have one view of the universe, end
users have another. We need more end users to speak
up and have a voice in the project!
Ted Young, co-founder of OpenTelemetry and
Director of Developer Education, Lightstep

GETTING INVOLVED
Juraci Paixão Kröhling, OpenTelemetry maintainer and
Software Engineer, Grafana

GETTING INVOLVED
…the biggest advantage is that companies can help shape the
project's direction according to their needs, and I don't mean it in a
bad way at all: a lot of times, the project maintainers make
decisions based on what they think users would want. Sometimes,
we have data or requests from actual customers, but it's not the
same thing: having the opinions of a diverse user base is essential
for the project's success.

GETTING INVOLVED
But one thing I see companies doing wrong is just telling their folks
to contribute, without a strategy in mind. So, my advice is to focus
on the areas that matter to the company, with a plan and strategic
direction. If they can get measurable goals attached to the
company's own goal, so much the better: this way, their open
source contributions become relevant to the company!

GETTING INVOLVED
I love working in open source because its
global nature exposes me to a very diverse set
of people, ideas, and opinions that would
otherwise be difficult to tap into.
Daniel Dyla, OpenTelemetry maintainer & Governance
Committee Member, and Senior Open Source Architect,
Dynatrace

GETTING INVOLVED
I also especially love the community feeling in
OpenTelemetry where vendors and platforms
who would ordinarily be considered competitors
can work together to improve the state of the
ecosystem for everybody involved.
Daniel Dyla, OpenTelemetry maintainer & Governance
Committee Member, and Senior Open Source Architect,
Dynatrace

GETTING INVOLVED
…participating and contributing to OSS helps
you hone your skills. If you have not worked for
a remote-first company before, joining an OSS
project will help you gain real world experience.
Ariel Valentin, OpenTelemetry contributor & adopter, and
Software Engineer Observability, GitHub

GETTING INVOLVED
● Was a great way to learn about PHP stuff from
experienced people, given I had little
● Helped me learn more about OTEL and the o11y
space as a whole
● Was a fun gateway to other OTEL channels to
learn even more and be aware of more people too
OpenTelemetry end user & contributor

GETTING INVOLVED
By contributing to an open source project
you will learn a lot from amazing engineers,
be at the forefront of innovation, and if the
project is success …being proud of all work
done
Henrik Rexed, OpenTelemetry contributor and Cloud
Native Advocate, Dynatrace

GETTING INVOLVED
● What are you interested in?
● Code and non-code contributions welcome
● Join:
○ Mailing lists
○ The appropriate SIG
○ Community meetings

GETTING INVOLVED
● Share your experiences and feedback about using
OpenTelemetry with us!
○ #otel-user-research (public)
○ #otel-endusers (invite-only)

Q&A
What else would you
like to know?

RESOURCES
OpenTelemetry links
● Ofﬁcial site
● Community Github
● Google calendar
● CNCF Slack
Get or keep in touch with me!
● LinkedIn (reese-lee)
● @reesesbytes (Twitter)

Copy of OTel Me All About OpenTelemetry The Current & Future State, Navigating the Project, and Getting Involved (2).pdf

More Related Content

Similar to Copy of OTel Me All About OpenTelemetry The Current & Future State, Navigating the Project, and Getting Involved (2).pdf (20)

More from LibbySchulze (20)

Recently uploaded (20)

Copy of OTel Me All About OpenTelemetry The Current & Future State, Navigating the Project, and Getting Involved (2).pdf