OpenTelemetry

OpenTelemetry community content

Stars
654
Forks
213
Open issues
108
Closed issues
931
Last commit
5 months ago
Watchers
654
Total releases
0
Total commits
698
Open PRs
7
Closed PRs
590
Repo URL
Project Website
https://opentelemetry.io/
Platform
License
apache-2.0
Category
Technology
c#
Offers premium version?
NO
Proprietary?
NO
About

OpenTelemetry community content

Table of Contents

  • Get Involved
  • Governing Bodies
  • Areas of Interest
  • Communication
    • Discussions
    • Calendar
    • Mailing Lists
    • Media

  • License
  • Logos and Brand Guide
  • How to
  • Special Interest Groups

    • Specification SIGs
    • Implementation SIGs

  • Related groups

    • W3C - Distributed Tracing Working Group
    • Erlang Ecosystem Foundation – Observability Working Group
    • CNCF TAG Observability - Technical Advisory Group
    • K8s SIG - Instrumentation Special Interest Group
    • OpenMetrics
    • eBPF Foundation

Get Involved

There is a lot to do! If you are interested in getting involved, please join the mailing lists and attend the community meetings. If you're interested in contributing to a specific part of the project, please 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 Discussions

We use GitHub discussions for most communications. Please join us there!

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 OpenTelemetry events is to join the calendar updates Google Group. This will invite you to every OpenTelemetry call and correctly block time for accepted events, and it will keep your calendar in sync with new and updated events.

(Internal Note: When creating or updating a calendar event in the OpenTelemetry Public Calendar, please ensure that opentelemetry-calendar@googlegroups.com is added as an attendee to the meeting invite. This is what allows updates to the calendar to be synchronized to other attendees.)

Mailing Lists

List Name Signup Membership Write Permissions Read Permissions Notes

cncf-opentelemetry-community@lists.cncf.io Here anyone GC and TC anyone

NotesThe 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.

cncf-opentelemetry-contributors@lists.cncf.io Here anyone anyone anyone

NotesThe 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.

cncf-opentelemetry-tc@lists.cncf.io N/A TC anyone members

NotesUsed 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.

cncf-opentelemetry-governance@lists.cncf.io N/A GC anyone members

NotesUsed 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.

cncf-opentelemetry-comms@lists.cncf.io Here GC and open for anyone anyone anyone

NotesMailing list to notify and request reviews of upcoming announcements, or request a post on the OpenTelemetry Twitter account or other public channels.

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. Refer to CONTRIBUTING.md for details on code attribution.

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.

Specification SIGs

Name Meeting Time Meeting Notes Slack Channel

Technical Committee Sponsors

Specification: General Every Tuesday at 08:00 PT Google Doc #otel-specification

Specification: Logs Merged into "Specification: General" See above #otel-logs Tigran Najaryan

Specification: Sampling Every Thursday at 08:00 PT Google Doc #otel-sampling Josh MacDonald

Specification: Configuration Every other Monday at 8:00 PT Google Doc #otel-config-file Carlos Alberto

Specification: Events Every Friday at 10:00 AM PT Google Doc #otel-event

Jack Berg
Tigran Najaryan

Semantic Conventions: General Every Monday at 08:00 PT Google Doc #otel-semantic-conventions-wg

Armin Ruech
Josh Suereth
Reiley Yang

Semantic Conventions: Messaging Every Thursday at 8:00 PT Google Doc #otel-messaging

Semantic Conventions: System Metrics Every Thursday at 08:30 PT Google Doc #otel-system-metrics-wg Josh Suereth

Implementation SIGs

Name Meeting Time Meeting Notes Slack Channel

Maintainers Meeting Every Monday at 09:00PT Google Doc #otel-maintainers

Collector Every Wednesday at 09:00 PT plus monthly on first Wednesday at 00:00 PT and on third Wednesday at 16:00 PT Google Doc #otel-collector

C/C++: SDK Every week alternating between Monday at 13:00 PT and Wednesday at 9:00 PT Google Doc #otel-cpp

.NET: Automatic Instrumentation Every Wednesday at 9:00 PT Google Doc #otel-dotnet-auto-instr

.NET: SDK Every Tuesday alternating between 9:00 and 16:00 PT Google Doc #otel-dotnet

Erlang/Elixir: SDK Every other Thursday at 9:00 PT Google Doc #otel-erlang-elixir

GoLang: SDK Every Thursday alternating between 10:00 and 15:00 PDT Google Doc #otel-go

GoLang: Automatic Instrumentation Every other week on Tuesday at 9:30 PT Google Doc #otel-go-instrumentation

Java: SDK + Automatic Instrumentation Every Thursday at 09:00 PT Google Doc #otel-java

JavaScript: SDK Every Wednesday at 09:00 PT Google Doc

#otel-js and GitHub Discussions

PHP: SDK Every Wednesday at 10:30 PT Google Doc #otel-php

Python: SDK Every Thursday at 09:00 PT Google Doc #otel-python

Ruby: SDK Every Tuesday at 09:00 PT Google Doc

#otel-ruby and GitHub Discussions

Rust: SDK Every Tuesday at 16:00 UTC Google Doc

#otel-rust and Gitter

Swift: SDK Every Thursday at 09:00 PT Google Doc #otel-swift

Communications (Website, etc.) Every other week on Monday at 10:00 PT Google Doc #otel-comms

End-User WG Every other week on Thursday at 10:00 PT Google Doc #otel-user-research

eBPF Every week on Tuesday at 09:00 PT Google Doc #otel-ebpf

Agent Management WG Every other week on Tuesday at 11:00 PT Google Doc #otel-agentmanwg

Prometheus Interoperability WG Every other week on Wednesday at 08:00 PT Google Doc #otel-prometheus-wg

Client Instrumentation Every Tuesday at 9:00 AM PT Google Doc #otel-client-side-telemetry

Kubernetes Operator Every other week on Thursday at 09:00 PT Google Doc #otel-operator

Community Demo Application Every Monday at 8:30 PT Google Doc #otel-community-demo

Functions as a Service (FAAS) Every other Tuesday at 12:00 PM PT Google Doc #otel-faas

Profiling WG Every other week on Thursday at 08:00 AM PT Google Doc #otel-profiles

Security Weekly on Wednesday at 08:30 AM PT Google Doc #otel-sig-security

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.

Alternative Projects

Subscribe to Open Source Businees Newsletter

Twice a month we will interview people behind open source businesses. We will talk about how they are building a business on top of open source projects.

We'll never share your email with anyone else.