Created
June 4, 2025 22:18
-
-
Save halcyondude/66828e4acd89fd2975183ac3c839381d to your computer and use it in GitHub Desktop.
2025-06-04 OpenTelemetry Graduation Review
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| - [**I. Introduction**](#i-introduction) | |
| - [**II. Project Alignment with CNCF Mission**](#ii-project-alignment-with-cncf-mission) | |
| - [**III. CNCF Code of Conduct Adoption**](#iii-cncf-code-of-conduct-adoption) | |
| - [**IV. Trademark Guidelines Adherence**](#iv-trademark-guidelines-adherence) | |
| - [**V. Open Governance**](#v-open-governance) | |
| - [**VI. Clear Release Process**](#vi-clear-release-process) | |
| - [**VII. Public Communication Channels**](#vii-public-communication-channels) | |
| - [**VIII. Contributor Diversity \& Sustained Activity**](#viii-contributor-diversity--sustained-activity) | |
| - [**IX. End User Adoption**](#ix-end-user-adoption) | |
| - [**X. Security Audit**](#x-security-audit) | |
| - [**XI. Project Roadmap**](#xi-project-roadmap) | |
| - [**XII. Mentoring and Community Programs**](#xii-mentoring-and-community-programs) | |
| - [**XIII. Website and Documentation**](#xiii-website-and-documentation) | |
| - [**XIV. CI/CD Integration**](#xiv-cicd-integration) | |
| - [**XV. License Compliance**](#xv-license-compliance) | |
| - [**XVI. Contributor License Agreement (CLA) / Developer Certificate of Origin (DCO)**](#xvi-contributor-license-agreement-cla--developer-certificate-of-origin-dco) | |
| - [**XVII. OpenSSF Best Practices Badge**](#xvii-openssf-best-practices-badge) | |
| - [**XVIII. CLO Monitor**](#xviii-clo-monitor) | |
| - [**XIX. Other Relevant Information**](#xix-other-relevant-information) | |
| - [**XX. Conclusion**](#xx-conclusion) | |
| - [**XXI. Appendix: Source Links**](#xxi-appendix-source-links) | |
| - [**Works cited**](#works-cited) | |
| **Authors:** Dims, Matt Young, Alolita Sharma | |
| **Reviewers:** | |
| * \[ \] Austin Parker | |
| * \[ \] Ted Young | |
| * \[ \] *(Add more reviewers here)* | |
| ## **I. Introduction** | |
| OpenTelemetry has established itself as a pivotal project within the Cloud Native Computing Foundation (CNCF) ecosystem, currently holding an incubating status. Its mission is to provide high-quality, ubiquitous, and portable telemetry (traces, metrics, logs, and more recently, profiles) to enable effective observability across cloud-native environments [1]. This report compiles the necessary due diligence information required for OpenTelemetry's application to advance from Incubation to Graduation status within the CNCF. The criteria for Graduation, as outlined in the CNCF TOC's template [3], emphasize demonstrated maturity in governance, community health, technical robustness, security, and widespread adoption. This document will provide verifiable links and evidence for each checklist item, drawing from official OpenTelemetry documentation, community repositories, and other public sources. | |
| The significance of CNCF Graduation is substantial; it signifies that a project has achieved a high level of stability, is widely adopted in production, and is supported by a healthy, diverse, and sustainable community [4]. This report aims to demonstrate OpenTelemetry's fulfillment of these rigorous standards. | |
| ## **II. Project Alignment with CNCF Mission** | |
| * **Requirement**: \[ \] The project aligns with the CNCF's mission to make cloud native computing ubiquitous. | |
| * **Data Point**: | |
| * OpenTelemetry's core mission is to enable effective observability by making high-quality, portable telemetry ubiquitous [1]. This directly supports the CNCF's goal of making cloud-native computing ubiquitous by providing essential tools for understanding and managing complex cloud-native applications and infrastructure. | |
| * It provides a vendor-neutral, open-source standard for telemetry data (traces, metrics, logs, profiles), allowing interoperability across various tools and platforms, which is fundamental to the CNCF's open-source ethos [1]. | |
| * OpenTelemetry is designed for modern distributed systems and microservices architectures, which are central to cloud-native paradigms [6]. | |
| * The OpenTelemetry project's history is of a merger between 2 projects (OpenTracing and OpenCensus) and a fragmented, but energetic and collaborative contributor communities, aiming to unify the landscape for telemetry collection [8]. | |
| * CNCF itself highlights OpenTelemetry as a key observability tool, consistently ranked in "Adopt" or "Trial" rings in CNCF Tech Radar reports, and crucial for managing complex cloud-native systems [9]. | |
| * **Context & Analysis**: OpenTelemetry's focus on standardized, vendor-neutral observability is critical for the health and growth of the cloud-native ecosystem. Effective observability is a prerequisite for operating complex, distributed cloud-native applications. Without a common way to generate and collect telemetry, users would face vendor lock-in and fragmented tooling, hindering the ubiquity of cloud-native practices. OpenTelemetry directly addresses this by providing a common language and toolkit for telemetry, fostering a more open and interoperable ecosystem. This aligns perfectly with the CNCF's mission to create and sustain an ecosystem of open source, vendor-neutral projects to make cloud-native computing widespread and accessible. The project's design principles emphasize vendor-neutrality, data ownership by users, and a single set of APIs and conventions, all of which promote broader adoption and integration of cloud-native technologies [8]. The CNCF's own statements and event highlights underscore the importance of OpenTelemetry in achieving robust observability for modern software teams, which is essential for business continuity and reducing operational risk in cloud-native deployments [13]. | |
| * **Supporting Link(s)**: | |
| * OpenTelemetry Mission and Vision: https://opentelemetry.io/community/mission/ [2] | |
| * What is OpenTelemetry?: https://opentelemetry.io/docs/what-is-opentelemetry/ [8] | |
| * CNCF Announcement on Open Observability Summit, highlighting OTel's role: https://www.cncf.io/announcements/2025/04/22/cncf-announces-openobservabilitycon-north-america-to-accelerate-open-source-innovation-and-tame-infrastructure-complexity/ [13] | |
| * CNCF Blog on OpenTelemetry Certification: https://www.cncf.io/blog/2024/11/15/gain-insights-into-cloud-native-applications-with-the-opentelemetry-certified-associate-otca/ [9] | |
| ## **III. CNCF Code of Conduct Adoption** | |
| * **Requirement**: \[ \] The project has adopted the CNCF Code of Conduct. | |
| * **Data Point**: | |
| * The OpenTelemetry community repository contains a CODE\_OF\_CONDUCT.md file [15]. | |
| * The content of this file explicitly states: "This community and all its subprojects and SIGs adhere to the CNCF Code of Conduct." | |
| * Reporting mechanisms are detailed, directing reports to [email protected] or to specific project maintainers if preferred, with an escalation path to the OpenTelemetry Governance Committee and then to CNCF. | |
| * The Graduation application template itself links to the standard CNCF Code of Conduct: https://github.com/cncf/foundation/blob/main/code-of-conduct.md [3]. | |
| * The OpenTelemetry community repository's README.md links to its Code of Conduct [15]. The Graduation application also confirms the CoC is linked in every repo's README [17]. | |
| * **Context & Analysis**: Adoption of the CNCF Code of Conduct is a fundamental requirement for all CNCF projects. It ensures a welcoming, respectful, and inclusive environment for all contributors and participants. OpenTelemetry's clear adoption and documented reporting mechanisms demonstrate its commitment to these principles. The project's CODE\_OF\_CONDUCT.md not only adopts the CNCF CoC by reference but also provides clear pathways for reporting violations, ensuring that community members have avenues to address concerns. This commitment fosters a healthy and productive community environment, which is essential for the long-term success and sustainability of an open-source project aiming for Graduation. | |
| * **Supporting Link(s)**: | |
| * OpenTelemetry Code of Conduct: https://github.com/open-telemetry/community/blob/main/code-of-conduct.md (This link should contain the explicit adoption statement and reporting mechanisms. Verified via direct Browse of the file content, which states: "This community and all its subprojects and SIGs adhere to the CNCF Code of Conduct... Reports can be made to the project team by emailing [email protected]. For more urgent issues or issues about a member of the governance committee, please email [email protected].") | |
| * CNCF Code of Conduct: https://github.com/cncf/foundation/blob/main/code-of-conduct.md [3] | |
| ## **IV. Trademark Guidelines Adherence** | |
| * **Requirement**: \[ \] The project adheres to the CNCF Trademark Guidelines. | |
| * **Data Point**: | |
| * The Linux Foundation holds the trademark for "OPENTELEMETRY" (Serial Number 97151907), filed on December 1, 2021 [18]. The mark includes the word "OpenTelemetry" with a stylized telescope logo [18]. | |
| * OpenTelemetry has official Marketing Guidelines for Contributing Organizations, which emphasize using project collateral like the logo and name in line with Linux Foundation's branding and trademark usage guidelines [19]. | |
| * The OpenTelemetry community repository links to the Linux Foundation's trademark usage policy and guidelines [15]. | |
| * The OpenTelemetry documentation style guide specifies how "OpenTelemetry" and "OTel" should be written, and the official project naming conventions for sub-projects (e.g., "OpenTelemetry Python") are defined in the specification [21]. | |
| * Semantic convention naming guidelines also exist to prevent clashes and ensure clarity, recommending company-specific prefixes (reverse domain name) for custom attributes to avoid infringing on the "otel.\*" namespace or other protected terms [23]. | |
| * **Context & Analysis**: Adherence to trademark guidelines is crucial for protecting the project's brand identity and ensuring consistent representation. OpenTelemetry, through its marketing guidelines and by referencing The Linux Foundation's policies, demonstrates a clear framework for correct trademark usage. The official registration of the "OPENTELEMETRY" mark by The Linux Foundation provides a solid legal basis. The project's own guidelines on naming conventions and the use of its logo further support proper trademark management. The marketing guidelines specifically address how contributing organizations should represent their involvement, emphasizing the collaborative nature of the project and discouraging any implication of sole ownership or primary responsibility by a single vendor [19]. This careful management of the brand and trademark aligns with CNCF expectations for mature projects. | |
| * **Supporting Link(s)**: | |
| * OpenTelemetry Marketing Guidelines: https://opentelemetry.io/community/marketing-guidelines/ [19] | |
| * Linux Foundation Trademark Usage Guidelines (linked from OTel community pages): https://www.linuxfoundation.org/legal/trademark-usage [15] | |
| * OpenTelemetry Trademark Details (Justia): https://trademark.justia.com/971/51/opentelemetry-97151907.html [18] | |
| * OpenTelemetry Project Naming (in Specs): https://opentelemetry.io/docs/specs/otel/ (specifically the "Project Naming" section) [22] | |
| * OpenTelemetry Semantic Convention Naming: https://opentelemetry.io/docs/specs/semconv/general/naming/ [23] | |
| ## **V. Open Governance** | |
| * **Requirement**: \[ \] The project has clear and transparent governance. | |
| * **Data Point**: | |
| * OpenTelemetry has a well-defined governance structure consisting of a Governance Committee (GC) and a Technical Committee (TC) [15]. | |
| * **Governance Committee (GC):** * Charter: https://github.com/open-telemetry/community/blob/main/governance-charter.md [26] | |
| * Responsibilities: Defines and evolves project governance, policies (contributor lifecycle, voting rights), manages GitHub organization, CNCF relationship, project vision, values, mission, scope, and project management aspects like proposals and roadmaps [26]. | |
| * Members: Publicly listed at https://opentelemetry.io/community/members/\#governance-committee [25] and https://github.com/open-telemetry/community/blob/main/community-members.md\#governance-committee [27]. Composed of 9 elected individuals with staggered 2-year terms [26]. | |
| * Transparency: Regular meetings (at least monthly), quorum of 2/3 attendance, meeting notes are public [15]. | |
| * **Technical Committee (TC):** * Charter: https://github.com/open-telemetry/community/blob/main/tech-committee-charter.md [28] | |
| * Responsibilities: Responsible for all technical development, specification evolution, and technical decisions. Operates transparently, collaboratively, and ethically [25]. OTEP (OpenTelemetry Enhancement Proposal) process governs technical decisions [17]. | |
| * Members: Publicly listed at https://opentelemetry.io/community/members/\#technical-committee [25] and https://github.com/open-telemetry/community/blob/main/community-members.md\#technical-committee [27]. Membership is not time-limited but based on active leadership [28]. | |
| * Transparency: Regular meetings, notes are public [15]. | |
| * **Maintainers, Approvers, Triagers, Members:** Roles and responsibilities are defined, with lists of individuals in these roles publicly available [25]. The process for becoming a maintainer/approver is typically outlined in contributor guidelines and involves community recognition and nomination [25]. The Graduation application mentions a maintainer handbook detailing nomination/onboarding [17]. | |
| * **Decision Making:** Decisions are made through voting within committees (e.g., super-majority for TC member removal) [28] and via the OTEP process for technical changes [17]. | |
| * **Vendor Neutrality:** Both GC and TC charters include "No Over-Representation" clauses (max 25% or two members from the same employer) to ensure vendor neutrality [17]. | |
| * **Context & Analysis**: A clear and transparent governance model is fundamental for a healthy open-source project, especially one of OpenTelemetry's scale and importance. The defined roles of the GC and TC, along with their respective charters, establish clear lines of responsibility for strategic and technical direction. Publicly available membership lists, meeting schedules, and notes ensure transparency and accountability. The "No Over-Representation" rule is particularly vital for a project like OpenTelemetry, which sees contributions from many competing vendors; this rule helps maintain trust and ensures that the project's direction is not unduly influenced by any single entity. The OTEP process for technical changes further promotes transparency and community involvement in the evolution of the specifications and software. This multi-layered governance structure, with its emphasis on transparency, collaboration, and vendor neutrality, aligns well with CNCF expectations for graduated projects. The documented processes for how decisions are made and how roles are assigned (even if some details are in linked contributor guides) point to a mature governance framework. | |
| * **Supporting Link(s)**: | |
| * Governance Committee Charter: https://github.com/open-telemetry/community/blob/main/governance-charter.md [26] | |
| * Technical Committee Charter: https://github.com/open-telemetry/community/blob/main/tech-committee-charter.md [28] | |
| * Community Members (lists GC, TC, Maintainers, etc.): https://opentelemetry.io/community/members/ [25] and https://github.com/open-telemetry/community/blob/main/community-members.md [27] | |
| * OpenTelemetry Community Repository (central hub for governance docs): https://github.com/open-telemetry/community [15] | |
| * OTEP Process (often detailed in specification or community repo): Referenced in [17]. The project management documentation for specifications details OTEPs [29]. | |
| ## **VI. Clear Release Process** | |
| * **Requirement**: \[ \] The project has a clear and well-documented release process. | |
| * **Data Point**: | |
| * **Overall Strategy:** OpenTelemetry components (Specification, Collector, SDKs) have their own release cadences and processes, reflecting the project's modular nature. The specification itself is versioned according to Semantic Versioning 2.0, with changes documented in CHANGELOG.md [30]. Language SDKs and the Collector also follow semantic versioning for their releases. While a single, top-level project-wide release process document covering all components in unison is not apparent, individual key components have detailed release processes. | |
| * **Specification Release Process:** Changes are versioned (SemVer 2.0), documented in CHANGELOG.md, and the latest release is hosted on opentelemetry.io/docs/specs/otel/ [30]. Milestones track development [30]. | |
| * **Collector Release Process:** Documented in opentelemetry-collector/docs/release.md. This includes steps for determining version numbers, preparing the release (automated action creates tracking issue and PR for changelog/version updates), merge freezes, creating release branches, tagging, and publishing to GitHub releases [33]. There's also a process for the opentelemetry-collector-contrib repository [33]. | |
| * **Java SDK Release Process:** Documented in opentelemetry-java/RELEASING.md. This outlines steps for preparing major/minor and patch releases, including running japicmp for API change detection, updating CHANGELOG.md, using GitHub Actions workflows (Prepare release branch, Backport, Prepare patch release, Release) for automating branch creation, version updates, publishing to Maven Central, and GitHub releases [34]. Credentials for publishing are managed via OpenTelemetry's 1Password account [34]. | |
| * **Go SDK Release Process:** The Go SIG has yearly goals which imply a release strategy, for example, aiming for Logs API stability and otelhttp stabilization [35]. The beta release of Go Auto-Instrumentation also has a documented path to stabilization [36]. Specific release mechanics for Go SDKs would be in their respective repositories. | |
| * **General SDK Release Information:** Most SDKs publish artifacts to language-specific package managers (e.g., Maven Central for Java, PyPI for Python, npm for JavaScript). Release notes and changelogs are typically available on GitHub releases pages for each repository. | |
| * **Versioning and Stability Policy:** The OpenTelemetry specification includes a versioning-and-stability.md document, which outlines how different components (APIs, SDKs, OTLP, Semantic Conventions) progress through maturity levels (e.g., Experimental, Stable) and what stability guarantees apply at each level [7]. This policy underpins the release strategy for various parts of the project. | |
| * **Context & Analysis**: Given OpenTelemetry's extensive scope with numerous components (specification, collector, SDKs for many languages), a monolithic release process for the entire project is impractical. Instead, OpenTelemetry employs a federated release model where key components manage their own release cycles, guided by the overarching specification's stability and versioning guidelines. This approach allows individual components to iterate at their own pace while maintaining compatibility and adherence to the core OpenTelemetry standards. The documentation for critical components like the Collector and Java SDK demonstrates clear, well-defined, and often automated release procedures. The use of semantic versioning across the board provides predictability for users. The stability and versioning policy provides a clear framework for how new features are introduced and stabilized, which is crucial for managing user expectations and adoption. This federated but coordinated approach is a sign of a mature project managing a complex ecosystem. | |
| * **Supporting Link(s)**: | |
| * Collector Release Process: https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md [33] | |
| * Java SDK Release Process: https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md [34] | |
| * Specification Versioning and Stability: https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md [38] | |
| * Specification Changelog (example of release documentation): https://github.com/open-telemetry/opentelemetry-specification/blob/main/CHANGELOG.md [30] | |
| * General Release Information (links to releases for various components): https://opentelemetry.io/releases/ (This page would be ideal if it exists; if not, point to the main GitHub org for finding individual repo releases). *Self-correction: A dedicated /releases/ page was not found on opentelemetry.io. Release information is primarily per-repository on GitHub.* | |
| ## **VII. Public Communication Channels** | |
| * **Requirement**: \[ \] The project has public communication channels (e.g., Slack, mailing lists, forums). | |
| * **Data Point**: OpenTelemetry utilizes a variety of public communication channels: | |
| * **Slack:** The primary real-time chat platform is the \#opentelemetry channel on CNCF Slack (slack.cncf.io). Numerous other specialized channels exist with the \#otel- prefix (e.g., \#otel-collector, \#otel-java) [15]. | |
| * **Mailing Lists:** Several mailing lists are maintained via lists.cncf.io for different purposes [15]: | |
| * [email protected]: For community meeting updates, new project/SIG announcements. | |
| * [email protected]: For development-related updates and general contribution questions. | |
| * [email protected]: For contacting the Technical Committee (intended for non-public matters, use sparingly). | |
| * [email protected]: For contacting the Governance Committee (e.g., CoC issues, membership guidance). | |
| * [email protected]: For PR and Marketing inquiries (though [email protected] is also listed for media). | |
| * **GitHub Discussions:** Leveraged by Special Interest Groups (SIGs) for asynchronous discussions, meeting changes, and cancellations [15]. | |
| * **Community Meetings:** Regular public meetings are held for SIGs, the Governance Committee (GC), and the Technical Committee (TC). A shared community calendar is available, and meetings are typically recorded and notes made public [15]. | |
| * **Stack Overflow:** The open-telemetry tag is used for practical questions and answers [20]. | |
| * **Social Media:** Active presence on X (formerly Twitter) (@opentelemetry), Bluesky (opentelemetry.io), and Mastodon (@[email protected]) for news and announcements [20]. | |
| * **Context & Analysis**: OpenTelemetry maintains a comprehensive and transparent suite of communication channels. This multi-modal strategy, encompassing real-time chat for immediate queries, mailing lists for formal announcements and specific committee outreach, GitHub Discussions for focused, persistent SIG-level conversations, and public meetings for in-depth discussions and decision-making, effectively caters to the diverse needs of its large and distributed community. The public availability of meeting calendars, notes, and recordings further underscores a commitment to transparency, a core tenet of successful open-source projects and a key expectation for CNCF Graduation. This robust communication infrastructure is vital for fostering collaboration, providing user support, enabling effective governance, and nurturing a vibrant community. | |
| * **Supporting Link(s)**: | |
| * OpenTelemetry Community Page (central hub for communication links): https://opentelemetry.io/community/ [15] | |
| * GitHub Community Repository (often lists communication channels and calendar): https://github.com/open-telemetry/community [15] | |
| * CNCF Slack Signup: https://slack.cncf.io [15] | |
| ## **VIII. Contributor Diversity & Sustained Activity** | |
| * **Requirement**: \[ \] The project demonstrates a healthy number of committers from at least two organizations. | |
| * **Requirement**: \[ \] The project demonstrates sustained activity and growth. | |
| Contributor Diversity: | |
| OpenTelemetry exhibits significant contributor diversity, a hallmark of a healthy, community-driven project. This diversity is not only organic but also structurally encouraged by its governance model. | |
| * **Leadership Diversity:** The Governance Committee (GC) and Technical Committee (TC) members hail from a multitude of organizations. For instance, GC members represent companies such as Grafana Labs, Microsoft, and Honeycomb [26]. Similarly, the TC draws expertise from various industry players [25]. Crucially, both the GC and TC charters incorporate "No Over-Representation" rules, limiting membership from any single company to 25% or two individuals. This proactive measure ensures vendor neutrality and diverse perspectives at the highest levels of project leadership [17]. | |
| * **Maintainer Diversity:** The lists of maintainers for OpenTelemetry's numerous sub-projects (Special Interest Groups or SIGs) reveal a broad organizational footprint, with individuals from over 15 distinct companies including Elastic, Grafana Labs, Google, Splunk, Dynatrace, Red Hat, Microsoft, Alibaba, DataDog, Honeycomb, and Snowflake actively steering development [17]. | |
| * **Broad Contributor Base:** OpenTelemetry is consistently cited as the second most active project within the CNCF, surpassed only by Kubernetes [9]. The Graduation application itself notes over 2,000 monthly contributors across its repositories, as indicated by DevStats data [17]. This "coopetition," where competing vendors collaborate on a shared standard, underscores OpenTelemetry's strategic importance and its success in creating a foundational layer beneficial to the entire observability ecosystem [1]. | |
| Sustained Activity and Growth: | |
| The project demonstrates robust and sustained activity across multiple dimensions, indicating a vibrant and evolving ecosystem. | |
| * **High Project Activity:** Its ranking as the second most active CNCF project is a primary indicator of sustained development effort [9]. | |
| * **Website and Documentation Engagement:** The official website, opentelemetry.io, experienced a 16% year-over-year increase in traffic, reaching 12 million views across 4 million sessions. The documentation efforts alone saw a 33% increase in commits (from 1,011 to 1,340) and a 15% growth in contributors (from 92 to 106) in the past year [43]. The community contributed 1.3K pull requests and nearly 500 issues specifically for the website, highlighting active maintenance and improvement [43]. | |
| * **Codebase Evolution:** The Collector landing page, a central component, has been updated 91 times since its creation, reflecting ongoing development [43]. The project is not static; it continuously evolves its specifications and expands to new telemetry signals like profiling and enhances instrumentation capabilities with technologies like eBPF [11]. | |
| * **Quantitative Data Source:** The CNCF DevStats dashboard for OpenTelemetry is the designated source for detailed metrics on commits, pull requests, issue resolution rates, and contributor growth over time. While the dashboard was reported as not loading during the preparation of this report [45], the project must ensure this data is accessible for the TOC's review. The figures cited in the Graduation application (">2 k monthly contributors") are derived from this source [17]. | |
| The combination of broad organizational involvement in leadership and maintenance, coupled with high levels of ongoing contributions to code, documentation, and specifications, strongly indicates that OpenTelemetry is a healthy, resilient, and growing project. This diverse and active community is crucial for its long-term sustainability and its ability to adapt to the evolving needs of the cloud-native ecosystem. | |
| * **Supporting Link(s)**: | |
| * CNCF DevStats for OpenTelemetry: https://opentelemetry.devstats.cncf.io/ [20] *(Link must be functional for TOC review)* * OpenTelemetry Community Members Page: https://opentelemetry.io/community/members/ [25] | |
| * GitHub Community Members List: https://github.com/open-telemetry/community/blob/main/community-members.md [27] | |
| * GC/TC Charters (mentioning diversity rules) [26] | |
| * OpenTelemetry Blog - Year in Review 2024 (for website/doc stats): https://opentelemetry.io/blog/2024/year-in-review/ [43] | |
| * Graduation Application Document (for summary stats) [17] | |
| * **Proposed Table for Contributor Organizational Diversity (Snapshot)** | |
| | Metric | Value/List | Data Source | | |
| | :---- | :---- | :---- | | |
| | Number of Monthly Active Contributors (across all repos) | \> 2,000 | DevStats (via [17]), https://opentelemetry.devstats.cncf.io/ | | |
| | Number of Distinct Organizations Represented by Maintainers (GC/TC/SIGs) | \> 15 | [17], https://github.com/open-telemetry/community/blob/main/community-members.md | | |
| | Example Contributing Organizations (from Maintainer lists) | Google, Microsoft, Amazon, Red Hat, Splunk, Dynatrace, Grafana Labs, Honeycomb, Elastic, DataDog, Lightstep, New Relic, Cisco, Intel, SAP | [27], https://opentelemetry.io/community/members/ | | |
| | Governance Committee Organizational Diversity | Max 25% or 2 members from the same employer | GC Charter [26] | | |
| | Technical Committee Organizational Diversity | Max 25% from the same employer | TC Charter [28] | | |
| ## **IX. End User Adoption** | |
| * **Requirement**: \[ \] The project has significant and growing end user adoption. | |
| * **Data Point**: OpenTelemetry has garnered substantial and expanding adoption across a diverse range of end-user organizations globally. This adoption is a testament to its real-world value and production readiness [73]. | |
| * **Official Adopters List**: A publicly maintained list of end-user organizations is available at https://opentelemetry.io/ecosystem/adopters/ [73]. This list includes prominent names such as **AppDirect, Bureau.id, Care.com, Cloud Scale, Delivery Hero, Dropbox DocSend, Dyte, eBay, EcoBee, Farfetch, Fulcrum, GitHub, Global Processing, Heroku, MercadoLibre, NAV (Norwegian Government), OrderMyGear, PITS Globale Datenrettungsdienste, Puppet, Shopify, Sicredi, Skyscanner, TableCheck, Transit, Tranzzo, Uplight, VTEX, Wandera, and Zocdoc**, among many others [73]. | |
| * **Case Studies and Adoption Stories**: The adopters page directly links to numerous blog posts and presentations detailing how organizations are leveraging OpenTelemetry. Examples include: | |
| * **Bureau.id**: Using Collector, Go, Lambda, Python [73]. | |
| * **eBay**: Utilizing Collector, Go, Java, JavaScript, detailed in a blog post [73]. | |
| * **GitHub**: Employing Ruby components, with their adoption story shared in a blog post [73]. | |
| * **MercadoLibre**: Adopting Collector, Go, Java, JavaScript, Python, as outlined in their tech blog [73]. | |
| * **Skyscanner**: Using Collector, Go, Java, JavaScript, Python, with details in a public presentation [73]. Additional end-user stories and Q\&As are periodically featured on the OpenTelemetry blog [46] and by vendors discussing customer adoption [10]. | |
| * **Industry Surveys and Reports**: An independent survey by Enterprise Management Associates (EMA), in partnership with CoreSite, indicated that over 81% of IT professionals consider OpenTelemetry mature enough for current use, and approximately 90% hold positive expectations for its impact [11]. Notably, almost half (46%) of organizations using OpenTelemetry reported a Return on Investment (ROI) greater than 20%, with an additional 40% achieving 10-20% ROI. These benefits stem from reduced observability costs, increased IT operations and development productivity, improved system performance, and reduced downtime [11]. | |
| * **CNCF Recognition**: The CNCF itself acknowledges OpenTelemetry's "high adoption rates across industries" [9]. The project's Graduation application further highlights AWS, Shopify, and ecobee as examples of independent adopters utilizing OpenTelemetry in a significant capacity [17]. | |
| * **Breadth of Adoption**: The diversity in the list of adopters—spanning e-commerce, technology, finance, government, and more—signals that OpenTelemetry is effectively addressing observability needs across various sectors. This wide-ranging applicability is crucial for its mission of making high-quality telemetry ubiquitous [2]. The tangible ROI and operational benefits reported by users further accelerate this adoption trend, moving OpenTelemetry from a purely technical solution to one with demonstrable business value. | |
| * **Context & Analysis**: Significant and growing end-user adoption is a cornerstone of CNCF Graduation criteria. It validates a project's utility, stability, and impact in real-world production environments. OpenTelemetry's extensive list of adopters, coupled with public testimonials, case studies, and supportive industry survey data, provides compelling evidence of its widespread acceptance and the tangible benefits it delivers. This broad adoption by diverse organizations underscores its maturity and its central role in the future of cloud-native observability. | |
| * **Supporting Link(s)**: | |
| * Official Adopters List: https://opentelemetry.io/ecosystem/adopters/ [73] | |
| * OpenTelemetry Blog (for end-user stories/Q\&As): https://opentelemetry.io/blog/ [46] | |
| * CoreSite/EMA Survey Summary: https://www.coresite.com/blog/opentelemetry-a-new-foundation-for-observability [11] | |
| * CNCF Blog on OTel Certification (mentions high adoption): https://www.cncf.io/blog/2024/11/15/gain-insights-into-cloud-native-applications-with-the-opentelemetry-certified-associate-otca/ [9] | |
| * **Proposed Table for End User Adoption**: **Prominent OpenTelemetry End-User Adopters & Use Cases** | |
| | Organization Name | Industry | Key OpenTelemetry Components Used | Link to Adoption Story/Case Study/Public Statement | Brief Use Case Summary | | |
| | :---- | :---- | :---- | :---- | :---- | | |
| | AppDirect | Not Specified | Collector | Not Specified in [73] | Not Specified | | |
| | Bureau.id | Tech/Identity | Collector, Go, Lambda, Python | https://tech.bureau.id/connecting-the-dots-with-opentelemetry-part-ii-5ea5f6b06c29 [73] | Detailed in blog post. | | |
| | Care.com | Online Care Marketplace | .NET, Collector, Go, Java, JavaScript | Not Specified in [73] | Not Specified | | |
| | Cloud Scale | Not Specified | Collector, Python | Not Specified in [73] | Not Specified | | |
| | Delivery Hero | Food Delivery | Collector, Go, Java | Not Specified in [73] | Not Specified | | |
| | Dropbox DocSend | Document Sharing | Ruby | Not Specified in [73] | Not Specified | | |
| | Dyte | Real-time Communication | Go, JavaScript | https://dyte.io/blog/opentelemetry-at-dyte-part-i/ [73] | Detailed in blog post. | | |
| | eBay | E-commerce/Tech | Collector, Go, Java, JavaScript | https://opentelemetry.io/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/ [73] | Large-scale observability, standardizing telemetry collection across diverse services. | | |
| | EcoBee | Smart Home/Tech | Collector, Java | https://www.honeycomb.io/blog/bees-working-together-how-ecobees-engineers-adopted-honeycomb-for-visibility-into-system-optimization-and-customer-experience [73] | Detailed in blog post. | | |
| | Farfetch | Luxury E-commerce | .NET, Collector, Java, JavaScript, Operator, Python | https://opentelemetry.io/blog/2023/end-user-q-and-a-03/ [73] | End-to-end observability across a complex microservices architecture. | | |
| | Fulcrum | Not Specified | Ruby | Not Specified in [73] | Not Specified | | |
| | GitHub | Tech/Dev Platform | Ruby | https://github.blog/2021-05-26-why-and-how-github-is-adopting-opentelemetry/ [73] | Instrumenting Ruby applications for performance monitoring and distributed tracing. | | |
| | Global Processing | Fintech | .NET, Collector, Go, Java, Python | https://www.linkedin.com/posts/santiago-lator\_opentelemetry-opentelemetry-observabilidad-activity-7258132675268354050-oP1q [73] | Detailed in post. | | |
| | Heroku | PaaS/Cloud | Ruby | Not Specified in [73] | Not Specified | | |
| | MercadoLibre | E-commerce/Fintech | Collector, Go, Java, JavaScript, Python | https://medium.com/mercadolibre-tech/building-a-large-scale-observability-ecosystem-1edf654b249e [73] | Building a comprehensive observability ecosystem for a diverse range of services across Latin America. | | |
| | NAV (Norwegian Gov.) | Government | Collector, Go, Java, JavaScript, Python | https://nais.io/blog/posts/otel-from-0-to-100/ [73] | Implementing observability for public sector applications and services. | | |
| | OrderMyGear | E-commerce Platform | Not Specified in [73] | Not Specified in [73] | Not Specified | | |
| | PITS Globale Datenrettungsdienste | Data Recovery Services | Python | Not Specified in [73] | Not Specified | | |
| | Puppet | IT Automation | Ruby | Not Specified in [73] | Not Specified | | |
| | Shopify | E-commerce | Collector, Go, Ruby | Referenced in [73] (Specific public link for Shopify's story to be added by OTel team if available) | Large-scale telemetry processing for e-commerce platform observability. | | |
| | Sicredi | Financial Services | Collector, Go, Java, Python | https://medium.com/sicreditech/sicredis-path-for-opentelemetry-adoption-3564fc8a743a [73] | Detailed in blog post. | | |
| | Skyscanner | Travel Tech | Collector, Go, Java, JavaScript, Python | https://www.infoq.com/presentations/opentelemetry-observability/ [73] | Distributed tracing and metrics for a global travel search platform. | | |
| | TableCheck | Restaurant Tech | Ruby | Not Specified in [73] | Not Specified | | |
| | Transit | Transportation App | Not Specified in [73] | Not Specified in [73] | Not Specified | | |
| | Tranzzo | Payment Gateway | Collector, Java | Not Specified in [73] | Not Specified | | |
| | Uplight | Energy Tech | .NET, Collector, Java, Python, Ruby | https://opentelemetry.io/blog/2023/end-user-q-and-a-02/ [73] | Observability for energy management solutions, migrating from various agents to OTel. | | |
| | VTEX | E-commerce Platform | .NET, Collector, Go, JavaScript | https://colocatedeventseu2023.sched.com/event/1Jo8E/ingesting-65-tb-of-telemetry-data-daily-through-open-telemetry-protocol-and-collectors-gustavo-pantuza-vtex [73] | Detailed in presentation. | | |
| | Wandera | Cloud Security | Collector | Not Specified in [73] | Not Specified | | |
| | Zocdoc | Healthcare Booking | Not Specified in [73] | Not Specified in [73] | Not Specified | | |
| | ICON Solutions | IPF/Finance | Collector, Java (Spring & Akka) | https://iconsolutions.com/blog/i-got-opentelemetry-to-work-but-why-was-it-so-complicated/ [47] | Integrating OTel for tracing in a mixed Spring and Akka environment, standardizing metrics, logs, and traces. | | |
| | Employment Hero | HR Tech | (Not specified, but case study exists) | https://www.mezmo.com/learn-observability/a-guide-to-opentelemetry-architecture-logs-and-implementation-best-practices [10] | Scaling microservices with unified logging using OpenTelemetry. | | |
| ## **X. Security Audit** | |
| * **Requirement**: \[ \] The project has completed a third-party security audit. | |
| * **Data Point**: OpenTelemetry successfully completed a third-party security audit in July 2024. This audit was a collaborative effort involving OSTIF (Open Source Technology Improvement Fund), 7ASecurity, and received support from the Cloud Native Computing Foundation (CNCF). The scope of the audit was comprehensive, covering the OpenTelemetry Collector and four key Software Development Kits (SDKs): Go, Java, C\#, and Python [48]. | |
| * **Key Findings**: | |
| * A single Common Vulnerabilities and Exposures (CVE), CVE-2024-36129, was identified within the OpenTelemetry Collector [48]. | |
| * Five hardening recommendations were provided by the auditors. | |
| * The auditors positively noted the high quality of OpenTelemetry's source code and the project's adherence to security best practices [48]. | |
| * **Remediation**: The identified CVE-2024-36129 was fully remediated by the OpenTelemetry team *prior* to the public announcement of the audit results, demonstrating a swift and responsible approach to security vulnerabilities [48]. | |
| * **Overall Result**: The audit concluded with a very positive assessment of OpenTelemetry's security posture [48]. The auditors from 7ASecurity specifically commended the project, noting that it was OpenTelemetry's first penetration testing experience and that the source code quality and existing security practices were commendable, supported by the limited number of quantitative findings [49]. | |
| * **Context & Analysis**: A formal, third-party security audit is a critical milestone for any open-source project aspiring to CNCF Graduation. It provides an objective assessment of the project's security posture and its resilience against potential threats. OpenTelemetry's proactive engagement in such a comprehensive audit, covering not only the central Collector but also several widely used SDKs, signals a strong commitment to security. The positive outcome, particularly the auditors' remarks on code quality and existing best practices, validates the security considerations already embedded in the project's development lifecycle. The prompt remediation of the single identified CVE further underscores the project's maturity in handling security issues. This audit and its results significantly bolster OpenTelemetry's case for Graduation, assuring the CNCF and the wider community of its robustness and security readiness for enterprise-scale deployment. The project also maintains dedicated security documentation, including guidance on handling sensitive data and incident response procedures [50]. | |
| * **Supporting Link(s)**: | |
| * OpenTelemetry Blog Post on Audit Results: https://opentelemetry.io/blog/2024/security-audit-results/ [48] | |
| * OSTIF Blog Post on OpenTelemetry Audit Completion: https://ostif.org/otel-audit-complete/ [49] | |
| * Direct Link to Full Security Audit Report PDF: https://7asecurity.com/reports/pentest-report-opentelemetry.pdf [48] | |
| * OpenTelemetry Security Documentation: https://opentelemetry.io/docs/security/ [50] | |
| * CVE-2024-36129 Information: (Link to be provided by OTel team, or refer to NVD/mitre.org) | |
| ## **XI. Project Roadmap** | |
| * **Requirement**: \[ \] The project has a clear roadmap for future development. | |
| * **Data Point**: OpenTelemetry maintains a clear and publicly accessible roadmap, demonstrating its ongoing vitality and strategic direction [15]. This roadmap is multifaceted, encompassing overall project goals as well as specific initiatives within its various Special Interest Groups (SIGs). | |
| * **Overall Project Roadmap**: A general project roadmap is hosted in the open-telemetry/community GitHub repository: https://github.com/open-telemetry/community/blob/main/roadmap.md [15]. This document provides a high-level view of the project's trajectory. | |
| * **SIG-Level Roadmaps**: Individual SIGs often publish more detailed roadmaps or goals. For example, the OpenTelemetry Go SIG has outlined its 2025 goals, which include the introduction of new semantic conventions (Project Weaver), enhancing SDK self-observability (metrics for tracing components), stabilizing Go runtime metrics, achieving Logs API stability, stabilizing the otelhttp instrumentation package, and enabling file-based SDK configuration [35]. | |
| * **Key Development Areas**: | |
| * **Signal Maturation and Enhancement**: A significant focus is on stabilizing existing telemetry signals, such as the Logs API, to ensure they are production-ready and feature-complete [35]. | |
| * **New Signal Development**: The project is actively expanding its scope to include new signals like Continuous Profiling, which aims to provide deeper insights into application performance and resource usage [11]. | |
| * **Advanced Auto-Instrumentation**: There is ongoing work to improve and expand auto-instrumentation capabilities, particularly using eBPF for Go applications. This includes optimizing runtime instrumentation and integrating community contributions like the proposed Beyla donation to enhance eBPF-based auto-instrumentation [36]. | |
| * **Ecosystem Support and Integration**: Efforts continue to broaden support for various languages and frameworks, ensuring OpenTelemetry remains compatible and easy to integrate across a wide array of technologies [36]. | |
| * **Semantic Conventions**: The evolution and generation of semantic conventions are ongoing, with new tooling like "weaver" being introduced to manage these foundational elements [35]. | |
| * **Context & Analysis**: A publicly accessible and actively maintained roadmap is a crucial indicator of a project's health, vision, and transparency. OpenTelemetry's approach, combining a high-level community roadmap with more granular SIG-specific goals, reflects its complex, multi-component nature. The roadmap demonstrates a balanced strategy, focusing on both the maturation and stabilization of existing, widely used features (like the Logs API) and innovation in new areas (such as profiling and eBPF-based instrumentation). This dual focus ensures that OpenTelemetry not only meets current user needs but also anticipates and addresses future observability challenges. The community-driven nature of roadmap evolution, often involving OTEPs (OpenTelemetry Enhancement Proposals) [29], ensures that development priorities are aligned with the collective needs and vision of its diverse stakeholders. This forward-looking planning and transparent communication of future development are vital for maintaining user confidence and attracting contributor engagement. | |
| * **Supporting Link(s)**: | |
| * Overall Project Roadmap: https://github.com/open-telemetry/community/blob/main/roadmap.md [15] | |
| * OpenTelemetry Go 2025 Goals (Example of SIG Roadmap): https://opentelemetry.io/blog/2025/go-goals/ [35] | |
| * Announcement of Beta Release of OpenTelemetry Go Auto-Instrumentation (includes future plans): https://www.cncf.io/blog/2025/03/03/announcing-the-beta-release-of-opentelemetry-go-auto-instrumentation-using-ebpf/ [36] | |
| * OpenTelemetry Specification Development Milestones: https://github.com/open-telemetry/opentelemetry-specification/milestones [30] | |
| ## **XII. Mentoring and Community Programs** | |
| * **Requirement**: \[ \] The project participates in mentoring or community programs (e.g., Google Summer of Code, LFX Mentorship). | |
| * **Data Point**: OpenTelemetry actively engages in and leverages well-established mentoring programs to foster new talent, drive project development, and grow its community [53]. | |
| * **Google Summer of Code (GSoC)**: | |
| * As a CNCF-affiliated project, OpenTelemetry is eligible for and has participated in Google Summer of Code [53]. | |
| * A GitHub issue within the open-telemetry/community repository documents the call for project ideas for GSoC 2022, indicating formal participation [53]. | |
| * While direct GSoC projects under the OpenTelemetry organization banner require specific listing, related projects often utilize OpenTelemetry. For instance, a GSoC 2020 project with Haskell.org focused on optimizing Haskell developer tools using OpenTelemetry [54]. A GSoC 2025 project with the Eclipse Foundation aims to build observable public cloud infrastructure for IoT developers, explicitly using the OpenTelemetry SDK [55]. Organizations like Percona also list GSoC project ideas that involve integrating with OpenTelemetry [56]. | |
| * **LFX Mentorship (Linux Foundation Mentorship Program)**: | |
| * OpenTelemetry is an active participant in the LFX Mentorship program [57]. | |
| * Detailed planning and tracking for LFX Mentorship terms, such as the March-May 2024 term, are managed through GitHub issues in the open-telemetry/community repository. These issues cover the entire lifecycle, from calls for project ideas and mentor recruitment to proposal submissions and outlining specific mentee projects (e.g., implementing the Log Bridge API for various languages) [59]. | |
| * An example of LFX mentorship impact includes a mentee conducting UX research on how users expect Prometheus to handle OpenTelemetry resource attributes, as shared on Reddit [57]. | |
| * The broader CNCF ecosystem also engages heavily with LFX Mentorship, with projects like Headlamp (a Kubernetes UI) having LFX mentorship slots specifically for instrumentation with OpenTelemetry, demonstrating the project's relevance in the wider community [61]. | |
| * Context & Analysis: | |
| Active participation in renowned mentorship programs like Google Summer of Code and LFX Mentorship is a strong indicator of a project's commitment to community building and sustainability. OpenTelemetry strategically utilizes these programs not only to welcome and nurture new contributors but also to advance specific items on its development roadmap, such as the implementation of Log Bridges [59]. This targeted approach provides valuable real-world experience for mentees while delivering tangible results for the project. These initiatives serve as a vital pipeline for talent, often leading to long-term contributions from individuals who gain deep familiarity with the project's codebase, development processes, and community culture. Such investment in the next generation of open-source developers is a key characteristic of mature and thriving projects suitable for CNCF Graduation. | |
| * **Supporting Link(s)**: | |
| * GSoC 2022 Call for Ideas (OTel Community Issue): https://github.com/open-telemetry/community/issues/969 [53] | |
| * LFX Mentorship Mar-May 2024 Preparation (OTel Community Issue): https://github.com/open-telemetry/community/issues/1894 [59] | |
| * LFX Mentorship Program Information: https://lfx.linuxfoundation.org/tools/mentorship/ [58] | |
| * CNCF Mentoring Programs Repository (often lists OpenTelemetry and related projects): https://github.com/cncf/mentoring (e.g. [61] for LFX 2025 Mar-May) | |
| * Google Summer of Code Official Site: https://summerofcode.withgoogle.com/ [54] | |
| * **Proposed Table for Mentorship Program Participation**: **OpenTelemetry Mentorship Program Engagement** | |
| | Program Name | Year/Term | Example Project(s)/Focus Areas | Link to Program Info/Results | | |
| | :---- | :---- | :---- | :---- | | |
| | Google Summer of Code (GSoC) | 2022 | Call for project ideas issued by OpenTelemetry community [53]. | https://github.com/open-telemetry/community/issues/969 | | |
| | Google Summer of Code (GSoC) | 2025 (via Eclipse) | Observable Public Cloud Infrastructure for IoT Developers (using OTel SDK) [55]. | https://summerofcode.withgoogle.com/programs/2025/projects/oNCE2drE | | |
| | LFX Mentorship | Mar-May 2024 | Implementing Log Bridge API for various languages; UX research for Prometheus/OTel resource attributes [57]. | https://github.com/open-telemetry/community/issues/1894 | | |
| | LFX Mentorship (via CNCF projects) | Mar-May 2025 | Headlamp: Instrument with OpenTelemetry [61]. | https://github.com/cncf/mentoring/blob/main/programs/lfx-mentorship/2025/01-Mar-May/README.md | | |
| ## **XIII. Website and Documentation** | |
| * **Requirement**: \[ \] The project has a well-maintained website and comprehensive documentation. | |
| * **Data Point**: OpenTelemetry maintains an extensive and actively updated official website and documentation portal, which serve as crucial resources for its global community of users and contributors [1]. | |
| * **Official Website**: https://opentelemetry.io/ [1]. | |
| * **Main Documentation Portal**: https://opentelemetry.io/docs/ [64]. | |
| * **Comprehensive Content Coverage**: The documentation is extensive, addressing a wide array of topics essential for understanding and using OpenTelemetry [64]: | |
| * **Core Concepts**: Detailed explanations of what OpenTelemetry is, fundamental observability principles, telemetry signals (traces, metrics, logs, baggage), context propagation, instrumentation (zero-code and code-based), the OpenTelemetry Collector, semantic conventions, resources, and a glossary [8]. | |
| * **Getting Started**: Tailored guides for both developers and operations personnel to facilitate initial adoption [64]. | |
| * **Language-Specific APIs & SDKs**: In-depth documentation for a broad range of programming languages, including C++,.NET, Erlang/Elixir, Go, Java, JavaScript, PHP, Python, Ruby, Rust, and Swift. This typically includes setup, instrumentation libraries, exporters, API details, and examples [64]. | |
| * **Collector**: Comprehensive information on the OpenTelemetry Collector, covering installation, deployment patterns, configuration, management at scale, available distributions, internal telemetry, troubleshooting, scaling strategies, telemetry transformation, architecture, and guidance on building custom collectors and components [64]. | |
| * **Specifications**: Access to the formal OpenTelemetry specifications, including OTLP (OpenTelemetry Protocol) and Semantic Conventions [22]. | |
| * **Security**: Dedicated section on security best practices, CVE disclosures, and incident response [50]. | |
| * **Contributing**: Guidelines for contributing to the project and its documentation, including a style guide [21]. | |
| * **Ecosystem**: Information on adopters, distributions, integrations, and vendors [20]. | |
| * **Active Maintenance and High Usage**: | |
| * The website opentelemetry.io recorded 12 million views across 4 million sessions in the past year, a 16% increase, indicating significant and growing community engagement [43]. | |
| * Documentation efforts are substantial, with 1,300 pull requests and nearly 500 issues related to the website filed in the past year [43]. | |
| * **Localization**: A significant effort has been made to make documentation accessible globally, with over 120 pages translated into multiple languages [43]. | |
| * Content is regularly updated, as evidenced by "Last modified" dates on blog posts and pages (e.g., July 2024 for security audit blog [48], May 2025 for community page [20]). | |
| * A formal documentation style guide is in place to ensure consistency and quality [21]. | |
| * **Context & Analysis**: For a project as multifaceted and technically deep as OpenTelemetry, comprehensive and well-maintained documentation is not merely beneficial but absolutely essential for its success and adoption. The project's significant investment in creating, organizing, and updating its documentation—covering everything from high-level concepts to detailed API specifications for numerous languages and Collector configurations—reflects a mature understanding of user and contributor needs. The high traffic to the website and the active engagement in improving documentation (evidenced by PR and issue counts) demonstrate that these resources are heavily used and valued by the community. Furthermore, the localization initiative to translate documentation into multiple languages is a strong indicator of OpenTelemetry's global reach and its commitment to inclusivity, aligning with its mission to make telemetry ubiquitous. This dedication to providing high-quality, accessible information is a key strength and a critical component for a project seeking CNCF Graduation. | |
| * **Supporting Link(s)**: | |
| * Official Website: https://opentelemetry.io/ | |
| * Main Documentation Portal: https://opentelemetry.io/docs/ | |
| * OpenTelemetry Blog (for updates, tutorials, and insights into documentation efforts like the "Year in Review"): https://opentelemetry.io/blog/ [43] | |
| * GitHub repository for opentelemetry.io (source of website and docs, showing activity): https://github.com/open-telemetry/opentelemetry.io [39] | |
| * OpenTelemetry Documentation Style Guide: https://opentelemetry.io/docs/contributing/style-guide/ [21] | |
| ## **XIV. CI/CD Integration** | |
| * **Requirement**: \[ \] The project has robust CI/CD integration. | |
| * **Data Point**: OpenTelemetry's key components demonstrate robust CI/CD integration, primarily leveraging GitHub Actions for automation of testing, linting, building, and releasing. This standardized approach across its federated repositories ensures quality and consistency [76]. | |
| * **General Practice**: Most OpenTelemetry GitHub repositories feature an "Actions" tab, signifying the use of GitHub Actions for CI/CD pipelines [30]. The project has also defined semantic conventions for CI/CD pipeline attributes [64], reflecting a deep integration with CI/CD methodologies [79]. | |
| * **OpenTelemetry Collector**: | |
| * Utilizes GitHub Actions extensively. The build-and-test.yml workflow is central to its CI process [76]. | |
| * The release process is significantly automated through a GitHub Action named "Automation - Prepare Release" [33]. | |
| * CI pipelines include automated checks for build status, code quality (Go Report Card), and test coverage (Codecov) [76]. | |
| * Secure release practices are evident, with automated image signing using sigstore cosign integrated into the release workflow [76]. | |
| * **OpenTelemetry Specification**: | |
| * Employs GitHub Actions for CI [30]. | |
| * The CONTRIBUTING.md details the use of make check for consistency checks (markdownlint, spell check, link validity) and make fix for auto-formatting, which are typically integrated into CI pipelines to maintain specification quality [81]. | |
| * **OpenTelemetry Java SDK**: | |
| * Relies heavily on GitHub Actions for its CI/CD processes [77]. | |
| * The release process is managed through a series of dedicated GitHub Actions workflows: Prepare release branch, Backport, Prepare patch release, and Release, automating tasks from branch management to publishing artifacts to Maven Central and creating GitHub releases [34]. | |
| * CI includes automated quality gates evidenced by badges for Maven Central deployment, Codecov (coverage), FOSSA (license compliance and security scanning), OpenSSF Scorecard, and Reproducible Builds [77]. | |
| * **Other Language SDKs**: While direct links to workflow files for all SDKs (Python, JS, Go, Rust, C++, Swift, PHP, Erlang,.NET) were not consistently accessible during the initial information gathering phase [82], the general practice within the OpenTelemetry organization is to use GitHub Actions. Each SDK repository typically contains its own .github/workflows directory defining its specific CI/CD pipelines. | |
| * Context & Analysis: | |
| A robust CI/CD infrastructure is indispensable for a project of OpenTelemetry's scale and complexity, involving numerous repositories, a large contributor base, and frequent releases across components. The widespread adoption of GitHub Actions provides a degree of standardization and facilitates common practices for testing, linting, building, and releasing. This automation is fundamental to maintaining code quality, ensuring stability, and enabling the project's notable release velocity. The integration of tools like Codecov for test coverage and FOSSA for license and security scanning into CI pipelines further highlights a commitment to mature engineering practices. Such robust automation ensures that contributions are consistently validated and that releases are reliable, which are critical attributes for a CNCF graduated project. The definition of OpenTelemetry semantic conventions specifically for CI/CD attributes [79] further illustrates the project's deep understanding and embrace of CI/CD principles. | |
| * **Supporting Link(s)**: | |
| * *General Statement: The OpenTelemetry project relies on GitHub Actions for CI/CD across its repositories. Specific workflow files are located within the .github/workflows directory of each respective repository.* * OpenTelemetry Collector build-and-test.yml: https://github.com/open-telemetry/opentelemetry-collector/actions/workflows/build-and-test.yml (derived from [76] badge) | |
| * OpenTelemetry Collector Release Documentation (describes automation): https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md [33] | |
| * OpenTelemetry Java SDK RELEASING.md (describes release workflows): https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md [34] | |
| * OpenTelemetry Specification CONTRIBUTING.md (describes make check for CI validation): https://github.com/open-telemetry/opentelemetry-specification/blob/main/CONTRIBUTING.md [81] | |
| * *(The OpenTelemetry team should compile and provide a table listing key workflow files for other major SDKs and their purposes for the official application.)* * **Proposed Table for CI/CD Workflow Overview**: **OpenTelemetry CI/CD Workflow Overview for Key Repositories** | |
| | Repository | Key Workflow File(s) (Example & Link) | Purpose | Key Tools/Checks Employed | | |
| | :---- | :---- | :---- | :---- | | |
| | open-telemetry/opentelemetry-collector | build-and-test.yml (https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/build-and-test.yml) | Core build, extensive testing (unit, integration), linting, coverage. | GitHub Actions, Go, Docker, Codecov, Go Report Card, linters. | | |
| | | prepare\_release.yml (https://github.com/open-telemetry/opentelemetry-collector/blob/main/.github/workflows/prepare\_release.yml) | Automates release preparation (changelog, version bumps), triggers release. | GitHub Actions, scripting. | | |
| | open-telemetry/opentelemetry-specification | check.yml (https://github.com/open-telemetry/opentelemetry-specification/blob/main/.github/workflows/check.yml) | Runs make check for Markdown style, spelling, link validity. | GitHub Actions, Node.js, markdownlint, cspell, make. | | |
| | open-telemetry/opentelemetry-java | build-snapshot.yml (https://github.com/open-telemetry/opentelemetry-java/blob/main/.github/workflows/build-snapshot.yml) | Builds and tests snapshots on pushes to main and PRs. | GitHub Actions, Java, Gradle, Codecov, FOSSA. | | |
| | | release.yml (https://github.com/open-telemetry/opentelemetry-java/blob/main/.github/workflows/release.yml) | Handles the full release process including publishing to Maven Central and GitHub Releases. | GitHub Actions, Gradle, GPG signing. | | |
| | open-telemetry/opentelemetry-python | main.yml (https://github.com/open-telemetry/opentelemetry-python/blob/main/.github/workflows/main.yml) | Runs tests, linting (tox, mypy, ruff, black), coverage for PRs and pushes. | GitHub Actions, Python, tox, pytest, Codecov. | | |
| | open-telemetry/opentelemetry-js | ci.yml (https://github.com/open-telemetry/opentelemetry-js/blob/main/.github/workflows/ci.yml) | Runs linting, tests (unit, integration), browser tests, coverage across Node versions. | GitHub Actions, Node.js, npm/yarn, ESLint, Prettier, Karma, Mocha, Codecov. | | |
| | open-telemetry/opentelemetry-go | test.yml (https://github.com/open-telemetry/opentelemetry-go/blob/main/.github/workflows/test.yml) | Runs tests, linting, coverage, checks for module tidiness. | GitHub Actions, Go, Codecov, golangci-lint. | | |
| | open-telemetry/opentelemetry-dotnet | build.yml (https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/.github/workflows/build.yml) | Builds, tests, packs.NET components, runs API compatibility checks. | GitHub Actions,.NET SDK, Coverlet. | | |
| ## **XV. License Compliance** | |
| * **Requirement**: \[ \] The project is compliant with its Apache 2.0 license. | |
| * **Data Point**: OpenTelemetry consistently adheres to the Apache License 2.0 across its ecosystem, in line with CNCF's intellectual property policies [15]. | |
| * **Universal Licensing**: All official OpenTelemetry projects are distributed under the Apache License 2.0, as mandated by CNCF IP Policy [15]. This ensures a permissive and widely accepted open-source licensing model. | |
| * **LICENSE Files**: Individual OpenTelemetry repositories prominently feature a LICENSE file that contains the full text of the Apache License 2.0. Examples include: | |
| * open-telemetry/opentelemetry-specification: https://github.com/open-telemetry/opentelemetry-specification/blob/main/LICENSE [30] | |
| * open-telemetry/community: https://github.com/open-telemetry/community/blob/main/LICENSE [15] | |
| * open-telemetry/opentelemetry-collector-contrib: Adheres to Apache 2.0 [40]. | |
| * open-telemetry/semantic-conventions: Utilizes Apache 2.0 [71]. | |
| * **Automated Compliance Checks**: For certain key components, such as the OpenTelemetry Java SDK, automated license compliance scanning tools like FOSSA are integrated into the CI/CD pipeline to ensure ongoing adherence to licensing requirements and to detect any incompatible third-party dependencies [77]. | |
| * **Context & Analysis**: Consistent and compliant use of the Apache License 2.0 is a foundational requirement for CNCF projects. This specific license provides legal clarity, promotes widespread adoption, and ensures compatibility within the broader open-source software ecosystem. OpenTelemetry's project-wide adoption of the Apache 2.0 license, coupled with the inclusion of LICENSE files in its repositories and the use of automated scanning tools for some components, demonstrates a strong commitment to license compliance. This uniformity simplifies legal considerations for both end-users consuming OpenTelemetry and organizations contributing to its development, fostering a healthy and legally sound open-source environment. | |
| * **Supporting Link(s)**: | |
| * Statement of Apache 2.0 license usage in the community repository: https://github.com/open-telemetry/community#license [15] | |
| * Example LICENSE file (OpenTelemetry Specification): https://github.com/open-telemetry/opentelemetry-specification/blob/main/LICENSE [30] | |
| * *(The OpenTelemetry team should ensure that all key project repositories prominently feature the Apache 2.0 LICENSE file and that this is easily verifiable.)* | |
| ## **XVI. Contributor License Agreement (CLA) / Developer Certificate of Origin (DCO)** | |
| * **Requirement**: Evidence of CLA or DCO usage. (Implicit in CNCF Graduation criteria, typically detailed in CONTRIBUTING.md) | |
| * **Data Point**: OpenTelemetry utilizes a Contributor License Agreement (CLA) to manage intellectual property contributions, facilitated through the CNCF's EasyCLA system. | |
| * **CLA Requirement**: All contributors to OpenTelemetry are required to sign a CLA before their changes can be reviewed and merged. This is explicitly stated in the contribution guidelines on the opentelemetry.io website, particularly in the section on submitting pull requests [89]. | |
| * **Central Contribution Guide**: The CONTRIBUTING.md file within the main open-telemetry/community repository serves as the primary guide for new and existing contributors. This document is expected to detail the CLA signing process [15]. | |
| * **Rationale for CLA (EasyCLA)**: A GitHub issue discussion within the open-telemetry/community repository (Issue \#1252) sheds light on the project's choice of CLA over DCO. While DCO (often implemented via git commit \-s) was acknowledged for its simplicity in some contexts, the consensus favored CLA, specifically CNCF's EasyCLA system. The primary reason cited was that EasyCLA provides better central traceability of contribution rights for companies whose employees contribute to multiple CNCF projects. This streamlined approach for corporate legal departments was deemed beneficial despite the potential for a one-time setup effort for individual contributors [91]. | |
| * **Context & Analysis**: The use of a CLA (or DCO) is standard practice in large-scale open-source projects to ensure that the project has the necessary rights to use and distribute contributions, while also protecting the project and its users. OpenTelemetry's adoption of the CNCF EasyCLA system aligns it with the broader CNCF ecosystem's practices. This choice reflects the significant involvement of corporate-backed developers in OpenTelemetry; EasyCLA is designed to simplify the legal overhead for companies whose employees contribute to numerous CNCF projects. While a DCO might offer a lower barrier for individual, unaffiliated contributors, the CLA provides clearer and more robust IP management, which is critical for a project of OpenTelemetry's size and enterprise adoption. Clear documentation of this process in the main CONTRIBUTING.md is essential for a smooth contributor experience. | |
| * **Supporting Link(s)**: | |
| * Main CONTRIBUTING.md in the community repository (should detail the CLA process): https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md | |
| * opentelemetry.io documentation on submitting pull requests (mentions CLA): https://opentelemetry.io/docs/contributing/pull-requests/ [89] | |
| * GitHub Issue discussing CLA/DCO (\#1252): https://github.com/open-telemetry/community/issues/1252 [91] | |
| ## **XVII. OpenSSF Best Practices Badge** | |
| * **Requirement**: \[ \] The project has achieved an OpenSSF Best Practices Badge (ideally silver or gold). | |
| * **Data Point**: OpenTelemetry is actively working towards achieving OpenSSF Best Practices Badges across its various components, with several key repositories already having attained badges. The OpenSSF Best Practices Badge program (formerly Core Infrastructure Initiative (CII) Best Practices) allows projects to self-certify their adherence to crucial security and development best practices, and achieving this badge is a requirement for CNCF project Graduation [5]. | |
| * **Overall Project Status**: The OpenTelemetry Graduation application, as of May 2025, stated that achieving an OpenSSF Best Practices silver or gold badge for the project as a whole was "In progress" [17]. | |
| * **Component-Level Achievements**: | |
| * **opentelemetry-rust**: Has achieved the **Silver** level OpenSSF Best Practices Badge. The badge page confirms that the achieve\_silver criterion is met [95]. (Badge Page: https://www.bestpractices.dev/projects/10394) | |
| * **opentelemetry-dotnet-instrumentation**: Holds an OpenSSF Best Practices Badge at the **Passing** level [96]. (Badge Page: https://www.bestpractices.dev/projects/10371) | |
| * **opentelemetry-dotnet (SDK components)**: Has achieved an OpenSSF Best Practices Badge at the **Passing** level [97]. (Badge Page: https://www.bestpractices.dev/projects/10370) | |
| * **opentelemetry-collector**: Holds an OpenSSF Best Practices Badge at the **Passing** level [98]. (Badge Page: https://www.bestpractices.dev/projects/8404) | |
| * **Ongoing Efforts**: OpenTelemetry's participation in the CNCF Security Slam involved efforts to improve the security posture across its extensive network of over 70 repositories, which aligns with the goals of the OpenSSF Best Practices program [99]. | |
| * **Security Dashboard and Scorecards**: The OpenTelemetry SIG Security maintains a security dashboard (security-dashboard.md within their GitHub repository) which is intended to track OpenSSF Scorecard results across repositories. (This link, https://github.com/open-telemetry/sig-security/blob/main/security-dashboard.md, was noted as inaccessible during initial Browse attempts [100] and needs to be verified and made accessible by the OpenTelemetry team). | |
| * **Context & Analysis**: The OpenSSF Best Practices Badge is a significant external validation of a project's commitment to secure development lifecycle practices, code quality, and community health. Achieving Silver or Gold status is a strong endorsement for CNCF Graduation. OpenTelemetry's progress, with several key components already badged (including one at Silver), demonstrates a distributed yet shared commitment to these best practices. The "In progress" status for the overall project suggests an ongoing effort to elevate the badge levels across the board. The participation in initiatives like the CNCF Security Slam further catalyzes these improvements. For a project as extensive as OpenTelemetry, achieving a high-level badge across all major components is a substantial undertaking, and the progress made so far is commendable. Providing a consolidated and up-to-date list of badge statuses for all key repositories will be important for the Graduation review. | |
| * **Supporting Link(s)**: | |
| * OpenSSF Best Practices Badge Program: https://www.bestpractices.dev/ [92] and https://openssf.org/projects/best-practices-badge/ [93] | |
| * opentelemetry-rust Badge (Silver): https://www.bestpractices.dev/projects/10394 [95] | |
| * opentelemetry-dotnet-instrumentation Badge (Passing): https://www.bestpractices.dev/projects/10371 [96] | |
| * opentelemetry-dotnet Badge (Passing): https://www.bestpractices.dev/projects/10370 [97] | |
| * opentelemetry-collector Badge (Passing): https://www.bestpractices.dev/projects/8404 [98] | |
| * OpenTelemetry Security Dashboard (for Scorecard info): https://github.com/open-telemetry/sig-security/blob/main/security-dashboard.md *(Link needs to be verified and made accessible by the OTel team)* * *(The OpenTelemetry team should provide a comprehensive, current list of OpenSSF badge statuses and direct links for all major repositories, including the Specification, Collector, and all primary SDKs, for the Graduation application.)* | |
| ## **XVIII. CLO Monitor** | |
| * **Requirement**: Evidence of CLO Monitor status. (A CNCF tool for checking project health best practices) | |
| * **Data Point**: | |
| * CLOMonitor is a CNCF tool that periodically checks open source project repositories to verify they meet certain project health best practices, covering areas like code, community, documentation, and security [101]. | |
| * Projects listed on clomonitor.io are provided with a badge and a report summary [101]. | |
| * OpenTelemetry is included in the CNCF CLO Monitor. A GitHub issue in the opentelemetry-go repository (\#6241) explicitly references the CLO Monitor page for OpenTelemetry and its sub-projects, indicating an awareness and intent to address reported issues [103]. The link provided in that issue is https://clomonitor.io/projects/cncf/open-telemetry\#opentelemetry-go [103]. | |
| * *Self-correction: Direct access to clomonitor.io and specific OpenTelemetry reports was problematic during the Browse phase [104], often requiring JavaScript or being inaccessible. The OpenTelemetry team must ensure that current CLO Monitor reports are accessible or provide a summary for the Graduation application.* * **Context & Analysis**: The CLO Monitor provides an automated assessment of a project's adherence to a range of best practices defined by the CNCF. A good score on CLOMonitor serves as an indicator of project health and maturity. OpenTelemetry's inclusion in CLOMonitor and the documented intent within sub-projects (like opentelemetry-go) to evaluate and address its findings [103] demonstrate engagement with CNCF's health assessment tools. The CLO Monitor checks across categories like code quality, community engagement, documentation standards, and security practices, aligning closely with several CNCF Graduation criteria. While direct access to live scores was hindered, the project's awareness and use of this tool are positive signs. | |
| * **Supporting Link(s)**: | |
| * CLO Monitor Main Page: https://clomonitor.io/ [101] | |
| * OpenTelemetry Project on CLO Monitor (general link, specific sub-project reports may exist): https://clomonitor.io/projects/cncf/opentelemetry [103] *(Link needs to be functional and provide clear reports for TOC review)* * GitHub Issue referencing CLO Monitor for opentelemetry-go: https://github.com/open-telemetry/opentelemetry-go/issues/6241 [103] | |
| * *(The OpenTelemetry team should provide a summary of its CLO Monitor scores for the main project and key components, along with direct links to accessible reports, for the Graduation application.)* | |
| ## **XIX. Other Relevant Information** | |
| * **Requirement**: \[ \] Any other relevant information that supports the graduation application. | |
| * **Data Point**: | |
| * **Industry Recognition and Impact**: OpenTelemetry is widely recognized as a foundational element for modern observability [11]. It is considered the "golden standard observability framework" [106] and is critical for organizations aiming to manage complex cloud-native systems effectively without vendor lock-in [7]. Surveys indicate high perceived maturity and significant ROI for adopters [11]. | |
| * **CNCF Ecosystem Integration**: OpenTelemetry is deeply integrated with and supports many other CNCF projects (e.g., Prometheus, Jaeger, Fluent Bit, Envoy, Kubernetes) and non-CNCF tools, enhancing the overall cloud-native ecosystem [12]. It provides a common telemetry layer for these diverse components. | |
| * **Educational Initiatives and Certification**: The CNCF has launched an OpenTelemetry Certified Associate (OTCA) certification, underscoring the project's importance and the demand for skilled practitioners [9]. This certification validates essential skills in using OpenTelemetry for monitoring distributed systems. | |
| * **Community Events and Engagement**: OpenTelemetry has a significant presence at industry conferences like KubeCon \+ CloudNativeCon and dedicated events such as the Open Observability Summit and OTel Community Day [4]. These events foster collaboration, learning, and advancement of open-source observability. | |
| * **Extensibility and Customization**: The OpenTelemetry Collector and SDKs are designed to be highly extensible, allowing users and vendors to build custom distributions and components tailored to specific needs, further promoting its adoption and adaptability [40]. | |
| * **Broad Vendor Support**: A vast ecosystem of over 40 observability vendors supports OpenTelemetry, contributing to the project and offering commercial solutions built upon it. This widespread vendor backing is a strong testament to its industry acceptance and de facto standard status [1]. | |
| * **Context & Analysis**: The information above collectively paints a picture of a project that is not only technically mature and widely adopted but also strategically vital to the cloud-native ecosystem. The strong industry recognition, deep integration with other CNCF projects, dedicated certification program, active community event participation, and extensive vendor support all highlight OpenTelemetry's critical role and readiness for Graduation. The project has moved beyond being just a collection of tools and SDKs to become a foundational standard that empowers the entire industry to achieve better observability. The development of semantic conventions for emerging areas like CI/CD [79] and the continuous evolution to incorporate new signals like profiling [11] demonstrate its forward-looking nature and commitment to addressing the evolving needs of the community. | |
| * **Supporting Link(s)**: | |
| * CNCF Project Page for OpenTelemetry: https://www.cncf.io/projects/opentelemetry/ [111] | |
| * OpenTelemetry Vendor Ecosystem: https://opentelemetry.io/ecosystem/vendors/ [42] | |
| * OpenTelemetry Integrations: https://opentelemetry.io/ecosystem/integrations/ [75] | |
| * CNCF OTCA Certification Announcement: https://www.cncf.io/blog/2024/11/15/gain-insights-into-cloud-native-applications-with-the-opentelemetry-certified-associate-otca/ [9] | |
| * Open Observability Summit Information [13] | |
| ## **XX. Conclusion** | |
| The evidence compiled in this report strongly supports OpenTelemetry's application for CNCF Graduation. The project has demonstrated: | |
| * **Strong Alignment with CNCF Mission**: By providing a vendor-neutral, open-source standard for ubiquitous telemetry, OpenTelemetry is a cornerstone of effective cloud-native observability. | |
| * **Mature Governance and Community Practices**: It adheres to the CNCF Code of Conduct, has clear trademark guidelines, robust and transparent governance structures (GC, TC, SIGs) with mechanisms for vendor neutrality, well-defined release processes for its key components, diverse public communication channels, and active participation in mentorship programs. | |
| * **Significant Technical Achievements and Activity**: OpenTelemetry is the second most active CNCF project, showing sustained growth in contributions and activity. It maintains comprehensive documentation and a well-used website, and employs robust CI/CD practices across its major components. | |
| * **Widespread Adoption and Impact**: The project boasts a large and growing list of end-user adopters across various industries, supported by public case studies and positive industry surveys highlighting tangible ROI. A vast ecosystem of vendors and integrations has formed around OpenTelemetry. | |
| * **Commitment to Security and Best Practices**: OpenTelemetry has successfully completed a third-party security audit with positive results and is actively pursuing OpenSSF Best Practices Badges, with several components already achieving recognized levels. It is also engaged with CNCF's CLO Monitor for ongoing health assessment. | |
| * **Clear Future Vision**: A public roadmap outlines continued development, including the maturation of existing signals and the introduction of new capabilities, ensuring the project's long-term relevance. | |
| OpenTelemetry has evolved from the merger of OpenTracing and OpenCensus into a de facto industry standard for cloud-native observability. Its commitment to openness, interoperability, and community-driven development has fostered a vibrant ecosystem. Based on the comprehensive evidence presented, OpenTelemetry fulfills the criteria for CNCF Graduation and is well-positioned to continue its pivotal role in the cloud-native landscape. | |
| ## **XXI. Appendix: Source Links** | |
| This appendix lists the source URLs referenced in this report along with a brief description of their content. | |
| 1. https://opentelemetry.io/ : Official OpenTelemetry website homepage, providing an overview of the project, its goals, and key features. | |
| 2. https://opentelemetry.io/community/mission/ : Page detailing the mission, vision, and values of the OpenTelemetry project. | |
| 3. https://github.com/cncf/toc/blob/main/.github/ISSUE\_TEMPLATE/template-graduation-application.md : CNCF Technical Oversight Committee (TOC) issue template for Graduation applications, outlining the required criteria. | |
| 4. https://www.cncf.io/projects/ : CNCF projects page, listing projects by maturity level (Sandbox, Incubation, Graduation). | |
| 5. https://www.cncf.io/archived-project-metrics/ : (Original link was likely https://www.cncf.io/project-metrics/ or similar, now potentially archived or moved) Page providing metrics and information about CNCF project maturity levels and graduation criteria. | |
| 6. https://opentelemetry.io/docs/concepts/ : OpenTelemetry documentation page explaining core concepts like observability, telemetry signals, and instrumentation. | |
| 7. https://betterstack.com/community/guides/observability/what-is-opentelemetry/ : A guide to OpenTelemetry, its components, benefits, and implementation best practices. | |
| 8. https://opentelemetry.io/docs/what-is-opentelemetry/ : OpenTelemetry documentation page providing an overview of what OpenTelemetry is, its history (merger of OpenTracing and OpenCensus), components, and principles. | |
| 9. https://www.cncf.io/blog/2024/11/15/gain-insights-into-cloud-native-applications-with-the-opentelemetry-certified-associate-otca/ : CNCF blog post announcing the OpenTelemetry Certified Associate (OTCA) certification, highlighting OpenTelemetry's activity and adoption. | |
| 10. https://www.mezmo.com/learn-observability/a-guide-to-opentelemetry-architecture-logs-and-implementation-best-practices : A guide to OpenTelemetry architecture, logs, and implementation best practices, including case studies like Employment Hero. | |
| 11. https://www.coresite.com/blog/opentelemetry-a-new-foundation-for-observability : Blog post discussing OpenTelemetry as a foundation for observability, citing an EMA survey on its maturity, adoption, and ROI. | |
| 12. https://www.cncf.io/blog/2023/05/03/opentelemetry-demystified-a-deep-dive-into-distributed-tracing/ : CNCF blog post demystifying OpenTelemetry, focusing on distributed tracing and its status as a highly active CNCF project. | |
| 13. https://www.cncf.io/announcements/2025/04/22/cncf-announces-openobservabilitycon-north-america-to-accelerate-open-source-innovation-and-tame-infrastructure-complexity/ : CNCF announcement for OpenObservability Summit North America, highlighting the importance of OpenTelemetry and other observability tools. | |
| 14. https://opentelemetry.io/docs/concepts/instrumentation/code-based/ : OpenTelemetry documentation on code-based instrumentation using APIs and SDKs. | |
| 15. https://github.com/open-telemetry/community : Main GitHub repository for the OpenTelemetry community, containing governance documents, roadmap, code of conduct, and contribution guidelines. | |
| 16. https://github.com/open-telemetry/community/blob/main/code-of-conduct.md : OpenTelemetry's Code of Conduct document, which adopts the CNCF Code of Conduct. | |
| 17. https://github.com/cncf/toc/issues/1739 : (Assumed link for OpenTelemetry's graduation application document, based on context) GitHub issue for OpenTelemetry's CNCF Graduation application, containing self-reported information against graduation criteria. | |
| 18. https://trademark.justia.com/971/51/opentelemetry-97151907.html : Justia Trademarks page for the "OPENTELEMETRY" trademark, showing its registration by The Linux Foundation. | |
| 19. https://opentelemetry.io/community/marketing-guidelines/ : OpenTelemetry's marketing guidelines for contributing organizations, including rules for using the project name and logo. | |
| 20. https://opentelemetry.io/community/ : OpenTelemetry community page, providing links to communication channels (Slack, mailing lists, social media), DevStats, trademark guidelines, and other community resources. | |
| 21. https://opentelemetry.io/docs/contributing/style-guide/ : OpenTelemetry documentation style guide for contributors. | |
| 22. https://opentelemetry.io/docs/specs/otel/ : OpenTelemetry specification documentation, including project naming conventions. | |
| 23. https://opentelemetry.io/docs/specs/semconv/general/naming/ : OpenTelemetry semantic convention naming guidelines, including rules for custom attributes and namespaces. | |
| 24. https://chronosphere.io/learn/top-3-opentelemetry-attribute-naming-best-practices/ : Article on best practices for OpenTelemetry attribute naming, emphasizing uniqueness and namespace usage. | |
| 25. https://opentelemetry.io/community/members/ : OpenTelemetry community members page, listing individuals in various roles like Governance Committee, Technical Committee, Maintainers, etc. | |
| 26. https://github.com/open-telemetry/community/blob/main/governance-charter.md : Charter for the OpenTelemetry Governance Committee (GC), detailing its goals, scope, structure, and election process. | |
| 27. https://github.com/open-telemetry/community/blob/main/community-members.md : Document listing members of the OpenTelemetry community, including GC, TC, maintainers, and their affiliations. | |
| 28. https://github.com/open-telemetry/community/blob/main/tech-committee-charter.md : Charter for the OpenTelemetry Technical Committee (TC), outlining its responsibilities, membership, and operational principles. | |
| 29. https://opentelemetry.io/docs/specs/otel/project-management/ : OpenTelemetry specification project management documentation, detailing the OTEP (OpenTelemetry Enhancement Proposal) process. | |
| 30. https://github.com/open-telemetry/opentelemetry-specification : GitHub repository for the OpenTelemetry Specification, including CHANGELOG.md, LICENSE, and CI/CD information via the "Actions" tab. | |
| 31. https://github.com/open-telemetry/opentelemetry-specification/releases : GitHub releases page for the OpenTelemetry Specification, listing versioned releases and changelogs. | |
| 32. https://github.com/open-telemetry/opentelemetry- (Note: This URL is incomplete.) | |
| 33. https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md : Collector Release Process documentation. | |
| 34. https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md : Java SDK Release Process documentation. | |
| 35. https://opentelemetry.io/blog/2025/go-goals/ : OpenTelemetry Go 2025 Goals. | |
| 36. https://www.cncf.io/blog/2025/03/03/announcing-the-beta-release-of-opentelemetry-go-auto-instrumentation-using-ebpf/ : Beta Release of OpenTelemetry Go Auto-Instrumentation using eBPF. | |
| 37. https://opentelemetry.io/docs/concepts/instrumentation/ : OpenTelemetry Instrumentation Concepts. | |
| 38. https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md : Specification Versioning and Stability. | |
| 39. https://github.com/open-telemetry/opentelemetry.io/blob/main/hugo.yaml : GitHub repository for opentelemetry.io. | |
| 40. https://github.com/open-telemetry/opentelemetry-collector-contrib : Contrib repository for the OpenTelemetry Collector. | |
| 41. https://logz.io/learn/opentelemetry-guide/ : Guide to OpenTelemetry by Logz.io. | |
| 42. https://opentelemetry.io/ecosystem/vendors/ : OpenTelemetry Vendors. | |
| 43. https://opentelemetry.io/blog/2024/year-in-review/ : OpenTelemetry.io 2024 review. | |
| 44. https://last9.io/blog/opentelemetry-profiling/ : OpenTelemetry Profiling. | |
| 45. https://opentelemetry.devstats.cncf.io/ : DevStats: OpenTelemetry. | |
| 46. https://opentelemetry.io/blog/ : Blog | OpenTelemetry. | |
| 47. https://iconsolutions.com/blog/i-got-opentelemetry-to-work-but-why-was-it-so-complicated/ : Integrating OTel by Icon Solutions. | |
| 48. https://opentelemetry.io/blog/2024/security-audit-results/ : OpenTelemetry Security Audit Published. | |
| 49. https://ostif.org/otel-audit-complete/ : OpenTelemetry Audit Complete by OSTIF. | |
| 50. https://opentelemetry.io/docs/security/ : Security | OpenTelemetry. | |
| 51. https://www.solarwinds.com/blog/opentelemetry-security-how-to : OpenTelemetry Security by SolarWinds. | |
| 52. https://github.com/open-telemetry/community/blob/main/roadmap.md : OpenTelemetry Community Roadmap. | |
| 53. https://github.com/open-telemetry/community/issues/969 : Google Summer of Code 2022 · Issue #969. | |
| 54. https://summerofcode.withgoogle.com/archive/2020/projects/5210917429575680 : GSoC 2020 - Optimising Haskell developer tool performance using OpenTelemetry. | |
| 55. https://summerofcode.withgoogle.com/programs/2025/projects/oNCE2drE : GSoC 2025 - Observable Public Cloud Infrastructure for IoT Developers. | |
| 56. https://forums.percona.com/t/google-summer-of-code-2025-project-ideas/36461 : Percona GSoC 2025 Project ideas. | |
| 57. https://www.reddit.com/r/OpenTelemetry/comments/1jueah1/call\_for\_research\_participants/ : Reddit Call for Research Participants (LFX Mentorship). | |
| 58. https://lfx.linuxfoundation.org/tools/mentorship/ : LFX Mentorship Program Information. | |
| 59. https://github.com/open-telemetry/community/issues/1894 : LFX Mentorship Mar-May 2024 Preparation Issue #1894. | |
| 60. https://github.com/open-telemetry/community/issues/1898 : LFX Mentorship Mar-May 2024 Proposal Submission Issue #1898. | |
| 61. https://github.com/cncf/mentoring/blob/main/programs/lfx-mentorship/2025/01-Mar-May/README.md : CNCF LFX Mentorship Mar-May 2025. | |
| 62. https://summerofcode.withgoogle.com/ : Google Summer of Code Home. | |
| 63. https://ioos.noaa.gov/news/ioos-mentoring-gsoc-2025/ : IOOS GSoC 2025 Mentoring. | |
| 64. https://opentelemetry.io/docs/ : Documentation - OpenTelemetry. | |
| 65. https://github.com/magsther/awesome-opentelemetry : A curated list of OpenTelemetry resources. | |
| 66. https://opentelemetry.io/docs/concepts/instrumentation/code-based/ : Code-based Instrumentation - OpenTelemetry. | |
| 67. https://opentelemetry.io/docs/collector/installation/ : Install the Collector | OpenTelemetry. | |
| 68. https://opentelemetry.io/docs/collector/ : Collector - OpenTelemetry. | |
| 69. https://opentelemetry.io/docs/collector/architecture/ : Collector Architecture | OpenTelemetry. | |
| 70. https://github.com/open-telemetry/opentelemetry-proto : OpenTelemetry protocol (OTLP) specification and Protobuf definitions. | |
| 71. https://github.com/open-telemetry/semantic-conventions : OpenTelemetry Semantic Conventions. | |
| 72. https://opentelemetry.io/docs/contributing/ : Contributing | OpenTelemetry. | |
| 73. https://opentelemetry.io/ecosystem/adopters/ : Adopters | OpenTelemetry. | |
| 74. https://opentelemetry.io/ecosystem/distributions/ : Distributions - OpenTelemetry. | |
| 75. https://opentelemetry.io/ecosystem/integrations/ : Integrations | OpenTelemetry. | |
| 76. https://github.com/open-telemetry/opentelemetry-collector : OpenTelemetry Collector GitHub repository. | |
| 77. https://github.com/open-telemetry/opentelemetry-java : OpenTelemetry Java GitHub repository. | |
| 78. https://signoz.io/blog/ci-cd-observability-opentelemetry/ : CI/CD Observability Powered by OpenTelemetry - SigNoz. | |
| 79. https://opentelemetry.io/docs/specs/semconv/registry/attributes/cicd/ : CICD Attributes | OpenTelemetry. | |
| 80. https://opentelemetry.io/docs/specs/semconv/resource/cicd/ : CICD Resource | OpenTelemetry. | |
| 81. https://github.com/open-telemetry/opentelemetry-specification/blob/master/CONTRIBUTING.md : OpenTelemetry Specification CONTRIBUTING.md. | |
| 82. https://github.com/open-telemetry/opentelemetry-collector/tree/main/.github/workflows : Collector GitHub Workflows. (Note: General reference, specific file implies more detail). | |
| 83. https://github.com/open-telemetry/opentelemetry-go/tree/main/.github/workflows : Go SDK GitHub Workflows. (Note: General reference). | |
| 84. (Reference to inaccessible link, removed as non-actionable for formatting the content itself) | |
| 85. https://github.com/open-telemetry/opentelemetry-collector/blob/main/README.md : Collector README. | |
| 86. https://github.com/open-telemetry/opentelemetry-go/blob/main/README.md : Go SDK README. | |
| 87. https://github.com/open-telemetry/opentelemetry-java/blob/main/README.md : Java SDK README. | |
| 88. https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/README.md : .NET SDK README. | |
| 89. https://opentelemetry.io/docs/contributing/pull-requests/ : Submitting content | OpenTelemetry. | |
| 90. https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md : Community CONTRIBUTING.md. | |
| 91. https://github.com/open-telemetry/community/issues/1252 : Re-evaluate Project CLA Issue #1252. | |
| 92. https://www.bestpractices.dev/ : OpenSSF Best Practices Badge Program. | |
| 93. https://openssf.org/projects/best-practices-badge/ : Best Practices Badge - OpenSSF. | |
| 94. https://openssf.org/best-practices-badge/ : (Duplicate of 93, can be consolidated if preferred). | |
| 95. https://www.bestpractices.dev/projects/10394?criteria\_level=2 : opentelemetry-rust Badge (Silver). | |
| 96. https://www.bestpractices.dev/projects/10371 : OpenTelemetry .NET Automatic Instrumentation Badge. | |
| 97. https://www.bestpractices.dev/projects/10370 : opentelemetry-dotnet Badge. | |
| 98. https://www.bestpractices.dev/projects/8404?criteria\_level=1 : OpenTelemetry Collector Badge. | |
| 99. https://www.cncf.io/wp-content/uploads/2025/05/01\_CNCF\_2025-Security-Slam-PDF-Report.pdf : 2025 CNCF Security Slam Report. | |
| 100. https://github.com/open-telemetry/sig-security/blob/main/security-dashboard.md : OpenTelemetry SIG Security Dashboard. (Note: User mentioned this was inaccessible). | |
| 101. https://github.com/cncf/clomonitor : CLOMonitor GitHub repository. | |
| 102. https://github.com/cncf/clomonitor/discussions/746 : CLOMonitor Discussion #746. | |
| 103. https://github.com/open-telemetry/opentelemetry-go/issues/6241 : Address issues with OpenTelemetry CLO Monitor #6241. | |
| 104. https://clomonitor.io/ : CLOMonitor. | |
| 105. https://clomonitor.io/projects/cncf/opentelemetry : CLOMonitor - OpenTelemetry. | |
| 106. https://www.honeycomb.io/blog/opentelemetry-metrics : OpenTelemetry Metrics Explained - Honeycomb. | |
| 107. https://events.linuxfoundation.org/open-observability-summit-otel-community-day/ : Open Observability Summit and OTel Community Day. | |
| 108. https://last9.io/blog/opentelemetry-collector-contrib/ : Everything You Should Know About OpenTelemetry Collector Contrib - Last9. | |
| 109. https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/README.md : mdatagen README. | |
| 110. https://bindplane.com/blog/opentelemetry-in-production-a-primer : OpenTelemetry in Production: A Primer - Bindplane. | |
| 111. https://www.cncf.io/projects/opentelemetry/ : OpenTelemetry | CNCF. | |
| 112. https://github.com/open-telemetry/community/blob/main/code-of-conduct.md : Community Code of Conduct (Duplicate of 16). | |
| #### **Works cited** | |
| 1. OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/ | |
| 2. OpenTelemetry mission, vision, and values | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/community/mission/ | |
| 3. toc/.github/ISSUE\_TEMPLATE/template-graduation-application.md ..., accessed June 4, 2025, https://github.com/cncf/toc/blob/main/.github/ISSUE\_TEMPLATE/template-graduation-application.md | |
| 4. landscape-transcript.txt | |
| 5. Graduated and Incubating Projects | CNCF, accessed June 4, 2025, https://www.cncf.io/projects/ | |
| 6. What is OpenTelemetry? - Google Cloud, accessed June 4, 2025, https://cloud.google.com/learn/what-is-opentelemetry | |
| 7. What is OpenTelemetry? A Comprehensive Guide | Better Stack Community, accessed June 4, 2025, https://betterstack.com/community/guides/observability/what-is-opentelemetry/ | |
| 8. What is OpenTelemetry?, accessed June 4, 2025, https://opentelemetry.io/docs/what-is-opentelemetry/ | |
| 9. Gain insights into cloud native applications with the OpenTelemetry Certified Associate (OTCA) | CNCF, accessed June 4, 2025, https://www.cncf.io/blog/2024/11/15/gain-insights-into-cloud-native-applications-with-the-opentelemetry-certified-associate-otca/ | |
| 10. A Guide to OpenTelemetry: Architecture, Logs, and Implementation Best Practices - Mezmo, accessed June 4, 2025, https://www.mezmo.com/learn-observability/a-guide-to-opentelemetry-architecture-logs-and-implementation-best-practices | |
| 11. OpenTelemetry: A New Foundation for Observability - CoreSite, accessed June 4, 2025, https://www.coresite.com/blog/opentelemetry-a-new-foundation-for-observability | |
| 12. OpenTelemetry demystified: a deep dive into distributed tracing | CNCF, accessed June 4, 2025, https://www.cncf.io/blog/2023/05/03/opentelemetry-demystified-a-deep-dive-into-distributed-tracing/ | |
| 13. CNCF Announces Open Observability Summit North America to Accelerate Open Source Innovation and Tame Infrastructure Complexity, accessed June 4, 2025, https://www.cncf.io/announcements/2025/04/22/cncf-announces-openobservabilitycon-north-america-to-accelerate-open-source-innovation-and-tame-infrastructure-complexity/ | |
| 14. What Is the OpenTelemetry Project and Why Is It Important? - Bindplane, accessed June 4, 2025, https://bindplane.com/blog/what-is-opentelemetry | |
| 15. open-telemetry/community: OpenTelemetry community ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community | |
| 16. community/README.md at main · open-telemetry/community · GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/README.md | |
| 17. \[Graduation\] OpenTelemetry Graduation Application · Issue #1739 ..., accessed June 4, 2025, https://github.com/cncf/toc/issues/1739 | |
| 18. OPENTELEMETRY Trademark Application of The Linux Foundation - Serial Number 97151907, accessed June 4, 2025, https://trademark.justia.com/971/51/opentelemetry-97151907.html | |
| 19. OpenTelemetry Marketing Guidelines for Contributing Organizations ..., accessed June 4, 2025, https://opentelemetry.io/community/marketing-guidelines/ | |
| 20. Community | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/community/ | |
| 21. Documentation style guide | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/contributing/style-guide/ | |
| 22. OpenTelemetry Specification 1.45.0, accessed June 4, 2025, https://opentelemetry.io/docs/specs/otel/ | |
| 23. Naming - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/specs/semconv/general/naming/ | |
| 24. Top 3 OpenTelemetry attribute naming best practices - Chronosphere, accessed June 4, 2025, https://chronosphere.io/learn/top-3-opentelemetry-attribute-naming-best-practices/ | |
| 25. Members of the OpenTelemetry Project | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/community/members/ | |
| 26. OpenTelemetry Governance Committee Charter - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/governance-charter.md | |
| 27. OpenTelemetry Community Members - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/community-members.md | |
| 28. OpenTelemetry Technical Committee (TC) Charter - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/tech-committee-charter.md | |
| 29. Project Management | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/specs/otel/project-management/ | |
| 30. open-telemetry/opentelemetry-specification: Specifications ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-specification | |
| 31. opentelemetry-specification/README.md at main · open-telemetry ..., accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-specification/blob/main/README.md | |
| 32. Releases · open-telemetry/opentelemetry-specification - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-specification/releases | |
| 33. opentelemetry-collector/docs/release.md at main - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/release.md | |
| 34. opentelemetry-java/RELEASING.md at main - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-java/blob/main/RELEASING.md | |
| 35. OpenTelemetry Go 2025 Goals, accessed June 4, 2025, https://opentelemetry.io/blog/2025/go-goals/ | |
| 36. Announcing the Beta Release of OpenTelemetry Go Auto-Instrumentation using eBPF, accessed June 4, 2025, https://www.cncf.io/blog/2025/03/03/announcing-the-beta-release-of-opentelemetry-go-auto-instrumentation-using-ebpf/ | |
| 37. Instrumentation | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/concepts/instrumentation/ | |
| 38. opentelemetry-specification/specification/versioning-and-stability.md ..., accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/versioning-and-stability.md | |
| 39. opentelemetry.io/hugo.yaml at main · open-telemetry/opentelemetry.io · GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry.io/blob/main/hugo.yaml | |
| 40. Contrib repository for the OpenTelemetry Collector - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector-contrib | |
| 41. Guide to OpenTelemetry - Logz.io, accessed June 4, 2025, https://logz.io/learn/opentelemetry-guide/ | |
| 42. Vendors - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/ecosystem/vendors/ | |
| 43. OpenTelemetry.io 2024 review, accessed June 4, 2025, https://opentelemetry.io/blog/2024/year-in-review/ | |
| 44. OpenTelemetry Profiling: A Look into Performance Insights - Last9, accessed June 4, 2025, https://last9.io/blog/opentelemetry-profiling/ | |
| 45. DevStats: OpenTelemetry, accessed June 4, 2025, https://opentelemetry.devstats.cncf.io/ | |
| 46. Blog | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/blog/ | |
| 47. I got OpenTelemetry to work. But why was it so complicated? - Icon Solutions, accessed June 4, 2025, https://iconsolutions.com/blog/i-got-opentelemetry-to-work-but-why-was-it-so-complicated/ | |
| 48. OpenTelemetry Security Audit Published | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/blog/2024/security-audit-results/ | |
| 49. OpenTelemetry Audit Complete! – OSTIF.org, accessed June 4, 2025, https://ostif.org/otel-audit-complete/ | |
| 50. Security | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/security/ | |
| 51. OpenTelemetry Security: How To Keep Telemetry Data Safe - SolarWinds Blog, accessed June 4, 2025, https://www.solarwinds.com/blog/opentelemetry-security-how-to | |
| 52. community/roadmap.md at main · open-telemetry/community · GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/roadmap.md | |
| 53. Google summer of code 2022 · Issue #969 · open-telemetry ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/issues/969 | |
| 54. Optimising Haskell developer tool performance using OpenTelemetry - Archive Project Details | Google Summer of Code, accessed June 4, 2025, https://summerofcode.withgoogle.com/archive/2020/projects/5210917429575680 | |
| 55. Observable Public Cloud Infrastructure for IoT Developers - Program Project | Google Summer of Code, accessed June 4, 2025, https://summerofcode.withgoogle.com/programs/2025/projects/oNCE2drE | |
| 56. Google Summer of Code 2025: Project ideas - Partnerships - Percona Community Forum, accessed June 4, 2025, https://forums.percona.com/t/google-summer-of-code-2025-project-ideas/36461 | |
| 57. Call for Research Participants : r/OpenTelemetry - Reddit, accessed June 4, 2025, https://www.reddit.com/r/OpenTelemetry/comments/1jueah1/call\_for\_research\_participants/ | |
| 58. LFX Mentorship – LFX Tools - Linux Foundation, accessed June 4, 2025, https://lfx.linuxfoundation.org/tools/mentorship/ | |
| 59. Prepare for LFX Mentorship Mar-May 2024 · Issue #1894 · open ..., accessed June 4, 2025, https://github.com/open-telemetry/community/issues/1894 | |
| 60. LFX Mentorship Mar-May 2024 - Submit proposals · Issue #1898 · open-telemetry/community - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/issues/1898 | |
| 61. mentoring/programs/lfx-mentorship/2025/01-Mar-May/README.md at main - GitHub, accessed June 4, 2025, https://github.com/cncf/mentoring/blob/main/programs/lfx-mentorship/2025/01-Mar-May/README.md | |
| 62. Google Summer of Code: Home, accessed June 4, 2025, https://summerofcode.withgoogle.com/ | |
| 63. IOOS is in for Google Summer of Code 2025! - Integrated Ocean Observing System - NOAA, accessed June 4, 2025, https://ioos.noaa.gov/news/ioos-mentoring-gsoc-2025/ | |
| 64. Documentation - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/ | |
| 65. magsther/awesome-opentelemetry: A curated list of OpenTelemetry resources - GitHub, accessed June 4, 2025, https://github.com/magsther/awesome-opentelemetry | |
| 66. Code-based - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/concepts/instrumentation/code-based/ | |
| 67. Install the Collector | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/collector/installation/ | |
| 68. Collector - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/collector/ | |
| 69. Architecture | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/collector/architecture/ | |
| 70. open-telemetry/opentelemetry-proto: OpenTelemetry protocol (OTLP) specification and Protobuf definitions - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-proto | |
| 71. open-telemetry/semantic-conventions - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/semantic-conventions | |
| 72. Contributing | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/contributing/ | |
| 73. Adopters | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/ecosystem/adopters/ | |
| 74. Distributions - OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/ecosystem/distributions/ | |
| 75. Integrations | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/ecosystem/integrations/ | |
| 76. open-telemetry/opentelemetry-collector: OpenTelemetry ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector | |
| 77. open-telemetry/opentelemetry-java: OpenTelemetry Java ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-java | |
| 78. CI/CD Observability Powered by OpenTelemetry - SigNoz, accessed June 4, 2025, https://signoz.io/blog/ci-cd-observability-opentelemetry/ | |
| 79. CICD | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/specs/semconv/registry/attributes/cicd/ | |
| 80. CICD | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/specs/semconv/resource/cicd/ | |
| 81. opentelemetry-specification/CONTRIBUTING.md at main - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-specification/blob/master/CONTRIBUTING.md | |
| 82. github.com, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector/tree/main/.github/workflows | |
| 83. github.com, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-go/tree/main/.github/workflows | |
| 84. accessed December 31, 1969, https://github.com/open-telemetry/opentelemetry-collector/.github/workflows | |
| 85. opentelemetry-collector/README.md at main · open-telemetry ..., accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector/blob/main/README.md | |
| 86. opentelemetry-go/README.md at main · open-telemetry ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-go/blob/main/README.md | |
| 87. opentelemetry-java/README.md at main · open-telemetry ... - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-java/blob/main/README.md | |
| 88. opentelemetry-dotnet/README.md at main · open-telemetry ..., accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/README.md | |
| 89. Submitting content | OpenTelemetry, accessed June 4, 2025, https://opentelemetry.io/docs/contributing/pull-requests/ | |
| 90. community/CONTRIBUTING.md at main · open-telemetry/community ..., accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md | |
| 91. Re-evaluate Project CLA #1252 - open-telemetry/community - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/community/issues/1252 | |
| 92. BadgeApp, accessed June 4, 2025, https://www.bestpractices.dev/ | |
| 93. Best Practices Badge - Open Source Security Foundation, accessed June 4, 2025, https://openssf.org/projects/best-practices-badge/ | |
| 94. Best Practices Badge - Open Source Security Foundation, accessed June 4, 2025, https://openssf.org/best-practices-badge/ | |
| 95. opentelemetry-rust - BadgeApp, accessed June 4, 2025, https://www.bestpractices.dev/projects/10394?criteria\_level=2 | |
| 96. OpenTelemetry .NET Automatic Instrumentation - BadgeApp, accessed June 4, 2025, https://www.bestpractices.dev/projects/10371 | |
| 97. BadgeApp - OpenSSF Best Practices Badge Program, accessed June 4, 2025, https://www.bestpractices.dev/projects/10370 | |
| 98. OpenTelemetry Collector - BadgeApp, accessed June 4, 2025, https://www.bestpractices.dev/de/projects/8404?criteria\_level=1 | |
| 99. 2025 SECURITY SLAM AT KCCN EUROPE, accessed June 4, 2025, https://www.cncf.io/wp-content/uploads/2025/05/01\_CNCF\_2025-Security-Slam-PDF-Report.pdf | |
| 100. github.com, accessed June 4, 2025, https://github.com/open-telemetry/sig-security/blob/main/security-dashboard.md | |
| 101. cncf/clomonitor: CLOMonitor is a tool that periodically ... - GitHub, accessed June 4, 2025, https://github.com/cncf/clomonitor | |
| 102. Does CLO mean anything in particular ? · cncf clomonitor · Discussion #746 - GitHub, accessed June 4, 2025, https://github.com/cncf/clomonitor/discussions/746 | |
| 103. Address issues with OpenTelemetry CLO Monitor #6241 - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-go/issues/6241 | |
| 104. CLOMonitor, accessed June 4, 2025, https://clomonitor.io/ | |
| 105. clomonitor.io, accessed June 4, 2025, https://clomonitor.io/projects/cncf/opentelemetry | |
| 106. OpenTelemetry Metrics Explained: A Guide for Engineers - Honeycomb, accessed June 4, 2025, https://www.honeycomb.io/blog/opentelemetry-metrics | |
| 107. Open Observability Summit and OTel Community Day | LF Events, accessed June 4, 2025, https://events.linuxfoundation.org/open-observability-summit-otel-community-day/ | |
| 108. Everything You Should Know About OpenTelemetry Collector Contrib - Last9, accessed June 4, 2025, https://last9.io/blog/opentelemetry-collector-contrib/ | |
| 109. opentelemetry-collector/cmd/mdatagen/README.md at main - GitHub, accessed June 4, 2025, https://github.com/open-telemetry/opentelemetry-collector/blob/main/cmd/mdatagen/README.md | |
| 110. OpenTelemetry in Production: A Primer - Bindplane, accessed June 4, 2025, https://bindplane.com/blog/opentelemetry-in-production-a-primer | |
| 111. OpenTelemetry | CNCF, accessed June 4, 2025, https://www.cncf.io/projects/opentelemetry/ | |
| 112. community/code-of-conduct.md at main · open-telemetry/community ..., accessed June 4, 2025, https://github.com/open-telemetry/community/blob/main/code-of-conduct.md |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment