|
| 1 | +--- |
| 2 | +title: Opentelemetry.io 2024 review |
| 3 | +linkTitle: Year in review |
| 4 | +date: 2024-12-17 |
| 5 | +author: >- |
| 6 | + [Severin Neumann](https://github.com/svrnm) (Cisco), [Patrice |
| 7 | + Chalin](https://github.com/chalin/) (CNCF), [Tiffany |
| 8 | + Hrabusa](https://github.com/tiffany76) (Grafana Labs) |
| 9 | +sig: Comms |
| 10 | +cSpell:ignore: Chalin Hrabusa opentelemetrybot |
| 11 | +--- |
| 12 | + |
| 13 | +As 2024 draws to a close, we reflect on the year and share some insights and |
| 14 | +accomplishments from [SIG Communications][Comms meetings], the team responsible |
| 15 | +for managing this website, blog, and documentation. |
| 16 | + |
| 17 | +## Key achievements of 2024 |
| 18 | + |
| 19 | +Several key accomplishments stand out in our efforts to make OpenTelemetry |
| 20 | +documentation more accessible, user-friendly, and impactful for our global |
| 21 | +community. |
| 22 | + |
| 23 | +### Multilingual documentation <i class="fa-solid fa-language"></i> {#multilingual-documentation} |
| 24 | + |
| 25 | +A major accomplishment this year was achieving multilingual support with the |
| 26 | +launch of our [localized documentation](/blog/2024/docs-localized/). Thanks to |
| 27 | +the efforts of localization teams, over 120 pages were translated from English |
| 28 | +into other languages. The available translations include: |
| 29 | + |
| 30 | +- [Chinese](/zh/) |
| 31 | +- [French](/fr/) |
| 32 | +- [Japanese](/ja/) |
| 33 | +- [Portuguese](/pt/) |
| 34 | +- [Spanish](/es/) |
| 35 | + |
| 36 | +A big thank you to everyone who contributed to this initiative. These |
| 37 | +translations make OpenTelemetry more accessible, enhancing the user experience |
| 38 | +for our global audience. |
| 39 | + |
| 40 | +### Information Architecture (IA) improvements <i class="fa-solid fa-sitemap"></i> {#ia-improvements} |
| 41 | + |
| 42 | +To **improve readership experience** and make OpenTelemetry **documentation more |
| 43 | +intuitive and accessible**, we undertook important updates to our Information |
| 44 | +Architecture (IA) this year. These changes were driven by the need to better |
| 45 | +organize content, clarify the purpose of key sections, and provide a more |
| 46 | +structured and user-friendly experience for end-users and developers. |
| 47 | + |
| 48 | +Key IA updates include: |
| 49 | + |
| 50 | +- Renaming the `Instrumentation` section to |
| 51 | + [Language APIs & SDKs](/docs/languages/) to better reflect its purpose and set |
| 52 | + clearer expectations for users. |
| 53 | +- Moving `Automatic Instrumentation` into the new |
| 54 | + [Zero-code Instrumentation](/docs/zero-code/) section to more clearly |
| 55 | + distinguish between instrumentation APIs & SDKs and tools like the Java agent, |
| 56 | + used to inject telemetry. |
| 57 | +- Following these updates, the Java SIG [proposed] and [reorganized their |
| 58 | + documentation][java-reorg], introducing substantial improvements to the |
| 59 | + structure and clarity of the content. The bulk of this effort is reflected in |
| 60 | + these PRs: |
| 61 | + |
| 62 | + - [Refactor Java SDK and configuration #4966][#4966] |
| 63 | + - [Refactor Java instrumentation #5276][#5276] |
| 64 | + - [Move performance to Java agent, merge Javadoc into API page #5590][#5590] |
| 65 | + |
| 66 | + <!-- prettier-ignore --> |
| 67 | + Kudos to [Jack Berg] and the [Java SIG] for their exemplary leadership in |
| 68 | + improving language-SIG documentation! |
| 69 | + {.mt-4} |
| 70 | + |
| 71 | +Next year, we aim to redesign how OpenTelemetry is introduced to beginners, |
| 72 | +ensuring a smoother and more accessible learning experience. If you're |
| 73 | +passionate about making OpenTelemetry easier to understand and use, we’d love |
| 74 | +your contributions — [join us][#2427] in this collaborative effort. |
| 75 | + |
| 76 | +[#2427]: https://github.com/open-telemetry/community/pull/2427 |
| 77 | +[#4966]: https://github.com/open-telemetry/opentelemetry.io/pull/4966 |
| 78 | +[#5276]: https://github.com/open-telemetry/opentelemetry.io/pull/5276 |
| 79 | +[#5590]: https://github.com/open-telemetry/opentelemetry.io/pull/5590 |
| 80 | +[Jack Berg]: https://github.com/jack-berg |
| 81 | +[Java SIG]: |
| 82 | + https://docs.google.com/document/d/1D7ZD93LxSWexHeztHohRp5yeoTzsi9Dj1HRm7Tad-hM |
| 83 | +[proposed]: https://github.com/open-telemetry/opentelemetry.io/discussions/4853 |
| 84 | +[java-reorg]: |
| 85 | + https://github.com/open-telemetry/opentelemetry.io/pulls?q=is%3Apr+java+is%3Aclosed+label%3Asig%3Ajava+merged%3A2024-01-01..2024-12-31+author%3Ajack-berg |
| 86 | + |
| 87 | +## Year in numbers <i class="fa-solid fa-chart-pie"></i> {#year-in-numbers} |
| 88 | + |
| 89 | +### Contributions |
| 90 | + |
| 91 | +In [December 2022], we started [monthly releases] of the website so that we |
| 92 | +could regularly summarize activities and highlight significant contributions. |
| 93 | +These releases allow us to track progress over time and perform long-term |
| 94 | +comparisons. |
| 95 | + |
| 96 | +For instance, comparing the periods [December 2022 to November 2023] and |
| 97 | +[December 2023 to November 2024], we observed an upward trend in contributions: |
| 98 | + |
| 99 | +- **Commits** increased 33% from 1,011 to 1,340 |
| 100 | +- **Contributors** grew 15% from 92 to 106 |
| 101 | +- The only metric that declined was the **number of files changed**, which |
| 102 | + decreased from 1,864 to 1,624 (13%) |
| 103 | + |
| 104 | +Since the repository’s inception in April 2019, the community has seen |
| 105 | +remarkable growth, with: |
| 106 | + |
| 107 | +- 3,824 merged pull requests (3,982 commits) by |
| 108 | +- 768 contributors |
| 109 | + |
| 110 | +Thank you to every contributor for helping to build and improve the |
| 111 | +OpenTelemetry website. Your efforts make a difference! |
| 112 | + |
| 113 | +[December 2022]: |
| 114 | + https://github.com/open-telemetry/opentelemetry.io/releases/tag/2022.12 |
| 115 | +[December 2022 to November 2023]: |
| 116 | + https://github.com/open-telemetry/opentelemetry.io/compare/2022.12...2023.11 |
| 117 | +[December 2023 to November 2024]: |
| 118 | + https://github.com/open-telemetry/opentelemetry.io/compare/2023.12...2024.11 |
| 119 | +[monthly releases]: https://github.com/open-telemetry/opentelemetry.io/releases |
| 120 | + |
| 121 | +### Which pages were the most popular? |
| 122 | + |
| 123 | +According to our publicly available [analytics] data, [opentelemetry.io](/) was |
| 124 | +viewed **12 million** times across 4 million sessions this year. This marks a |
| 125 | +**16% increase** over last year's nearly 10 million views and over 3 million |
| 126 | +sessions. |
| 127 | + |
| 128 | +The most popular pages and sections of the documentation were: |
| 129 | + |
| 130 | +| Page/Section | Views | % [^1] | |
| 131 | +| ------------------------ | ----: | -----: | |
| 132 | +| [What is OpenTelemetry?] | 290K | 2.4% | |
| 133 | +| [Collector] | 1.3M | 10.5% | |
| 134 | +| [Concepts] | 1.2M | 9.8% | |
| 135 | +| [Demo] | 829K | 6.7% | |
| 136 | +| [Ecosystem] | 500K | 4.0% | |
| 137 | + |
| 138 | +[analytics]: https://lookerstudio.google.com/s/tSTKxK1ECeU |
| 139 | +[Collector]: /docs/collector |
| 140 | +[Concepts]: /docs/what-is-opentelemetry/ |
| 141 | +[Demo]: /docs/demo/ |
| 142 | +[Ecosystem]: /ecosystem/ |
| 143 | +[What is OpenTelemetry?]: /docs/what-is-opentelemetry/ |
| 144 | + |
| 145 | +[^1]: Percentage of the site-total 12M views. |
| 146 | + |
| 147 | +### Fun trivia <i class="fa-solid fa-lightbulb"></i> {#trivia} |
| 148 | + |
| 149 | +Did you know that: |
| 150 | + |
| 151 | +- "OpenTelemetry" occurs 7.3K times in the English website pages, making it the |
| 152 | + 3rd most frequent word after "the" and "to." The word "collector" is used 3.2K |
| 153 | + times, putting it in 11th place! |
| 154 | +- The [Collector landing page] has been the most updated file since its |
| 155 | + creation, with 91 changes. |
| 156 | +- With 511 commits (27K additions, and 10K deletions) the [opentelemetrybot] is |
| 157 | + the fourth most active contributor. Go bots! |
| 158 | +- The record for the PR with the most comments this year—and of all time is held |
| 159 | + by: |
| 160 | + |
| 161 | + - [Generative AI updates blog post (#5575)][#5575], with 150 comments! |
| 162 | + |
| 163 | + <!-- prettier-ignore --> |
| 164 | + A close second goes to: |
| 165 | + {.mt-3} |
| 166 | + |
| 167 | + - [Portuguese translation of Go instrumentation][#5380], with 146 comments |
| 168 | + |
| 169 | +[#5380]: https://github.com/open-telemetry/opentelemetry.io/pull/5380 |
| 170 | +[#5575]: https://github.com/open-telemetry/opentelemetry.io/pull/5575 |
| 171 | +[Collector landing page]: /docs/collector/ |
| 172 | +[opentelemetrybot]: https://github.com/opentelemetrybot |
| 173 | + |
| 174 | +## Amazing Community <i class="fa-regular fa-heart"></i> {#amazing-community} |
| 175 | + |
| 176 | +With [1.3K PRs], we collectively contributed an equally impressive number of |
| 177 | +reviews to ensure that content is accurate, valuable, aligned with our |
| 178 | +documentation goals, and easy to read and understand. |
| 179 | + |
| 180 | +In addition to PRs, contributors created nearly [500 issues] and engaged in many |
| 181 | +[discussions], reporting bugs, suggesting improvements, and driving |
| 182 | +collaboration. Each of these efforts reflects our community's dedication to |
| 183 | +maintaining the quality of OpenTelemetry docs. |
| 184 | + |
| 185 | +We are fortunate to have many contributors who take on responsibilities, |
| 186 | +including: |
| 187 | + |
| 188 | +- **Approvers and maintainers** from other SIGs who co-own parts of the docs |
| 189 | +- **Localization teams** who oversee translations into various languages |
| 190 | +- **The OpenTelemetry community**, whose contributions make all the difference |
| 191 | + — every drive-by edit and typo fix counts! |
| 192 | +- **SIG Communications team members**, for their contributions and for |
| 193 | + orchestrating it all! |
| 194 | + |
| 195 | +Thank you to everyone who contributed their time and expertise to OpenTelemetry |
| 196 | +docs this year! |
| 197 | + |
| 198 | +[500 issues]: |
| 199 | + https://github.com/open-telemetry/opentelemetry.io/issues?q=is%3Aissue+created%3A2024-01-01..2024-12-31 |
| 200 | +[1.3K PRs]: |
| 201 | + https://github.com/open-telemetry/opentelemetry.io/pulls?q=is%3Apr+is%3Amerged+merged%3A2024-01-01..2024-12-31 |
| 202 | + |
| 203 | +## Join us in 2025 |
| 204 | + |
| 205 | +A big shout-out to everyone for making 2024 a successful year! We look forward |
| 206 | +to continuing our collaboration in 2025. |
| 207 | + |
| 208 | +Whether you're an end user, a contributor, or simply enthusiastic about |
| 209 | +OpenTelemetry, we welcome your participation. You can [get involved] by raising |
| 210 | +[issues], participating in [discussions], or [submitting PRs]. |
| 211 | + |
| 212 | +You can also join us: |
| 213 | + |
| 214 | +- On the [CNCF Slack](https://slack.cncf.io/) at any one of the many |
| 215 | + `#otel`-prefixed channels. |
| 216 | +- In [Comms meetings], held every other Monday at 10:00 AM Pacific time. |
| 217 | + |
| 218 | +Together, we can make 2025 another amazing year for [opentelemetry.io](/)! |
| 219 | + |
| 220 | +[Comms meetings]: |
| 221 | + https://docs.google.com/document/d/1wW0jLldwXN8Nptq2xmgETGbGn9eWP8fitvD5njM-xZY |
| 222 | +[discussions]: https://github.com/open-telemetry/opentelemetry.io/discussions |
| 223 | +[get involved]: /docs/contributing/ |
| 224 | +[issues]: https://github.com/open-telemetry/opentelemetry.io/issues |
| 225 | +[submitting PRs]: /docs/contributing/pull-requests/ |
0 commit comments