Home

Awesome

<img src="https://opentelemetry.io/img/logos/opentelemetry-logo-nav.png" alt="OpenTelemetry Icon" width="45" height=""> OpenTelemetry community content

<details> <summary> Table of Contents </summary> </details>

Get Involved

There is a lot to do! If you are interested in getting involved, here's how you can start:

  1. Check out our contributor guide to learn about our contribution process.
  2. Join our Slack and attend our community meetings.
  3. If you're interested in contributing to a specific part of the project, join the appropriate Special Interest Group (SIG).

Details for all of these items are below. We are a friendly, collaborative group and look forward to working together!

Governing Bodies

Both committees meet regularly, and the respective meeting notes are publicly available in the GC meeting notes and the TC meeting notes Google Docs. The Governance Committee meetings are also recorded. If you want to check out the recordings, head to the meeting recordings.

Areas of Interest

Technical committee members, maintainers, and approvers are encouraged to list their areas of interest in this document to help community members find interested parties and form new special interest groups.

Communication

Slack

For those who are brand new to OpenTelemetry and want to chat or get redirected to the appropriate place for a specific question, feel free to join the CNCF OpenTelemetry Slack channel. If you are new, you can create a CNCF Slack account here.

Calendar

The shared community calendar contains all public OpenTelemetry meetings, including weekly SIG meetings, monthly community meetings, etc. You can access it via:

The best way to subscribe to specific OpenTelemetry meeting series is to join the associated calendar-...@opentelemetry.io meeting invite groups below. This will invite you to the specific OpenTelemetry meetings, correctly block time for accepted meetings, and keep your calendar in sync with new and updated events.

Alternatively, if you wish to subscribe to all OpenTelemetry meeting series you can subscribe to calendar-all@opentelemetry.io.

Mailing Lists

List NameSignupMembershipWrite PermissionsRead PermissionsNotes
cncf-opentelemetry-community@lists.cncf.ioHereanyoneGC and TCanyone<details><summary>Notes</summary>The community mailing list is for anybody who wants to monitor the latest news from the project. It is used to send updates on community meetings and announcements about new projects and SIGs. There is minimal moderation for a new user to reduce spam, and new users are approved after one post.</details>
cncf-opentelemetry-contributors@lists.cncf.ioHereanyoneanyoneanyone<details><summary>Notes</summary>The discussions mailing list is for anyone who is interested in contributing to OpenTelemetry or has questions (related to the contribution, technical issues,etc) they’d like to discuss. Will be used to announce updates related to how the project is being developed and ask general contribution questions related to the contribution processes. No approval is required to join.</details>
cncf-opentelemetry-tc@lists.cncf.ioN/ATCanyonemembers<details><summary>Notes</summary>Used by the OpenTelemetry Technical Committee for internal communication. This mailing list should be used sparingly as we strive to keep all communication public. It only should be used to contact the Technical Committee with questions that cannot be discussed publicly on GitHub, GitHub discussions, or the community or contributors' mailing lists.</details>
cncf-opentelemetry-governance@lists.cncf.ioN/AGCanyonemembers<details><summary>Notes</summary>Used by the OpenTelemetry GC for internal communication. Additionally, contact the GC for questions that cannot be discussed publicly on GitHub, GitHub discussions, or other mailing lists. For instance, members could use this for issues related to improper applications of our community membership guidance.</details>
cncf-opentelemetry-comms@lists.cncf.ioHereGC and open for anyoneanyoneanyone<details><summary>Notes</summary>Mailing list to notify and request reviews of upcoming announcements, or request a post on the OpenTelemetry Twitter account or other public channels.</details>

Media

For PR & Marketing inquiries, please contact pr@cncf.io.

License

All OpenTelemetry projects are shipped under the permissive Apache 2.0 license as CNCF IP Policy dictates. This blog post explains the reasoning behind choosing this license.

Logos and Brand Guide

The OpenTelemetry logos and brand guide can be found in the CNCF artwork repository. In addition, a Google Slides template is also available.

How to

Special Interest Groups

We organize the community into Special Interest Groups (SIGs) to improve our workflow and more efficiently manage a community project. While meetings are expected to happen regularly, they are subject to contributors' availability and may be rescheduled or changed at time. Check our public calendar and SIG-specific GitHub discussions for meeting changes and cancellations. All meetings happen over Zoom, have a meeting notes document, and are recorded and available on Zoom cloud.

Please do not hesitate to contact SIG owners if the proposed time of the meeting or tools used is unavailable for you. For instance, it is a good practice to alternate morning/evening meetings once SIG has representatives from 3 largely distinct timezones. The best way to report it and suggest an alternative is to file an issue on this repository or discuss it in SIG-specific GitHub discussions.

[!NOTE] The meeting times in the tables below are given in 24-hour notation. All meeting hours between 2pm and 1am UTC are in Pacific Time (PT), with Daylight Saving Time. All meeting hours between 2am and 1pm UTC in UTC+8, without Daylight Saving Time.

<!-- sigs -->

Specification SIGs

NameMeeting TimeMeeting NotesSlack ChannelMeeting Invites GroupSponsorsGovernance Committee Liaison
Specification: GeneralTuesday at 08:00 PTGoogle Doc#otel-specificationcalendar-spec-general
Specification: SamplingThursday at 08:00 PTGoogle Doc#otel-samplingcalendar-spec-samplingJosh MacDonaldDaniel Dyla
Specification: ConfigurationEvery other Monday at 08:00 PTGoogle Doc#otel-config-filecalendar-spec-configCarlos Alberto,<br/>Jack BergTrask Stalnaker
Specification: LogsTuesday at 10:00 PTGoogle Doc#otel-spec-logscalendar-spec-logsTed Young,<br/>Trask StalnakerTed Young
Semantic Conventions: GeneralMonday at 08:00 PTGoogle Doc#otel-semantic-conventions-wgcalendar-semconvArmin Ruech,<br/>Josh Suereth,<br/>Reiley YangTrask Stalnaker
Semantic Conventions: ToolingWednesday at 07:00 PTGoogle Doc#otel-semantic-conventions-wgcalendar-semconvJosh Suereth
Semantic Conventions: MessagingThursday at 8:00 PTGoogle Doc#otel-messagingcalendar-semconvJohannes Tax,<br/>Liudmila MolkovaTrask Stalnaker
Semantic Conventions: DatabaseWednesday at 9:30 PT and Friday at 8:30 PTGoogle Doc#otel-db-client-semconv-stability-wgcalendar-semconvJack Berg,<br/>Liudmila MolkovaTrask Stalnaker
Semantic Conventions: System MetricsThursday at 07:30 PTGoogle Doc#otel-system-metrics-wgcalendar-semconvJosh SuerethSeverin Neumann
Semantic Conventions: K8sEvery other Wednesday at 08:00 PTGoogle Doc#otel-k8s-semconv-sigcalendar-semconvJosh Suereth,<br/>Alexander WertAlolita Sharma
Semantic Conventions and Instrumentation: GenAIAlternating between every other Thursday 10:00 PT and every other Thursday 14:00 UTC+8Google Doc#otel-genai-instrumentation-wgcalendar-semconvTed Young,<br/>Liudmila MolkovaTed Young
Semantic Conventions: CI/CDEvery Thursday at 06:00 PTGoogle Doc#otel-cicdcalendar-semconvJosh Suereth,<br/>Carlos AlbertoDaniel Gomez Blanco
Semantic Conventions: SecurityMeets during Semantic Conventions: GeneralGoogle Doc#otel-semconv-securitycalendar-semconvJosh SuerethTrask Stalnaker
Semantic Conventions: Feature FlagsEvery other Monday at 07:30 PTGoogle Doc#otel-ff-semconvcalendar-semconvDaniel Dyla,<br/>Alexander WertDaniel Dyla
Specification: EntitiesEvery other Thursday at 08:00 PTGoogle Doc#otel-entitiescalendar-entitiesJosh Suereth,<br/>Tigran NajaryanDaniel Dyla
Agent ManagementEvery other Wednesday at 11:00 PTGoogle Doc#otel-agentmanwgcalendar-agent-mgmtTigran NajaryanTed Young
Prometheus InteroperabilityEvery other Wednesday at 08:00 PTGoogle Doc#otel-prometheus-wgcalendar-prometheusAlolita Sharma
Functions as a Service (FAAS)Every other Wednesday at 8:00 PTGoogle Doc#otel-faascalendar-faasAustin Parker
ProfilingEvery other Thursday at 08:00 PTGoogle Doc#otel-profilescalendar-profilingJosh Suereth,<br/>Tigran NajaryanMorgan McLean
OpenTelemetry on MainframesTuesday at 10:00 PTGoogle Doc#otel-mainframescalendar-mainframeAlolita Sharma,<br/>Daniel Dyla,<br/>Morgan McLeanMorgan McLean
Client InstrumentationTuesday at 09:00 PTGoogle Doc#otel-client-side-telemetrycalendar-client-sideDaniel Gomez Blanco

Implementation SIGs

NameMeeting TimeMeeting NotesSlack ChannelMeeting Invites GroupGovernance Committee Liaison
Android: SDK + Automatic InstrumentationTuesday at 08:00 PTGoogle Doc#otel-androidcalendar-androidTrask Stalnaker
CollectorWednesday alternating between 09:00 PT, 05:00 PT, 17:00 PTGoogle Doc#otel-collectorcalendar-collectorJuraci Paixão Kröhling
C++: SDKAlternating between Monday at 13:00 PT and Wednesday at 09:00 PT PTGoogle Doc#otel-cppcalendar-cppSeverin Neumann
.NET: Automatic InstrumentationWednesday at 09:00 PTGoogle Doc#otel-dotnet-auto-instrcalendar-dotnetMorgan McLean
.NET: SDKTuesday alternating between 09:00 PT and 16:00 PTGoogle Doc#otel-dotnetcalendar-dotnetMorgan McLean
Erlang/Elixir: SDKEvery other Thursday at 09:00 PTGoogle Doc#otel-erlang-elixircalendar-erlangAustin Parker
GoLang: SDKThursday alternating between 09:00 PT and 10:00 PTGoogle Doc#otel-gocalendar-goTed Young
GoLang: Automatic InstrumentationEvery other Tuesday at 09:30 PTGoogle Doc#otel-go-instrumentationcalendar-goJuraci Paixão Kröhling
Java: SDK + InstrumentationThursday at 09:00 PT, and every other Thursday at 09:00 UTC+8Google Doc#otel-javacalendar-javaTrask Stalnaker
JavaScript: SDKWednesday at 09:00 PTGoogle Doc#otel-js and GitHub Discussionscalendar-jsDaniel Dyla
PHP: SDKWednesday at 10:30 PTGoogle Doc#otel-phpcalendar-phpSeverin Neumann
Python: SDKThursday at 09:00 PTGoogle Doc#otel-pythoncalendar-pythonDaniel Gomez Blanco
Ruby: SDKTuesday at 09:00 PTGoogle Doc#otel-ruby and GitHub Discussionscalendar-rubyTed Young
Rust: SDKTuesday at 09:00 PTGoogle Doc#otel-rust and Gittercalendar-rustTed Young
Swift: SDKThursday at 09:00 PTGoogle Doc#otel-swiftcalendar-swiftAlolita Sharma
eBPFTuesday at 09:00 PTGoogle Doc#otel-ebpfcalendar-ebpfTed Young
Kubernetes OperatorThursday at 09:00 PTGoogle Doc#otel-operatorcalendar-k8s-operatorJuraci Paixão Kröhling
Community Demo ApplicationWednesday at 08:00 PTGoogle Doc#otel-community-democalendar-demo-appAustin Parker

Cross-Cutting SIGs

NameMeeting TimeMeeting NotesSlack ChannelMeeting Invites GroupGovernance Committee Liaison
Maintainer MeetingMonday at 09:00 PTGoogle Doc#otel-maintainerscalendar-maintainer-meetingMorgan McLean
Communications (Website, Documentation, etc.)Every other Monday at 10:00 PTGoogle Doc#otel-commscalendar-commsSeverin Neumann
End-User SIGEvery other Thursday at 10:00 PTGoogle Doc#otel-user-researchcalendar-user-researchDaniel Gomez Blanco
SecurityEvery other Wednesday at 07:00 PTGoogle Doc#otel-sig-securitycalendar-sig-securityJuraci Paixão Kröhling
Project InfrastructureWednesday at 08:00 PTGoogle Doc#otel-project-infracalendar-project-infraAustin Parker
Contributor ExperienceMonday alternating between 10:00 PT and 17:00 UTC+8Google Doc#otel-contributor-experiencecalendar-contributor-experienceJuraci Paixão Kröhling
Developer ExperienceWednesday 11:00 PT and 17:00 UTC+8Google Doc#otel-devexcalendar-developer-experienceAustin Parker
<!-- endsigs -->

Related groups

W3C - Distributed Tracing Working Group

Join W3C Distributed Tracing Working Group to discuss standardization efforts in distributed tracing space.

Erlang Ecosystem Foundation – Observability Working Group

The Erlang and Elixir API and SDK are maintained by the Erlang Ecosystem Foundation Observability Working Group members. See the Observability Working Group page on the EEF website for details.

CNCF TAG Observability - Technical Advisory Group

The CNCF TAG Observability is a technical advisory group for observability that focuses on topics pertaining to the observation of cloud native workloads. Check out the CNCF TAG Observability page for details.

K8s SIG - Instrumentation Special Interest Group

The K8s SIG Instrumentation special interest group coordinates metric requirements of different SIGs for other components through finding common APIs. This group also covers best practices for cluster observability through metrics, logging, and events across all Kubernetes components. See the Instrumentation Special Interest Group for details on joining this group.

OpenMetrics

OpenMetrics is an effort to create an open standard for transmitting metrics at scale, supporting text representation and Protocol Buffers. See the OpenMetrics page for details.

eBPF Foundation

The eBPF foundation aims to facilitate collaboration between eBPF projects, and to ensure good maintenance and clear roadmap for eBPF core. See the eBPF Foundation page for more details.