diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index c93011fdaf0b..a66882ada401 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -22,7 +22,7 @@ content-modules/opentelemetry-proto @open-telemetry/docs-maintainers @open- content-modules/opentelemetry-specification @open-telemetry/docs-maintainers @open-telemetry/specs-approvers content-modules/semantic-conventions @open-telemetry/docs-maintainers @open-telemetry/specs-semconv-approvers content/en/blog/ @open-telemetry/docs-maintainers -content/en/community/end-user/ @open-telemetry/docs-approvers @open-telemetry/end-user-wg +content/en/community/end-user/ @open-telemetry/docs-approvers @open-telemetry/sig-end-user-approvers content/en/docs/collector @open-telemetry/docs-approvers @open-telemetry/collector-approvers content/en/docs/demo @open-telemetry/docs-approvers @open-telemetry/demo-approvers content/en/docs/languages/cpp/ @open-telemetry/docs-approvers @open-telemetry/cpp-approvers @@ -41,4 +41,4 @@ content/en/docs/kubernetes/helm/ @open-telemetry/docs-approvers @open-te content/en/docs/specs/ @open-telemetry/docs-approvers @open-telemetry/specs-approvers content/en/docs/security/ @open-telemetry/docs-approvers @open-telemetry/sig-security-maintainers content/en/ecosystem/demo/ @open-telemetry/demo-approvers @open-telemetry/demo-approvers -content/en/docs/contributing/ @open-telemetry/docs-approvers @open-telemetry/docs-maintainers \ No newline at end of file +content/en/docs/contributing/ @open-telemetry/docs-approvers @open-telemetry/docs-maintainers diff --git a/.github/component-label-map.yml b/.github/component-label-map.yml new file mode 100644 index 000000000000..a91191aea426 --- /dev/null +++ b/.github/component-label-map.yml @@ -0,0 +1,76 @@ +blog: + - changed-files: + - any-glob-to-any-file: + - content/en/blog/** +sig:cpp: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/cpp/** +sig:erlang: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/erlang/** +sig:go: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/go/** +sig:java: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/java/** +sig:js: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/js/** +sig:dotnet: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/net/** +sig:php: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/php/** +sig:python: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/python/** +sig:ruby: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/ruby/** +sig:rust: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/rust/** +sig:swift: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/languages/swift/** +sig:operator: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/kubernetes/operator/** +sig:helm: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/kubernetes/helm/** +sig:security: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/security/** +sig:demo: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/demo/** +sig:collector: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/collector/** +sig:enduser: + - changed-files: + - any-glob-to-any-file: + - content/en/community/end-user/** +sig:spec: + - changed-files: + - any-glob-to-any-file: + - content/en/docs/specs/** diff --git a/.github/workflows/label-prs.yml b/.github/workflows/label-prs.yml new file mode 100644 index 000000000000..ffa50224c538 --- /dev/null +++ b/.github/workflows/label-prs.yml @@ -0,0 +1,16 @@ +name: 'Label PR' +on: + - pull_request_target + +jobs: + labeler: + name: 'Add component labels' + permissions: + contents: read + pull-requests: write + runs-on: ubuntu-latest + steps: + - uses: actions/checkout@v4 + - uses: actions/labeler@v5 + with: + configuration-path: '.github/component-label-map.yml' diff --git a/.github/workflows/pr-actions.yml b/.github/workflows/pr-actions.yml index 8c16950b3b97..360287437cf9 100644 --- a/.github/workflows/pr-actions.yml +++ b/.github/workflows/pr-actions.yml @@ -50,11 +50,11 @@ jobs: run: | gh pr comment $PR_NUM -b "You triggered fix:${PR_ACTION} action run at $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID" env: - GH_TOKEN: ${{ github.token }} + GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }} - run: gh pr checkout $PR_NUM -b "pr-action-${RANDOM}" env: - GH_TOKEN: ${{ github.token }} + GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }} - name: Create NPM cache-hash input file run: | @@ -106,4 +106,4 @@ jobs: run: | gh pr comment $PR_NUM -b "fix:${PR_ACTION} run failed, please check $GITHUB_SERVER_URL/$GITHUB_REPOSITORY/actions/runs/$GITHUB_RUN_ID for details" env: - GH_TOKEN: ${{ github.token }} + GH_TOKEN: ${{ secrets.OPENTELEMETRYBOT_GITHUB_TOKEN }} diff --git a/.gitmodules b/.gitmodules index 690e80fb5c0d..e89e163409df 100644 --- a/.gitmodules +++ b/.gitmodules @@ -1,13 +1,13 @@ [submodule "themes/docsy"] path = themes/docsy url = https://github.com/google/docsy.git - docsy-pin = v0.9.1-17-gb077a74 + docsy-pin = v0.10.0-2-g6f7e81d docsy-note = "2024-04-01 Switching to google/docsy.git from cncf/docsy.git since we don't have any CNCF customizations." docsy-reminder = "Ensure that any tag referenced by `docsy-pin` is present in the remote repo (url), otherwise add (push) the tags to the repo." [submodule "content-modules/opentelemetry-specification"] path = content-modules/opentelemetry-specification url = https://github.com/open-telemetry/opentelemetry-specification.git - spec-pin = v1.31.0 + spec-pin = v1.33.0 [submodule "content-modules/community"] path = content-modules/community url = https://github.com/open-telemetry/community @@ -15,7 +15,7 @@ [submodule "content-modules/opentelemetry-proto"] path = content-modules/opentelemetry-proto url = https://github.com/open-telemetry/opentelemetry-proto - otlp-pin = v1.2.0 + otlp-pin = v1.3.1 [submodule "content-modules/semantic-conventions"] path = content-modules/semantic-conventions url = https://github.com/open-telemetry/semantic-conventions @@ -23,7 +23,7 @@ [submodule "content-modules/opamp-spec"] path = content-modules/opamp-spec url = https://github.com/open-telemetry/opamp-spec - opamp-pin = v0.8.0-5-g0360da8 + opamp-pin = v0.9.0-2-g950df29 [submodule "content-modules/opentelemetry-go"] path = content-modules/opentelemetry-go url = https://github.com/open-telemetry/opentelemetry-go diff --git a/.htmltest.yml b/.htmltest.yml index 8b68fc6a980e..10ed33141869 100644 --- a/.htmltest.yml +++ b/.htmltest.yml @@ -3,6 +3,7 @@ DirectoryPath: public IgnoreDirectoryMissingTrailingSlash: true IgnoreAltMissing: true IgnoreCanonicalBrokenLinks: false +IgnoreInternalEmptyHash: true # TODO: remove after resolution of https://github.com/google/docsy/issues/1995 CheckMailto: false TestFilesConcurrently: true IgnoreDirs: @@ -35,6 +36,8 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored - ^https://x.com # OTel Google calendar - curl returns 200, but the link checker gets a 401: - ^https://calendar.google.com/calendar/embed\?src=google.com_b79e3e90j7bbsa2n2p5an5lf60%40group.calendar.google.com + # YouTube playlists sometimes give a 404, although they give a 200 when accessed via browser: + - ^https://www.youtube.com/playlist\?list= # Ignore Docsy-generated GitHub links for now - ^https?://github\.com/.*?/.*?/(new|edit)/ # view-page, edit-source etc diff --git a/.prettierignore b/.prettierignore index 6ee6abc77c04..c44f102276cb 100644 --- a/.prettierignore +++ b/.prettierignore @@ -8,6 +8,11 @@ /layouts/shortcodes/* !/layouts/shortcodes/docs +# Ignore all languages other than en for now + +/content/* +!/content/en + # Ignore content-modules except for published Community pages /content-modules/* diff --git a/README.md b/README.md index 786d6f049372..20e8a68d7ccd 100644 --- a/README.md +++ b/README.md @@ -36,7 +36,7 @@ Check out the [OpenTelemetry community calendar][] for the Zoom link and any updates to this schedule. Meeting notes are available as a public [Google doc][]. If you have trouble -accessing the doc, get in touch on [Slack][]. +accessing the doc, get in touch in the `#otel-comms` channel on [Slack][]. Here is a list of community roles with current and previous members: @@ -94,4 +94,4 @@ already contributed][contributors]! https://github.com/open-telemetry/opentelemetry.io/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22 [google doc]: https://docs.google.com/document/d/1wW0jLldwXN8Nptq2xmgETGbGn9eWP8fitvD5njM-xZY/edit?usp=sharing -[slack]: https://cloud-native.slack.com/archives/C02UN96HZH6 +[slack]: https://slack.cncf.io/ diff --git a/assets/scss/_registry.scss b/assets/scss/_registry.scss index 6d6855dae410..06ed0693de9f 100644 --- a/assets/scss/_registry.scss +++ b/assets/scss/_registry.scss @@ -39,31 +39,3 @@ .registry-entry { @extend .shadow; } - -// fix me: the registry seems not to load the main.min.css with the extended -// styles, so we need to define the styles here again. -.highlight { - margin: 1rem 0; - padding: 0; - position: relative; - max-width: 95%; - border: var(--bs-card-border-width) solid var(--bs-card-border-color); - border-radius: var(--bs-card-border-radius); - & pre { - padding: 1rem; - margin: 0; - display: block; - text-align: right; - overflow-y: auto; - & button.td-click-to-copy { - position: absolute; - color: #ced4da; - border-radius: 3px; - border-width: 0; - background-color: inherit; - box-shadow: 1px 1px #ced4da; - right: 4px; - top: 2px; - } - } -} diff --git a/assets/scss/_styles_project.scss b/assets/scss/_styles_project.scss index bb65387e5f6e..560775b61ae4 100644 --- a/assets/scss/_styles_project.scss +++ b/assets/scss/_styles_project.scss @@ -4,6 +4,7 @@ @import 'registry'; @import 'tabs'; @import 'external_link'; +@import 'td/code-dark'; .td-home { .otel-logo { @@ -135,11 +136,12 @@ width: 100%; position: fixed; margin-left: -15px; - z-index: 32; + z-index: 31; top: 4rem; } - background: $gray-100; + background: var(--td-pre-bg); + color: var(--bs-body-color); text-align: center; & p { diff --git a/content-modules/opamp-spec b/content-modules/opamp-spec index 0360da84c300..950df2967e22 160000 --- a/content-modules/opamp-spec +++ b/content-modules/opamp-spec @@ -1 +1 @@ -Subproject commit 0360da84c3009866b7af702606f7480eb72da6d3 +Subproject commit 950df2967e22526aa553aac1d874ac90b973d140 diff --git a/content-modules/opentelemetry-proto b/content-modules/opentelemetry-proto index 24d4bc002003..b3060d2104df 160000 --- a/content-modules/opentelemetry-proto +++ b/content-modules/opentelemetry-proto @@ -1 +1 @@ -Subproject commit 24d4bc002003c74db7aa608c8e254155daf8e49d +Subproject commit b3060d2104df364136d75a35779e6bd48bac449a diff --git a/content-modules/opentelemetry-specification b/content-modules/opentelemetry-specification index 3985e212f0ef..a7bb6473769d 160000 --- a/content-modules/opentelemetry-specification +++ b/content-modules/opentelemetry-specification @@ -1 +1 @@ -Subproject commit 3985e212f0ef5439daf9b10f0ee490e349c69368 +Subproject commit a7bb6473769d93ddbe063071c94729a242a2cdb2 diff --git a/content/en/_index.md b/content/en/_index.md index 05e045a23de4..12a2ece429a2 100644 --- a/content/en/_index.md +++ b/content/en/_index.md @@ -4,6 +4,9 @@ description: >- High-quality, ubiquitous, and portable telemetry to enable effective observability show_banner: true +outputs: + - HTML + - REDIRECTS # Include this `content/en` ONLY developer_note: The blocks/cover shortcode (used below) will use as a background image any image file containing "background" in its name. diff --git a/content/en/blog/2024/collector-roadmap/can-haz-collector.png b/content/en/blog/2024/collector-roadmap/can-haz-collector.png new file mode 100644 index 000000000000..941e0bc2a925 Binary files /dev/null and b/content/en/blog/2024/collector-roadmap/can-haz-collector.png differ diff --git a/content/en/blog/2024/collector-roadmap/index.md b/content/en/blog/2024/collector-roadmap/index.md new file mode 100644 index 000000000000..3a1d5bafa3ac --- /dev/null +++ b/content/en/blog/2024/collector-roadmap/index.md @@ -0,0 +1,97 @@ +--- +title: The roadmap to v1 for the OpenTelemetry Collector +linkTitle: Collector Roadmap +date: 2024-05-06 +# prettier-ignore +cSpell:ignore: Antipatterns Boten Broadbridge Helmuth Hrabovcak Ishan Jaglowski OTTL Pantuza pushback Shishi Vijay +author: '[Alex Boten](https://github.com/codeboten) (Honeycomb)' +--- + +The [OpenTelemetry Collector](/docs/collector/) is a very popular component in +OpenTelemetry that has been under heavy development for quite some time. It is a +binary that allows many formats of telemetry to be sent to it, transformed, and +emitted to a destination. Much has been said about the Collector over the past +few years in various blog posts and talks. Here's a small list of talks about +the Collector if you haven't had the chance to learn about it: + +- [Connected Observability Pipelines in the OpenTelemetry Collector - Dan Jaglowski](https://www.youtube.com/watch?v=uPpZ23iu6kI) +- [OpenTelemetry Collector Antipatterns - Adriana Villela](/blog/2024/otel-collector-anti-patterns/) +- [Telemetry Showdown: Fluent Bit Vs. OpenTelemetry Collector - Henrik Rexed](https://www.youtube.com/watch?v=ykq1F_3PmJw) +- [OpenTelemetry Collector Deployment Patterns - Juraci Kröhling](https://www.youtube.com/watch?v=WhRrwSHDBFs) +- [OTTL Me Why Transforming Telemetry in the OpenTelemetry Collector Just Got Better - Tyler Helmuth & Evan Bradley](https://www.youtube.com/watch?v=uVs0oUV72CE) +- [Manage OpenTelemetry Collectors at scale with Ansible - Ishan Jain](/blog/2024/scaling-collectors/) + +The Collector has been a core component for organizations looking to adopt +OpenTelemetry as part of their strategy to improve the telemetry emitted by +their systems. Organizations around the world have already adopted it and +successfully process large amounts of data through pipelines as documented by +these various talks: + +- [Adopting OpenTelemetry Collector @ eBay - Swapping Engines Mid Flight - Vijay Samuel](https://www.youtube.com/watch?v=tZJd6W-CIcU) +- [Ingesting 6.5 Tb of Telemetry Data Daily Through OpenTelemetry Protocol and Collectors - Gustavo Pantuza](https://www.youtube.com/watch?v=aDysORX1zIs) +- [Today, Not Tomorrow: Scalable Strategies for Migrating to OpenTelemetry - Jason Anderson & Kevin Broadbridge](https://www.youtube.com/watch?v=iPGd9_aYu-A) +- [How and Why You Should Adopt and Expose OSS Interfaces Like OTel & Prometheus - Daniel Hrabovcak & Shishi Chen](https://www.youtube.com/watch?v=D71fK2MFreI) +- [Why, How to, and Issues: Tail-Based Sampling in the OpenTelemetry Collector - Reese Lee](https://www.youtube.com/watch?v=l4PeclHKl7I) + +A few months ago, there was an +[ask from the community](https://github.com/open-telemetry/community/issues/1971) +to declare the OpenTelemetry Collector stable. + +![Can haz Collector v1?](can-haz-collector.png) + +Now you might be asking yourself "Why would anyone want the Collector to be +declared stable? You just told me it's already used in production!" It's true, +the Collector and its configuration have been fairly stable for core components +for some time. However, being "unofficially stable" is not good enough for a +wide variety of organizations who wish to adopt the Collector: + +- An official v1 will signal that the OpenTelemetry community is ready to + provide long term support and not introduce backwards incompatible changes + without bumping the major version. +- Organizations with policies not to use pre-release software will be able to + start adopting the Collector. +- Stability in the Collector helps the community move OpenTelemetry to become a + CNCF Graduated project. + +The request to stabilize was met with pushback from maintainers since calling +anything 1.0 has a way of setting expectations indefinitely. This led to a +series of discussions and meetings that brought together the maintainers of the +Collector to decide on what a 1.0 really means for the Collector. + +And after a lot of back and forth, we decided on a limited scope of what we +wanted to focus on: + +1. A distribution of the Collector that only includes an OTLP receiver and an + OTLP exporter. +2. Individual Go modules that the Collector components rely upon must also be + marked as stable as per the project's + [versioning guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/VERSIONING.md#public-api-expectations). + +Aside from this, there were a few areas the contributors wanted to improve based +on user feedback: + +- The telemetry generated by the Collector about itself: + - Traces, metrics, and logs must be available via OTLP. + - The configuration for the telemetry must follow the configuration schema. +- The scalability of the Collector: + - Handling for queueing, back pressure, and errors must be improved. + - Clear benchmarks and performance expectations for end users. +- Overall documentation befitting of a stable piece of critical infrastructure. + +The +[roadmap](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/ga-roadmap.md) +was published in the Collector's repository and milestones were created to track +the work underway. To ensure the effort can be successful, the scope of the +deliverable was limited to provide: + +- a clear and achievable goal +- the focus needed to not get distracted +- a signal to new contributors of where the project is focusing + +There is much to do as you can see on the +[project board](https://github.com/orgs/open-telemetry/projects/83), but there +is a lot of excitement around this effort. If you're keen on helping, reach out +either by commenting on any of the open issues in GitHub, or attending the +Collector SIG call that happens weekly on Wednesdays. For a quick overview of +the 1.0 progress you can checkout the tracking +[issue](https://github.com/open-telemetry/opentelemetry-collector/issues/9375). diff --git a/content/en/blog/2024/otel-collector-survey/areas-of-improvement.png b/content/en/blog/2024/otel-collector-survey/areas-of-improvement.png new file mode 100644 index 000000000000..80741de2dae9 Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/areas-of-improvement.png differ diff --git a/content/en/blog/2024/otel-collector-survey/deployment-environment.png b/content/en/blog/2024/otel-collector-survey/deployment-environment.png new file mode 100644 index 000000000000..81f9834e3689 Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/deployment-environment.png differ diff --git a/content/en/blog/2024/otel-collector-survey/deployment-scale.png b/content/en/blog/2024/otel-collector-survey/deployment-scale.png new file mode 100644 index 000000000000..31447ed77c58 Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/deployment-scale.png differ diff --git a/content/en/blog/2024/otel-collector-survey/index.md b/content/en/blog/2024/otel-collector-survey/index.md new file mode 100644 index 000000000000..77184375f8ec --- /dev/null +++ b/content/en/blog/2024/otel-collector-survey/index.md @@ -0,0 +1,163 @@ +--- +title: Insights from the OpenTelemetry Collector Survey +linkTitle: OpenTelemetry Collector Survey +date: 2024-05-08 +author: '[Hope Oluwalolope](https://github.com/iamebonyhope) (Microsoft)' +# prettier-ignore +cSpell:ignore: attributesprocessor basicauthextension batchprocessor bearertokenauthextension clientauthextension countconnector customizability datadogconnector debugexporter distros filelogreceiver filterprocessor healthcheckextension hostmetricsreceiver k8sattributesprocessor lokiexporter memorylimiterprocessor Oluwalolope otlpexporter otlpreceiver Pprof pprofextension prometheusexporter prometheusreceiver prometheusremotewriteexporter routingconnector sclusterreceiver Servicegraph servicegraphconnector spanmetricsconnector +--- + +The [OpenTelemetry (OTel) Collector](/docs/collector/) has become a cornerstone +tool for observing and monitoring modern software applications. Recently, the +End User SIG conducted a survey to gather feedback from users about their +experiences with the OTel Collector. While we acknowledge that the 186 responses +we received may not be statistically significant, they represent a great start +and provide valuable insights. These insights include details about users’ +deployment practices and implementation challenges, which are instrumental in +helping to drive the OTel Collector’s future direction. + +## Key Takeaways + +- Companies typically have medium to large collector deployments: + - \>5 Collectors: 125/186 + - \>10 Collectors: 100/186 +- Building custom binaries/distributions of the Collector is more popular than + expected (61/186), with most people using the + [OTel Collector Builder](https://github.com/open-telemetry/opentelemetry-collector-builder) + to do so (49/61) +- The vast majority deploy the Collector on Kubernetes (150/186) +- There's more desire for stability (59), self-observability (53), and config + management (59), than for new components (14) + +## Detailed Insights + +### Deployment Scale and Environment + +Our findings indicate robust use of the OTel Collector at scale, with +53.8%(100/186) of respondents deploying more than 10 collectors, 13.4%(25/186) +running between 5 and 10 collectors, and 22%(41/186) running between 2 and 5 +collectors. + +![Chart showing how many otel collectors people run in their organization](deployment-scale.png) + +Kubernetes is the leading platform for Collector deployment (80.6%), followed by +virtual machines (33.3%) and bare metal (10.8%). + +![Chart showing where people deploy their otel collectors](deployment-environment.png) + +### Usage Scenarios + +The OTel Collector is primarily used as a gateway (64.5%), demonstrating its +pivotal role in aggregating telemetry data from various sources. Daemonsets +(51.6%) and sidecars (23.7%) are also popular deployment models, showcasing the +flexibility of the OTel Collector in different operational contexts. + +![Chart showing the usage scenarios of the otel collector](usage-scenarios.png) + +### Customization and Configuration + +A surprising number of people build their own distributions of the Collector +(61/186), indicating that providing a composable Collector is important for the +community. Most people who do build their own Collector distros use the +[OTel Collector Builder (OCB)](https://github.com/open-telemetry/opentelemetry-collector-builder) +(49/61). Of the 49 respondents who leverage the OCB, most were able to figure it +out, with only 2 respondents stating that it’s too hard to use. + +![Chart showing how easy people find it to use the otel collector builder](ocb-usage.png) + +### Monitoring and Observability + +When it comes to monitoring the Collectors, a vast majority of respondents rely +on Collector metrics and logs (81.7%), and only a few don't monitor their +Collector(s) at all (16.6%). When we peered deeper into the data, we found that +of the 125 respondents with more than 5 Collectors, only 15 are not monitoring +their Collectors, and of the 100 respondents with more than 10 Collectors, only +9 are not monitoring their Collectors. This seems to indicate that users take +monitoring their Collectors seriously once they reach a certain maturity with +their Collector deployments. + +![Chart showing how people monitor their otel collector](monitoring.png) + +### OTel Components Usage + +The OTel Collector's flexibility is vividly illustrated by the wide array of +exporters, receivers, processors, connectors, and extensions that are used +across various environments. This highlights the Collector's capability to +integrate with a vast range of tools and systems. + +The top components according to our survey results are as follows: + +### Exporters + +1. [otlpexporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/otlpexporter) +2. [prometheusremotewriteexporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/prometheusremotewriteexporter/README.md) +3. [prometheusexporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/prometheusexporter/README.md) +4. [lokiexporter](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/lokiexporter/README.md) +5. [debugexporter](https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/debugexporter) + +### Receivers + +1. [otlpreceiver](https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/otlpreceiver) +2. [prometheusreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/prometheusreceiver/README.md) +3. [filelogreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver) +4. [hostmetricsreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/hostmetricsreceiver/README.md) +5. [k8sclusterreceiver](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/receiver/k8sclusterreceiver/README.md) + +### Processors + +1. [batchprocessor](https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/batchprocessor) +2. [attributesprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/attributesprocessor/README.md) +3. [filterprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/filterprocessor/README.md) +4. [memorylimiterprocessor](https://github.com/open-telemetry/opentelemetry-collector/tree/main/processor/memorylimiterprocessor) +5. [k8sattributesprocessor](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/k8sattributesprocessor/README.md) + +### Connectors + +1. [spanmetricsconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/spanmetricsprocessor/README.md) +2. [servicegraphconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/servicegraphprocessor/README.md) +3. [routingconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/processor/routingprocessor/README.md) +4. [countconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/countprocessor/README.md) +5. [datadogconnector](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/datadogexporter/README.md) + +### Extensions + +1. [healthcheckextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/healthcheckextension/README.md) +2. [basicauthextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/basicauthextension/README.md) +3. [pprofextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/pprofextension/README.md) +4. [bearertokenauthextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/bearertokenauthextension/README.md) +5. [oauth2clientauthextension](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/extension/oauth2clientauthextension/README.md) + +
+ +For a more detailed look at the specific exporters, receivers, processors, +connectors, and extensions in use, you can check out the +[raw results](https://github.com/open-telemetry/sig-end-user/blob/main/end-user-surveys/otel-collector/otel-collector-survey.csv). +The data provides a clear view of the popular choices within the community as +well as the niche configurations that exemplify the customizability of the OTel +Collector. + +### Areas for Improvement + +Respondents were clear about their desire for enhancements in stability (30.6%), +configuration management and resolution (30.1%), and self-observability (28%), +versus wanting new components (<8%) + +![Chart showing interested areas of improvement for the otel collector](areas-of-improvement.png) + +The +[OTel Collector survey results](https://github.com/open-telemetry/sig-end-user/blob/main/end-user-surveys/otel-collector/otel-collector-survey.csv) +offer a snapshot of the current state of Collector deployment and utilization. +It's evident that while the OTel Collector is widely adopted and highly +customizable, there are also opportunities to make it more user-friendly and +robust. + +## Keep in touch + +Thanks to everyone who participated in the survey! We rely on your feedback to +help guide the future development of OpenTelemetry and to ensure it continues to +meet your evolving needs. + +We will post upcoming surveys in the following avenues: +[#otel-sig-end-user Slack channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ) +– you can also reach out to us here! +[End user resources page](/community/end-user/) diff --git a/content/en/blog/2024/otel-collector-survey/monitoring.png b/content/en/blog/2024/otel-collector-survey/monitoring.png new file mode 100644 index 000000000000..f96529100c9c Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/monitoring.png differ diff --git a/content/en/blog/2024/otel-collector-survey/ocb-usage.png b/content/en/blog/2024/otel-collector-survey/ocb-usage.png new file mode 100644 index 000000000000..08a35f95e374 Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/ocb-usage.png differ diff --git a/content/en/blog/2024/otel-collector-survey/usage-scenarios.png b/content/en/blog/2024/otel-collector-survey/usage-scenarios.png new file mode 100644 index 000000000000..a7d8a12eeb0d Binary files /dev/null and b/content/en/blog/2024/otel-collector-survey/usage-scenarios.png differ diff --git a/content/en/blog/2024/otel-errors/OTel-spans.png b/content/en/blog/2024/otel-errors/OTel-spans.png new file mode 100644 index 000000000000..3f5deb54faf7 Binary files /dev/null and b/content/en/blog/2024/otel-errors/OTel-spans.png differ diff --git a/content/en/blog/2024/otel-errors/index.md b/content/en/blog/2024/otel-errors/index.md new file mode 100644 index 000000000000..e7043078b654 --- /dev/null +++ b/content/en/blog/2024/otel-errors/index.md @@ -0,0 +1,293 @@ +--- +title: Dude, where's my error? How OpenTelemetry records errors +linkTitle: Understanding OTel Errors +date: 2024-04-19 +author: >- + [Reese Lee](https://github.com/reese-lee) (New Relic), [Adriana + Villela](https://github.com/avillela) (ServiceNow) +cSpell:ignore: Dalle +canonical_url: https://newrelic.com/blog/how-to-relic/dude-wheres-my-error +--- + +![A confused penguin trying to learn about errors and exceptions. Image generated with AI using Dalle3 via Bing Copilot](penguin-chalkboard.jpg) + +Depending on the language you’re used to developing in, you may have certain +ideas about what an error is, as well as what constitutes an exception and how +it should be handled. For example, Go doesn't have exceptions, partly to +discourage programmers from labeling too many ordinary errors as exceptional. On +the other hand, languages such as Java and Python provide built-in support for +throwing and catching exceptions. + +When different languages disagree about what errors or exceptions are and how to +handle them, what do you use when you need standardized telemetry and error +reporting across microservices written in those languages? OpenTelemetry is the +tool with which we'll address the following, and more: + +- How an error is visualized in a backend might not be where you think it’ll be, + or how you expect it to look. +- How span kind affects error reporting. +- Errors reported by spans versus logs. + +## Errors versus exceptions + +Before we get into how OTel deals with errors and exceptions, let’s establish +what they are, and how they differ from each other. While there are variations +on the definitions of these terms, we’ve landed on the following ones, which +we’ll be using in this article. Note that this is **not** official OTel +language; they are general industry definitions: + +An **error** is an unexpected issue in a program that hinders its execution. +Examples include syntax errors, such as a missing semicolon or incorrect +indentation, and runtime errors, resulting from errors in logic. + +An **exception** is a type of runtime error that disrupts the normal flow of a +program. Examples include dividing by zero or accessing an invalid memory +address. + +Some languages, such as Python and JavaScript, treat errors and exceptions as +synonyms; others, such as PHP and Java, do not. Understanding the distinction +between errors and exceptions is crucial for effective error handling, because +it empowers you to adopt more nuanced strategies for handling and recovering +from failures in your applications. + +## Handling errors in OTel + +So how does OTel deal with all these conceptual differences across languages? +This is where the [specification](/docs/specs/otel/) (or “spec” for short) comes +in. The spec provides a blueprint for developers working on various parts of the +project, and standardizes implementation across all languages. + +Since language APIs and SDKs are implementations of the spec, there are general +rules against implementing anything that isn’t covered in the spec. This +provides a guiding principle to help organize contributions to the project. In +practice, there are a few exceptions; for example, a language might prototype a +new feature as part of adding it to the spec, but the feature may be published +(usually as alpha or experimental) before the corresponding language is added. + +Another exception is when a language might decide to diverge from the spec. +Although it is generally not advised, sometimes there are strong +language-specific reasons to do something different. In this way, the spec +allows for some flexibility for each language to implement features as +idiomatically as possible. For example, most languages have implemented +`RecordException` (for example, +[Python](https://opentelemetry-python.readthedocs.io/en/latest/_modules/opentelemetry/sdk/trace.html#Span.record_exception)), +while Go has implemented +[`RecordError`](https://github.com/open-telemetry/opentelemetry-go/blob/main/sdk/trace/span.go), +which does the same thing. + +You can view this +[compliance matrix](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md) +of the spec across all languages, but you’ll get the most updated info by +checking the individual language repository. Now we can begin figuring out how +to handle errors in OTel, starting with how to report them: + +- Spans +- Logs + +### Errors in spans + +In OTel, spans are the building blocks of distributed traces, representing +individual units of work within a distributed system. Spans are related to each +other and to a trace through context. Put simply, context is the glue that turns +a pack of data into a unified trace. Context propagation allows us to pass +information across multiple systems, therefore tying them together. Traces can +tell us all sorts of things about our applications through metadata and span +events. + +![Graphic that shows the spans within a trace](OTel-spans.png) + +### Enhancing spans with metadata + +OTel enables you to enhance spans with metadata +([attributes](/docs/concepts/signals/traces/#attributes)) in the form of +key-value pairs. By attaching relevant information to spans, such as user IDs, +request parameters, or environment variables, you can gain deeper insights into +the circumstances surrounding an error and quickly identify its root cause. This +metadata-rich approach to error handling can significantly reduce the time and +effort required to diagnose and resolve issues, ultimately improving the +reliability and maintainability of your applications. + +Spans also have a [span kind](/docs/concepts/signals/traces/#span-kind) field, +which gives us some additional metadata that can help developers troubleshoot +errors. OTel defines several span kinds, each of which has unique implications +for error reporting: + +- **client**: For outgoing synchronous remote calls (for example, outgoing HTTP + request or DB call) +- **server**: For incoming synchronous remote calls (for example, incoming HTTP + request or remote procedure call) +- **internal**: For operations that do not cross process boundaries (for + example, instrumenting a function call) +- **producer**: For the creation of a job which may be asynchronously processed + later (for example, job inserted into a job queue) +- **consumer**: For the processing of a job created by a producer, which may + start long after the producer span has ended + +Span kind is determined automatically by the instrumentation libraries used. + +Spans can be further enhanced with +[span status](/docs/concepts/signals/traces/#span-status). By default, span +status is marked as `Unset` unless otherwise specified. You can mark a span +status as `Error` if the resulting span depicts an error, and `Ok` if the +resulting span is error-free. + +### Enhancing spans with span events + +A [span event](/docs/concepts/signals/traces/#span-events) is a structured log +message embedded within a span. Span events help enhance spans by providing +descriptive information about a span. +[Span events can also have attributes of their own](/docs/languages/ruby/instrumentation/#add-span-events). + +When a span status is set to `Error`, a span event is created automatically, +capturing the span’s resulting error message and stack trace as an event on that +span. You can further enhance this span error by adding attributes to it. + +Earlier, we mentioned a method called `RecordException`. Per +[the spec](/docs/specs/otel/trace/api/#record-exception) (emphasis our own), “To +facilitate recording an exception languages SHOULD provide a RecordException +method **if the language uses exceptions**… The signature of the method is to be +determined by each language and can be overloaded as appropriate.” + +Since Go doesn’t support the “conventional” concept of exceptions, it instead +supports +[`RecordError`](https://github.com/open-telemetry/opentelemetry-go/blob/main/sdk/trace/span.go#L445-L467), +which essentially does the same thing idiomatically. You have to make an +additional call to set its status to `Error` if that’s what it should be, as it +won’t automatically be set to that. Similarly, `RecordException` can be used to +record span events without setting the span’s status to `Error`, which means you +can use it to record any additional data about a span. + +By decoupling the span status from being automatically set to `Error` when a +span exception occurs, you can support the use case where you can have an +exception event with a status of `Ok` or `Unset`. This gives instrumentation +authors the most flexibility. + +### Errors in logs + +In OTel, a log is a structured, timestamped message emitted by a service or +other component. The recent addition of logs to OTel gives us yet another way of +reporting errors. Logs have traditionally had different severity levels for +representing the type of message being emitted such as `DEBUG`, `INFO`, +`WARNING`, `ERROR`, and `CRITICAL`. + +OTel allows for the correlation of logs to traces, in which a log message can be +associated to a span within a trace, via trace context correlation. Hence, +looking for a log message with a log level of `ERROR` or `CRITICAL` can yield +further information of what led to that error, by pulling up the correlated +trace. + +To record an error on a log, either `exception.type` or `exception.message` is +required, while `exception.stacktrace` is recommended. For more information, see +[Semantic Conventions for Exceptions in Logs](/docs/specs/semconv/exceptions/exceptions-logs/). + +## Logs or spans to capture errors? + +After all this, you might be wondering which signal to use to capture errors: +spans or logs? The answer is: "It depends!" Perhaps your team primarily uses +traces; perhaps it primarily uses logs. + +Spans can be great for capturing errors, because if the operation errors out, +marking a span as an error makes it stand out and therefore easier to spot. On +the other hand, if you’re not filtering or tail sampling your traces and your +system is producing thousands of spans per minute, you could miss errors that +aren’t occurring frequently, but that still need to be handled. + +What about using span events versus logs? Again, this depends. It may be +convenient to use span events, because when a span status is set to `Error`, a +span event with the exception message (and other metadata you may wish to +capture) is automatically created. + +Another consideration is your observability backend. Does your backend render +both logs and traces? How easily queryable or discoverable are your logs, spans, +and span events? Is logs and trace correlation supported? + +## Visualizing errors in different backends + +While OTel provides us with the raw telemetry data emitted by our systems, it +doesn’t provide data visualization or interpretation. This is done by an +observability backend. Because OTel is vendor-neutral, it means that the same +information emitted can be visualized and interpreted by different backends +without re-instrumenting your application. + +### Jaeger + +Let’s take a look at what an OTel error looks like in +[Jaeger](https://www.jaegertracing.io/). The error data was generated by the +code in [this repository](https://github.com/avillela/otel-errors-talk). Here is +a trace view for the service +[py-otel-server](https://github.com/avillela/otel-errors-talk/blob/main/src/python/server.py). +As you can see below, the error spans show up as red dots: + +![List of traces in the Jaeger UI](jaeger-high-level-view.png) + +And if we drill down and zero in on the error span, we can click into `Logs`, +which is how span events are expressed in Jaeger, and view the information that +was captured on it: + +![Attributes and other metadata for an error span in Jaeger](jaeger-error.png) + +The span is clearly marked as error, and includes a span event with the +exception captured. Jaeger expresses the span event as a log, but does not +visualize logs outside of spans. + +### Proprietary backends + +If you’ve been using a proprietary agent to monitor your applications and have +recently migrated to OTel, you might notice that an OTel error may not be +expressed the way you expect in your observability backend, as compared to the +same error captured by the proprietary agent. This is most likely due to the +fact that OTel simply models errors differently than how vendors have been +modeling them. + +As a broad example, vendors might have their own notion of what constitutes a +logical unit of work in an application. You may be familiar with the term +`transaction`, which means something slightly different from vendor to vendor. +In OTel, this is represented by a trace. You’ve likely noticed differences in +your data visualization experiences as vendors make their own adjustments to +their platforms to accommodate OTLP as a first-class citizen data type. + +As a more specific example, OTel’s notion of span kinds may affect how your OTel +error is expressed in your backend. For instance, if you have a trace that has +one exception and it’s on an internal span with its status set to `Error`, you +should see the trace marked with an error, but it may not be counted toward your +overall app error rate. This is because the vendor might have an opinion that +only errors on entry point spans (server spans) and consumer spans should be +counted toward your error rate. + +If your backend supports trace and log correlation, you should be able to +navigate to the associated trace from the log, and vice versa. Furthermore, +while Jaeger visualizes span events as logs, some vendors might synthesize span +events as its own data type instead of as a log data type, which would impact +the way you query that data. + +## Conclusion + +We’ve just explored the challenges of handling errors and exceptions across +different programming languages within a microservices architecture, and +introduced OTel as a solution for standardized telemetry and error reporting. +The OTel specification serves as a blueprint for standardizing error handling +across various languages, providing guidelines for implementation, but allowing +for a degree of flexibility. + +You can record errors on spans by making use of your language SDK’s +`RecordException` or its equivalent, and enrich the span events further by +adding custom attributes. You can also record errors on logs by adding +`exception.type` or `exception.message`, and capture the stack trace by adding +`exception.stacktrace` to yield further information about what happened. + +Once that data is in your observability backend, if you have previously used +their proprietary monitoring agent, you might notice that there is a difference +in how OTel-instrumented errors are visualized versus how the agent-instrumented +errors were visualized. This is mainly because OTel models errors differently +than vendors might have previously done. + +By leveraging OTel's capabilities to record errors through logs and spans and to +enhance them with metadata, you can gain deeper insights into your applications' +behavior and more effectively troubleshoot issues. You'll be better equipped to +build and maintain resilient, reliable, and high-performing software +applications in today's dynamic and demanding environments. To learn more, see +[Error handling in OpenTelemetry](/docs/specs/otel/error-handling/). + +_A version of this article was +[originally posted](https://newrelic.com/blog/how-to-relic/dude-wheres-my-error) +on the New Relic blog._ diff --git a/content/en/blog/2024/otel-errors/jaeger-error.png b/content/en/blog/2024/otel-errors/jaeger-error.png new file mode 100644 index 000000000000..e2364f02b5ba Binary files /dev/null and b/content/en/blog/2024/otel-errors/jaeger-error.png differ diff --git a/content/en/blog/2024/otel-errors/jaeger-high-level-view.png b/content/en/blog/2024/otel-errors/jaeger-high-level-view.png new file mode 100644 index 000000000000..fe92c1f1a53d Binary files /dev/null and b/content/en/blog/2024/otel-errors/jaeger-high-level-view.png differ diff --git a/content/en/blog/2024/otel-errors/penguin-chalkboard.jpg b/content/en/blog/2024/otel-errors/penguin-chalkboard.jpg new file mode 100644 index 000000000000..10745aa6a2c2 Binary files /dev/null and b/content/en/blog/2024/otel-errors/penguin-chalkboard.jpg differ diff --git a/content/en/blog/2024/otel-operator-q-and-a/index.md b/content/en/blog/2024/otel-operator-q-and-a/index.md new file mode 100644 index 000000000000..209b21a4d6fc --- /dev/null +++ b/content/en/blog/2024/otel-operator-q-and-a/index.md @@ -0,0 +1,353 @@ +--- +title: + Things You Might Not Have Known About the OpenTelemetry Operator - An OTel + Operator Q&A +linkTitle: OTel Operator Q&A +date: 2024-05-13 +author: >- + [Adriana Villela](https://github.com/avillela) (ServiceNow), + +canonical_url: https://adri-v.medium.com/81d63addbf92? +cSpell:ignore: automagically mycollector +--- + +![Seattle's Mount Rainier rising about the clouds, as seen from an airplane. Photo by Adriana Villela](mount-rainier.jpg) + +The +[OpenTelemetry (OTel) Operator](https://github.com/open-telemetry/opentelemetry-operator) +is a +[Kubernetes Operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) +that manages OTel for you in your Kubernetes cluster to make life a little +easier. It does the following: + +- Manages deployment of the + [OpenTelemetry Collector](http://localhost:1313/docs/collector/), supported by + the + [`OpenTelemetryCollector`](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#getting-started) + [custom resource (CR)](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). +- Manages the configuration of a fleet of OpenTelemetry Collectors via + [OpAMP](/docs/specs/opamp/) integration, supported by the + [`OpAMPBridge`](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api.md#opampbridge) + custom resource. +- Provides + [integration with the Prometheus Operator's `PodMonitor` and `ServiceMonitor` CRs](https://github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator). +- Injects and configures + [auto-instrumentation](https://www.honeycomb.io/blog/what-is-auto-instrumentation) + into your pods, supported by the + [`Instrumentation`](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#opentelemetry-auto-instrumentation-injection) + custom resource. + +I've had a chance to use the Operator in the last year, and learned some pretty +cool things, so I thought it might be helpful to share some little OTel Operator +goodies that I’ve picked up along the way, in the form of a Q&A. + +Please note that this post assumes that you have some familiarity with +OpenTelemetry, the +[OpenTelemetry Collector](http://localhost:1313/docs/collector/), the +[OpenTelemetry Operator](https://github.com/open-telemetry/opentelemetry-operator) +(including the +[Target Allocator](https://adri-v.medium.com/prometheus-opentelemetry-better-together-41dc637f2292)), +and [Kubernetes](https://kubernetes.io). + +## Q&A + +### Q1: Does the Operator support multiple Collector configuration sources? + +Short answer: No. + +Longer answer: OTel Collector can be fed more than one Collector config YAML +file. That way, you can keep your base configurations in, say, +`otelcol-config.yaml`, and overrides or additions to the base configuration can +go in, for example, `otelcol-config-extras.yaml`. See an example of this in the +[OTel Demo’s Docker compose file](https://github.com/open-telemetry/opentelemetry-demo/blob/06f020c97f78ae9625d3a4a5d1107c55045c567f/docker-compose.yml#L665-L668). + +Unfortunately, while the OTel Collector supports multiple Collector +configuration files, the Collector managed by the OTel Operator does not. + +To get around this, you could merge the multiple Collector configs through some +external tool beforehand. For example, if you +[were deploying the Operator via Helm](https://github.com/open-telemetry/opentelemetry-helm-charts/tree/main/charts/opentelemetry-operator), +you could technically +[pass it multiple Collector config files using multiple --values flags](https://stackoverflow.com/a/56653384) +and let [Helm](https://helm.sh) do the merging for you. + +> **NOTE:** There are plans to offer higher-level constructs for specifying +> configurations in the future, as per +> [this PR](https://github.com/open-telemetry/opentelemetry-operator/issues/1906). + +For reference, +[check out this thread in the #otel-operator CNCF Slack channel](https://cloud-native.slack.com/archives/C033BJ8BASU/p1709321896612279). + +### Q2: How can I securely reference access tokens in the Collector's configuration? + +In order to send OpenTelemetry data to an observability backend, you must define +at least one [exporter](/docs/collector/configuration/#exporters). Whether you +use [OTLP](/docs/specs/otel/protocol/) or +[some proprietary vendor format](/docs/specs/otel/protocol/), most exporters +typically require that you specify an endpoint and an access token when sending +data to a vendor backend. + +When using the OpenTelemetry Operator to manage the OTel Collector, the OTel +Collector config YAML is defined in the +[OpenTelemetryCollector](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#getting-started) +CR. This file should be version-controlled and therefore shouldn’t contain any +sensitive data, including access tokens stored as plain text. + +Fortunately, the `OpenTelemetryCollector` CR gives us a way to reference that +value as a secret. Here’s how you do it: + +1- Create a Kubernetes secret for your access token. Remember to +[base-64 encode](https://www.base64encode.org/) the secret. + +2- +[Expose the secret as an environment variable](https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret) +by adding it to the `OpenTelemetryCollector` CR’s +[`env` section](https://github.com/avillela/otel-target-allocator-talk/blob/21e9643e28165e39bd79f3beec7f2b1f989d87e9/src/resources/02-otel-collector-ls.yml#L16-L21). +For example: + +```yaml +env: + - name: TOKEN_VALUE + valueFrom: + secretKeyRef: + key: TOKEN_VALUE + name: otel-collector-secret +``` + +3- Reference the environment variable in your +[exporter definition](https://github.com/avillela/otel-target-allocator-talk/blob/21e9643e28165e39bd79f3beec7f2b1f989d87e9/src/resources/02-otel-collector-ls.yml#L43-L47): + +```yaml +exporters: + otlp: + endpoint: '' + headers: + '': '${TOKEN_VALUE}' +``` + +For more info, see the +[full example](https://github.com/avillela/otel-target-allocator-talk/blob/main/src/resources/02-otel-collector-ls.yml), +along with the +[instructions](https://github.com/avillela/otel-target-allocator-talk/tree/main?tab=readme-ov-file#3b--kubernetes-deployment-servicenow-cloud-observability-backend). + +### Q3: Is the Operator version at parity with the Collector version? + +For every Collector release, there is an Operator release which provides support +for that Collector version. For example, at the time of this writing, the latest +Operator version is 0.98.0. Thus, the the default image of the Collector used by +the Operator is version 0.98.0 of the +[core distribution](/blog/2024/otel-collector-anti-patterns/#3--not-using-the-right-collector-distribution-or-not-building-your-own-distribution) +(as opposed to the contrib distribution). + +### Q4: Can I override the base OTel Collector image? + +Yes! In fact, +[you probably should](https://cloud-native.slack.com/archives/C033BJ8BASU/p1713894678225579)! + +As we saw earlier, the +[core distribution](https://github.cm/open-telemetry/open-telemetry-collector) +is the default Collector distribution used by the `OpenTelemetryCollector` CR. +The Core distribution is a bare-bones distribution of the Collector for OTel +developers to develop and test. It contains a base set of components–i.e. +[extensions](/docs/collector/configuration/#service-extensions), +[connectors](/docs/collector/configuration/#connectors), +[receivers](/docs/collector/configuration/#receivers), +[processors](/docs/collector/configuration/#processors), and +[exporters](/docs/collector/configuration/#exporters). + +If you want access to more components than the ones offered by core, you can use +the Collector's +[Kubernetes Distribution](https://github.com/open-telemetry/opentelemetry-collector-releases/tree/main/distributions/otelcol-k8s) +instead. This distribution is made specifically to be used in a Kubernetes +cluster to monitor Kubernetes and services running in Kubernetes. It contains a +subset of components from +[OpenTelemetry Collector Core](https://github.com/open-telemetry/opentelemetry-collector) +and +[OpenTelemetry Collector Contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). + +If you want to use your own specific Collector components, you can build your +own distribution using the +[OpenTelemetry Collector Builder](/docs/collector/custom-collector/) (OCB), and +include only the components that you need. + +Either way, the OpenTelemetryCollector CR allows you to override the default +Collector image with one that better suits your needs by `adding spec.image` to +your `OpenTelemetryCollector` YAML. In addition, you can also specify the number +of Collector replicas by adding `spec.replicas`. This is totally independent of +whether or not you override the Collector image. + +Your code would look something like this: + +```yaml +apiVersion: opentelemetry.io/v1alpha1 +kind: OpenTelemetryCollector +metadata: + name: otelcol + namespace: mynamespace +spec: + mode: statefulset + image: + replicas: +``` + +Where: + +- `` is the name of a valid Collector image from a container + repository +- `` is the number of pod instances for the underlying + OpenTelemetry Collector + +Keep in mind that if you're pulling a Collector image from a private container +registry, you'll need to use +[`imagePullSecrets`](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/). +Since private container registries require authentication, this will enable you +to authenticate against that private registry. For more info on how to use +`imagePullSecrets` for your Collector image, see +[the instructions](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#using-imagepullsecrets). + +For more info, check out the +[OpenTelemetryCollector CR API docs](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api.md#opentelemetrycollector). + +### Q5: Does the Target Allocator work for all deployment types? + +No. The Target Allocator only works for +[StatefulSet](https://kubernetes.io/docs/concepts/workloads/controllers/statefulset/), +and +[DaemonSet](https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/) +([newly-introduced](https://github.com/open-telemetry/opentelemetry-operator/pull/2430#discussion_r1420495631)). +For more info, see +[`collector_webhook.go`](https://github.com/open-telemetry/opentelemetry-operator/blob/aed905c2c3c0aa3fb608a79c2e4d0e7b73dff980/apis/v1beta1/collector_webhook.go#L328). + +### Q6: If I enable `prometheusCR` in the Target Allocator, do I need the `PodMonitor` and `ServiceMonitor` CRs installed in my Kubernetes cluster? + +Yes, you do. These CRs are bundled with the +[Prometheus Operator](https://github.com/prometheus-operator/prometheus-operator); +however, they can be installed standalone, which means that you don’t need to +install the Prometheus Operator just to use these two CRs with the Target +Allocator. + +The easiest way to install the +[`PodMonitor`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#monitoring.coreos.com/v1.PodMonitor) +and +[`ServiceMonitor`](https://github.com/prometheus-operator/prometheus-operator/blob/main/Documentation/api.md#monitoring.coreos.com/v1.ServiceMonitor) +CRs is to grab a copy of the individual +[PodMonitor YAML](https://github.com/prometheus-community/helm-charts/blob/main/charts/kube-prometheus-stack/charts/crds/crds/crd-podmonitors.yaml) +and +[ServiceMonitor YAML](https://github.com/prometheus-community/helm-charts/blob/main/charts/kube-prometheus-stack/charts/crds/crds/crd-servicemonitors.yaml) +[custom resource definitions (CRDs)](https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/), +like this: + +```shell +kubectl --context kind-otel-target-allocator-talk apply -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/example/prometheus-operator-crd/monitoring.coreos.com_servicemonitors.yaml + +kubectl --context kind-otel-target-allocator-talk apply -f https://raw.githubusercontent.com/prometheus-operator/prometheus-operator/main/example/prometheus-operator-crd/monitoring.coreos.com_podmonitors.yaml +``` + +See my +[example of the OpenTelemetry Operator’s Target Allocator with `ServiceMonitor`](https://github.com/avillela/otel-target-allocator-talk/tree/main?tab=readme-ov-file#3b--kubernetes-deployment-servicenow-cloud-observability-backend). + +### Q7: Do I need to create a service account to use the Target Allocator? + +No, but you do need to do a bit of extra work. So, here’s the deal…although you +need a +[service account](https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/) +to use the Target Allocator, you don’t have to create your own. + +If you enable the Target Allocator and don’t create a service account, one is +automagically created for you. This service account’s default name is a +concatenation of the Collector name (`metadata.name` in the +`OpenTelemetryCollector` CR) and `-collector`. For example, if your Collector is +called `mycollector`, then your service account would be called +`mycollector-collector`. + +By default, this service account has no defined policy. This means that you’ll +still need to create your own +[`ClusterRole`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole) +and +[`ClusterRoleBinding`](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding), +and associate the `ClusterRole` to the `ServiceAccount` via +`ClusterRoleBinding`. + +See the +[Target Allocator readme](https://github.com/open-telemetry/opentelemetry-operator/tree/main/cmd/otel-allocator#rbac) +for more on Target Allocator RBAC configuration. + +> **NOTE:** This will be automated fully in the near future (see accompanying +> [PR](https://github.com/open-telemetry/opentelemetry-operator/pull/2787)), as +> part of version `0.100.0`. + +### Q8: Can I override the Target Allocator base image? + +Just like you can override the Collector base image in the +`OpenTelemetryCollector` CR, you can also override the Target Allocator base +image. + +Please keep in mind that +[it’s usually best to keep the Target Allocator and OTel operator versions the same](https://cloud-native.slack.com/archives/C033BJ8BASU/p1709128862949249?thread_ts=1709081221.484429&cid=C033BJ8BASU), +to avoid any compatibility issues. If do you choose to override the Target +Allocator’s base image, you can do so by adding `spec.targetAllocator.image` in +the `OpenTelemetryCollector` CR. You can also specify the number of replicas by +adding `spec.targetAllocator.replicas`. This is totally independent of whether +or not you override the TA image. + +Your code would look something like this: + +```yaml +apiVersion: opentelemetry.io/v1alpha1 +kind: OpenTelemetryCollector +metadata: + name: otelcol + namespace: mynamespace +spec: + mode: statefulset + targetAllocator: + image: + replicas: +``` + +Where: + +- `` is a valid Target Allocator image from a container + repository. +- `` is the number of pod instances for the underlying + Target Allocator + +### Q9: If it’s not recommended that you override the Target Allocator base image, then why would you want to? + +One use case might be +[if you need to host a mirror of the Target Allocator image in your own private container registry for security purposes](https://cloud-native.slack.com/archives/C033BJ8BASU/p1713894678225579). + +If you do need to reference a Target Allocator image from a private registry, +you’ll need to use `imagePullSecrets`. For details, see +[the instructions](https://github.com/open-telemetry/opentelemetry-operator?tab=readme-ov-file#using-imagepullsecrets). +Note that you don’t need to create a `serviceAccount` for the Target Allocator, +since once is already created for you automagically if you don’t create one +yourself (see +[Q7](#q7-do-i-need-to-create-a-service-account-to-use-the-target-allocator)). + +For more info, check out the +[Target Allocator API docs](https://github.com/open-telemetry/opentelemetry-operator/blob/main/docs/api.md#opentelemetrycollectorspectargetallocator). + +### Q10: Is there a version lag between the OTel Operator auto-instrumentation and auto-instrumentation of supported languages? + +If there is a lag, it's minimal, as maintainers try to keep these up to date for +each release cycle. Keep in mind that there are breaking changes in some +semantic conventions and the team is trying to avoid breaking users' code. For +details, see this +[`#otel-operator` thread](https://cloud-native.slack.com/archives/C033BJ8BASU/p1713894678225579). + +## Final thoughts + +Hopefully this has helped to demystify the OTel Operator a bit more. There’s +definitely a lot going on, and the OTel Operator can certainly be a bit scary at +first, but understanding some of the basics will get you well on your way to +mastering this powerful tool. + +If you have any questions about the OTel Operator, I highly recommend that you +post questions on the +[#otel-operator](https://cloud-native.slack.com/archives/C033BJ8BASU) channel on +the [CNCF Slack](https://communityinviter.com/apps/cloud-native/cncf). +Maintainers and contributors are super friendly, and have always been more than +willing to answer my questions! You can also +[hit me up](https://bento.me/adrianamvillela), and I'll try my best to answer +your questions, or to direct you to folks who have the answers! diff --git a/content/en/blog/2024/otel-operator-q-and-a/mount-rainier.jpg b/content/en/blog/2024/otel-operator-q-and-a/mount-rainier.jpg new file mode 100644 index 000000000000..8230b5ce09f6 Binary files /dev/null and b/content/en/blog/2024/otel-operator-q-and-a/mount-rainier.jpg differ diff --git a/content/en/blog/2024/scaling-collectors.md b/content/en/blog/2024/scaling-collectors.md new file mode 100644 index 000000000000..e1ba3028967c --- /dev/null +++ b/content/en/blog/2024/scaling-collectors.md @@ -0,0 +1,222 @@ +--- +title: Manage OpenTelemetry Collectors at scale with Ansible +linkTitle: Collectors at scale with Ansible +date: 2024-04-15 +author: '[Ishan Jain](https://github.com/ishanjainn) (Grafana)' +cSpell:ignore: ansible associated Ishan ishanjainn Jain +--- + +You can scale the deployment of +[OpenTelemetry Collector](/docs/collector/deployment/) across multiple Linux +hosts through [Ansible](https://www.ansible.com/), to function both as +[gateways](/docs/collector/deployment/gateway/) and +[agents](/docs/collector/deployment/agent/) within your observability +architecture. Using the OpenTelemetry Collector in this dual capacity enables a +robust collection and forwarding of metrics, traces, and logs to analysis and +visualization platforms. + +We outline a strategy for deploying and managing the OpenTelemetry Collector's +scalable instances throughout your infrastructure using Ansible. In the +following example, we'll use [Grafana](https://grafana.com/) as the target +backend for metrics. + +## Prerequisites + +Before we begin, make sure you meet the following requirements: + +- Ansible installed on your base system +- SSH access to two or more Linux hosts +- Prometheus configured to gather your metrics + +## Install the Grafana Ansible collection + +The +[OpenTelemetry Collector role](https://github.com/grafana/grafana-ansible-collection/tree/main/roles/opentelemetry_collector) +is provided through the +[Grafana Ansible collection](https://docs.ansible.com/ansible/latest/collections/grafana/grafana/) +as of release 4.0. + +To install the Grafana Ansible collection, run this command: + +```sh +ansible-galaxy collection install grafana.grafana +``` + +## Create an Ansible inventory file + +Next, gather the IP addresses and URLs associated with your Linux hosts and +create an inventory file. + +1. Create an Ansible inventory file. + + An Ansible inventory, which resides in a file named `inventory`, lists each + host IP on a separate line, like this (8 hosts shown): + + ```properties + 10.0.0.1 # hostname = ubuntu-01 + 10.0.0.2 # hostname = ubuntu-02 + 10.0.0.3 # hostname = centos-01 + 10.0.0.4 # hostname = centos-02 + 10.0.0.5 # hostname = debian-01 + 10.0.0.6 # hostname = debian-02 + 10.0.0.7 # hostname = fedora-01 + 10.0.0.8 # hostname = fedora-02 + ``` + +2. Create an `ansible.cfg` file within the same directory as `inventory`, with + the following values: + + ```toml + [defaults] + inventory = inventory # Path to the inventory file + private_key_file = ~/.ssh/id_rsa # Path to private SSH Key + remote_user=root + ``` + +## Use the OpenTelemetry Collector Ansible role + +Next, define an Ansible playbook to apply your chosen or created OpenTelemetry +Collector role across your hosts. + +Create a file named `deploy-opentelemetry.yml` in the same directory as your +`ansible.cfg` and `inventory` files: + +```yaml +- name: Install OpenTelemetry Collector + hosts: all + become: true + + tasks: + - name: Install OpenTelemetry Collector + ansible.builtin.include_role: + name: opentelemetry_collectorr + vars: + otel_collector_receivers: + hostmetrics: + collection_interval: 60s + scrapers: + cpu: {} + disk: {} + load: {} + filesystem: {} + memory: {} + network: {} + paging: {} + process: + mute_process_name_error: true + mute_process_exe_error: true + mute_process_io_error: true + processes: {} + + otel_collector_processors: + batch: + resourcedetection: + detectors: [env, system] + timeout: 2s + system: + hostname_sources: [os] + transform/add_resource_attributes_as_metric_attributes: + error_mode: ignore + metric_statements: + - context: datapoint + statements: + - set(attributes["deployment.environment"], + resource.attributes["deployment.environment"]) + - set(attributes["service.version"], + resource.attributes["service.version"]) + + otel_collector_exporters: + prometheusremotewrite: + endpoint: https:///api/prom/push + headers: + Authorization: 'Basic ' + + otel_collector_service: + pipelines: + metrics: + receivers: [hostmetrics] + processors: + [ + resourcedetection, + transform/add_resource_attributes_as_metric_attributes, + batch, + ] + exporters: [prometheusremotewrite] +``` + +{{% alert title="Note" %}} + +Adjust the configuration to match the specific telemetry you intend to collect +as well as where you plan to forward it to. This configuration snippet is a +basic example designed for collecting host metrics that get forwarded to +Prometheus. + +{{% /alert %}} + +The previous configuration would provision the OpenTelemetry Collector to +collect metrics from the Linux host. + +## Running the Ansible playbook + +Deploy the OpenTelemetry Collector across your hosts by running the following +command: + +```sh +ansible-playbook deploy-opentelemetry.yml +``` + +## Check your metrics in the backend + +After your OpenTelemetry Collectors start sending metrics to Prometheus, follow +these steps to visualize them in Grafana: + +### Set up Grafana + +1. **Install Docker**: Make sure Docker is installed on your system. + +2. **Run Grafana Docker Container**: Start a Grafana server with the following + command, which fetches the latest Grafana image: + + ```sh + docker run -d -p 3000:3000 --name=grafana grafana/grafana + ``` + +3. **Access Grafana**: Open in your web browser. The + default login username and password are both `admin`. + +4. **Change passwords** when prompted on first login -- pick a secure one! + +For other installation methods and more detailed instructions, refer to the +[official Grafana documentation](https://grafana.com/docs/grafana/latest/#installing-grafana). + +### Add Prometheus as a data source + +1. In Grafana, navigate to **Connections** > **Data Sources**. +2. Click **Add data source** and select **Prometheus**. +3. In the settings, enter your Prometheus URL, for example, + `http://`, along with any other necessary details. +4. Select **Save & Test**. + +### Explore your metrics + +1. Go to the **Explore** page +2. In the Query editor, select your data source and enter the following query + + ```PromQL + 100 - (avg by (cpu) (irate(system_cpu_time{state="idle"}[5m])) * 100) + ``` + + This query calculates the average percentage of CPU time not spent in the + "idle" state, across each CPU core, over the last 5 minutes. + +3. Explore other metrics and create dashboards to gain insights into your + system's performance. + +This blog post illustrated how you can configure and deploy multiple +OpenTelemetry Collectors across various Linux hosts with the help of Ansible, as +well as visualize collected telemetry in Grafana. Incase you find this useful, +GitHub repository for +[OpenTelemetry Collector role](https://github.com/grafana/grafana-ansible-collection/tree/main/roles/opentelemetry_collector) +for detailed configuration options. If you have questions, You can connect with +me using my contact details at my GitHub profile +[@ishanjainn](https://github.com/ishanjainn). diff --git a/content/en/community/end-user/_index.md b/content/en/community/end-user/_index.md index aaef21e9a6a0..3b95baef139a 100644 --- a/content/en/community/end-user/_index.md +++ b/content/en/community/end-user/_index.md @@ -1,24 +1,33 @@ --- -title: End-user Resources -linkTitle: End User -description: Vendor-agnostic resources for users of OpenTelemetry +title: End-user resources +linkTitle: End user +description: Vendor-agnostic resources for OpenTelemetry users --- -The [OpenTelemetry End User Working Group][] has heard feedback from users who -desire a vendor-agnostic space to discuss adopting OpenTelemetry, so we provide -multiple ways for you to connect with other users of the project and share best -practices: - -- [A synchronous monthly discussion group](discussion-group/) -- [A private slack channel](slack-channel/) -- [Talks about OTel in practice](otel-in-practice/) -- [Direct interview/feedback sessions](interviews-feedback/) - -These forums will bring together operations and development engineers from +Looking to connect with other OpenTelemetry end users in a vendor-agnostic +space, or to learn more about OpenTelemetry? Perhaps you have some feedback +about your implementation or adoption that you'd like to share with project +contributors, or you want to help prioritize project issues. You've come to the +right place! + +- To connect with other end users and learn about upcoming events: + - Join the [Slack channel](slack-channel/) + - Join the [APAC end user discussion group](discussion-group/) +- To learn about OpenTelemetry, check out: + - [OTel in practice](otel-in-practice/) + - Curated content on the + [OpenTelemetry YouTube channel](https://www.youtube.com/@otel-official) +- To provide feedback and help prioritize issues: + - Participate in a [direct interview/feedback session](interviews-feedback/) + - Take a [survey](/community/end-user/feedback-survey/) + - Join a panel discussion (more info coming soon!) + - Vote on issues (more info coming soon!) + +These forums aim to bring together operations and development engineers from different organizations to discuss challenges and solutions to achieving -ubiquitous observability. Share successes and failures, discover best practices, -and meet others who are also on a journey to implement observability powered by -OpenTelemetry. +ubiquitous observability. We encourage you to share your successes and failures, +discover best practices, and meet others who are also on a journey to implement +observability powered by OpenTelemetry. ### Topics @@ -37,15 +46,13 @@ But here are some of the kinds of things we expect will be on the table: **Is this group only for OpenTelemetry end users?** -No! Anyone is welcome to join and discuss their journey to observability. This -group is hosted by the OpenTelemetry Community End-User Working Group, so we -expect most participants will be from organizations that are evaluating or using +Everybody is welcome to join and discuss their journey to observability. This +group is hosted by the OpenTelemetry Community End-User SIG, so we expect most +participants will be from organizations that are evaluating or using OpenTelemetry. **I have questions about this, who can I reach out to?** -You can find members of the End User Working Group in -[#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ). - -[opentelemetry end user working group]: - https://github.com/open-telemetry/community/tree/main/working-groups/end-user +You can find members of the +[OpenTelemetry End User SIG](https://github.com/open-telemetry/community/tree/main/working-groups/end-user) +in [#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ). diff --git a/content/en/community/end-user/discussion-group.md b/content/en/community/end-user/discussion-group.md index 7ab67cadd9c7..f8459caadf1e 100644 --- a/content/en/community/end-user/discussion-group.md +++ b/content/en/community/end-user/discussion-group.md @@ -5,6 +5,9 @@ description: Monthly OpenTelemetry usage discussions, all are welcome! weight: 20 --- +**As of April 2024, AMER and EMEA sessions are discontinued in favor of +discussion panels with a more targeted focus.** + Interested in learning how other end users are implementing OpenTelemetry in their organizations? Come talk shop with other OpenTelemetry end users! This is a vendor-neutral space to discuss best practices, ask questions, and meet other @@ -16,7 +19,6 @@ and changes to the project. ## About -- Sessions are available for all regions! - Search the blog for "End-User Discussions" to find summaries of past discussions. - A project maintainer and/or a Governance Committee member will be in @@ -29,21 +31,11 @@ and changes to the project. Here are upcoming sessions, or you can view them on the [OpenTelemetry calendar](https://github.com/open-telemetry/community#calendar): -- **EMEA (Europe, Middle East, and Africa)**: every third Tuesday of the month - at 11AM GMT ([Zoom link](https://us06web.zoom.us/j/85691064809?pwd=c0VCejh)) - - February 20 - - March 19 - - April 16 - **APAC (Asia Pacific)**: every third Wednesday of the month at 11AM India ST (GMT +5.5), [register](https://lu.ma/1w129wgu) to get the Zoom link - - February 21 - - March 20 - April 17 -- **AMER (Americas)**: every third Thursday of the month at 9AM PT (GMT -8), - ([Zoom link](https://us06web.zoom.us/j/87037874951?pwd=WGo3eUZpeWFZTlhJQXhJeXZhQmwvUT09)) - - February 15 - - March 21 - - April 18 + - May 15 + - June 19 Past topics/questions have included: diff --git a/content/en/community/end-user/feedback-survey.md b/content/en/community/end-user/feedback-survey.md index ac414aaebd75..97d21336fe12 100644 --- a/content/en/community/end-user/feedback-survey.md +++ b/content/en/community/end-user/feedback-survey.md @@ -1,6 +1,6 @@ --- title: Feedback Survey -redirect: https://docs.google.com/forms/d/e/1FAIpQLSdKm6oLYRXlZOhEZMVmjoIn4eBToVYNmF6fwpm5GAIipQmPxA/viewform?pli=1 +redirect: https://forms.gle/xLdJCtRpBaWuDBbs8 manualLinkTarget: _blank _build: { render: link } weight: 60 diff --git a/content/en/community/end-user/interviews-feedback.md b/content/en/community/end-user/interviews-feedback.md index b084fd8d1a4a..c4e945612ec4 100644 --- a/content/en/community/end-user/interviews-feedback.md +++ b/content/en/community/end-user/interviews-feedback.md @@ -4,10 +4,10 @@ description: Help improve OpenTelemetry - share your feedback directly with us! weight: 10 --- -One of the core functions of the OpenTelemetry End User Working Group is to -improve the project by gathering feedback from end users and sharing them with -the appropriate SIGs to help drive prioritization of improvements and changes to -the project. +One of the core functions of the OpenTelemetry End User SIG is to improve the +project by gathering feedback from end users and sharing them with the +appropriate SIGs to help drive prioritization of improvements and changes to the +project. Direct interview or feedback sessions between an organization and the OpenTelemetry Community is one such resource. In these hour-long sessions, we @@ -24,8 +24,8 @@ We will then take the feedback you shared and turn them into actionable tasks for the relevant SIGs, as well as provide context and insight for you during the session as appropriate. -We schedule these sessions once a month, usually during one of the end-user -working group's meetings (alternating Thursdays at 10AM Pacific Time), but can +We try to schedule these sessions once a month, usually during one of the +end-user SIG's meetings (alternating Thursdays at 10AM Pacific Time), but can set up a different time if that does not work for you. The sessions are typically attended by a few project maintainers and/or Governance Committee members, as well as some curious general members of the Community. @@ -40,13 +40,16 @@ Things to keep in mind: concerns. - These are open to the public, so other users may come and ask you questions. -To schedule a session, reach out to us in -[CNCF Community Slack](https://communityinviter.com/apps/cloud-native/cncf): +You can view +[past recordings](https://www.youtube.com/playlist?list=PLVYDBkQ1TdywIl9xKEo5_u7zlwY38dW43) +on the OpenTelemetry YouTube channel. + +To schedule a session, reach out to us via +[CNCF's Community Slack](https://communityinviter.com/apps/cloud-native/cncf): - In the - [#otel-user-research](https://cloud-native.slack.com/archives/C01RT3MSWGZ) + [#otel-sig-end-user](https://cloud-native.slack.com/archives/C01RT3MSWGZ) channel - Via direct message: ping - [Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405), - [Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A), or - [Rynn Mancuso](https://cloud-native.slack.com/team/U03FU45JA1M) + [Reese Lee](https://cloud-native.slack.com/team/U03UARAJ405) or + [Adriana Villela](https://cloud-native.slack.com/team/U02EUCBFK8A) diff --git a/content/en/community/end-user/otel-in-practice.md b/content/en/community/end-user/otel-in-practice.md index c768c67ae81f..33d2cf20ca2b 100644 --- a/content/en/community/end-user/otel-in-practice.md +++ b/content/en/community/end-user/otel-in-practice.md @@ -1,9 +1,9 @@ --- -title: OpenTelemetry In Practice +title: OTel In Practice linkTitle: OTel in Practice description: >- - _OpenTelemetry in Practice_ is a _series_ of talks initiated by some members - of the End User Working Group. + _OTel in Practice_ is a _series_ of talks initiated by some members of the End + User SIG. weight: 30 --- @@ -14,13 +14,16 @@ We’re aiming to: - Build stronger connections with developers focused on specific languages - Improve the experience of implementing OpenTelemetry in production -Each OpenTelemetry in Practice session will include a half hour of lightning -talks and a half hour of open conversation about the topic. We are looking for -people to join the OpenTelemetry in Practice team and people to give talks at -future events. So if you’re interested in shaping these conversations, reach out -in the -[#otel-user-research channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ) -of the [CNCF Slack](https://slack.cncf.io). +Each OTel in Practice session typically includes one or more talks by end users +or project contributors, with space for discussion. We welcome speakers from all +backgrounds! If you're interested in sharing what you've learned in a 15-minute +lightning talk or a longer 30-minute session, reach out in the +[#otel-sig-end-user channel](https://cloud-native.slack.com/archives/C01RT3MSWGZ) +on the [CNCF's Slack](https://slack.cncf.io). + +You can view +[past sessions](https://www.youtube.com/playlist?list=PLVYDBkQ1TdyxKgdGE4ThYLkNRCuLLYy9x) +on the [OpenTelemetry YouTube channel](https://youtube.com/@otel-official). Join the [OpenTelemetry in Practice Meetup Group](https://www.meetup.com/opentelemetry-in-practice-meetup-group/) diff --git a/content/en/community/end-user/slack-channel.md b/content/en/community/end-user/slack-channel.md index 664b509f8f5e..fa91be02db9f 100644 --- a/content/en/community/end-user/slack-channel.md +++ b/content/en/community/end-user/slack-channel.md @@ -2,19 +2,29 @@ title: Slack Channel linkTitle: Slack description: >- - Join a private slack channel to discuss OpenTelemetry with other end users. + Join a Slack channel to discuss OpenTelemetry with other end users. weight: 40 --- -- Confirm your agreement with channel [Code of Conduct][] and reach out to Reese - Lee, Rynn Mancuso, or Adriana Villela on CNCF slack for an invite to - `#otel-endusers`. +Previously, we had a private channel to provide a space for end users to discuss +adoption and implementation issues while allowing them to maintain a layer of +privacy and to meet compliance concerns. Now that the project and community have +grown, and with the transition of the End User WG to End User SIG, we believe +that this private channel is no longer needed. + +As of April 2024, we will begin shifting all of our communications to the +[`#otel-sig-end-user`](https://cloud-native.slack.com/archives/C01RT3MSWGZ) +channel (previously named the `#otel-user-research` channel), and will be +archiving the private channel by **April 30, 2024**. + +We encourage you to join us over at +[`#otel-sig-end-user`](https://cloud-native.slack.com/archives/C01RT3MSWGZ) to +learn about our new charter, what you can expect from us as an end user, and +more. Note the following: + - Troubleshooting or tactical SDK specific questions are still best directed to individual SIG channels or the - [#opentelemetry](https://cloud-native.slack.com/archives/CJFCJHG4Q) channel. + [`#opentelemetry`](https://cloud-native.slack.com/archives/CJFCJHG4Q) channel. - Vendor specific questions are still best directed to vendor channels, or if it - doesn’t exist - [#otel-vendor](https://cloud-native.slack.com/archives/C031SAMGV2A) - -[code of conduct]: - https://github.com/open-telemetry/community/blob/main/working-groups/end-user/discussion-group-code-of-conduct.md + doesn’t exist, + [`#otel-vendor`](https://cloud-native.slack.com/archives/C031SAMGV2A) diff --git a/content/en/docs/collector/_index.md b/content/en/docs/collector/_index.md index bdfe8da5024b..0ccc245e7759 100644 --- a/content/en/docs/collector/_index.md +++ b/content/en/docs/collector/_index.md @@ -3,7 +3,7 @@ title: Collector description: Vendor-agnostic way to receive, process and export telemetry data. aliases: [collector/about] cascade: - vers: 0.97.0 + vers: 0.100.0 weight: 10 --- diff --git a/content/en/docs/collector/configuration.md b/content/en/docs/collector/configuration.md index 419d1c9c7081..4cf07ed66e9e 100644 --- a/content/en/docs/collector/configuration.md +++ b/content/en/docs/collector/configuration.md @@ -34,8 +34,8 @@ You can also provide configurations using environment variables, YAML paths, or HTTP URIs. For example: ```shell -otelcol --config=env:MY_CONFIG_IN_AN_ENVVAR` --config=https://server/config.yaml -otelcol --config="yaml:exporters::debug::verbosity: normal"` +otelcol --config=env:MY_CONFIG_IN_AN_ENVVAR --config=https://server/config.yaml +otelcol --config="yaml:exporters::debug::verbosity: normal" ``` To validate a configuration file, use the `validate` command. For example: @@ -609,10 +609,9 @@ Collector issues. It consists of two subsections: `logs` and `metrics`. The `logs` subsection lets you configure how the logs can be generated by the Collector. By default, the Collector writes its logs to `stderr` with a log level of `INFO`. You can also add static key-value pairs to all log entries with -the `initial_fields` to enrich the logging context. As per the `LogsConfig` -defined in v{{% -param vers %}} [here](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/service/telemetry/config.go), the `logs` configuration options are: +the `initial_fields` to enrich the logging context. The [`logs` configuration +options](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% +param vers %}}/service/telemetry/config.go) are: - `level`: sets the minimum enabled logging level, default `INFO`. - `development`: puts the logger in development mode, default `false`. @@ -635,17 +634,16 @@ The `metrics` subsection lets you configure how the metrics can be generated and exposed by the Collector. By default, the Collector generates basic metrics about itself and expose them for scraping at . You can expose the endpoint to a specific or even all network interfaces when -needed. As per the `MetricsConfig` defined in v{{% -param vers %}} [here](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/service/telemetry/config.go), the `metrics` configuration options -are: +needed. The [`metrics` configuration +options](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% +param vers %}}/service/telemetry/config.go) are: - `level`: the level of telemetry metrics, default `basic`. The possible values are: - - "none" indicates that no telemetry data should be collected. - - "basic" is the recommended and covers the basics of the service telemetry. - - "normal" adds some other indicators on top of basic. - - "detailed" adds dimensions and views to the previous levels. + - `none`: no telemetry is collected. + - `basic`: essential service telemetry. + - `normal`: the default level, adds standard indicators on top of basic. + - `detailed`: the most verbose level, includes dimensions and views. - `address`: the `[address]:port` formatted URL that metrics exposition should be bound to. Default `127.0.0.1:8888`. @@ -858,7 +856,7 @@ Install [`cfssl`](https://github.com/cloudflare/cfssl) and create the following Then run the following commands: -```bash +```sh cfssl genkey -initca csr.json | cfssljson -bare ca cfssl gencert -ca ca.pem -ca-key ca-key.pem csr.json | cfssljson -bare cert ``` @@ -880,14 +878,14 @@ define with this method are merged into the final configuration after all The following examples show how to override settings inside nested sections: -```shell -# The following example sets the verbosity -# level of the debug exporter to 'detailed' +```sh otelcol --set "exporters::debug::verbosity=detailed" -# The following example overrides gRPC -# settings for the OTLP receiver otelcol --set "receivers::otlp::protocols::grpc={endpoint:localhost:4317, compression: gzip}" ``` -Note tha the `--set` option doesn't support setting a key that contains a dot or -an equal sign. +{{% alert title="Important" color="warning" %}} + +The `--set` option doesn't support setting a key that contains a dot or an equal +sign. + +{{% /alert %}} diff --git a/content/en/docs/collector/deployment/agent.md b/content/en/docs/collector/deployment/agent.md index 6db6d6b233ee..2a17343c3b7b 100644 --- a/content/en/docs/collector/deployment/agent.md +++ b/content/en/docs/collector/deployment/agent.md @@ -42,8 +42,8 @@ like so: receivers: otlp: # the OTLP receiver the app is sending traces to protocols: - grpc: - endpoint: 0.0.0.0:4317 + http: + endpoint: 0.0.0.0:4318 processors: batch: @@ -66,8 +66,8 @@ service: receivers: otlp: # the OTLP receiver the app is sending metrics to protocols: - grpc: - endpoint: 0.0.0.0:4317 + http: + endpoint: 0.0.0.0:4318 processors: batch: @@ -90,8 +90,8 @@ service: receivers: otlp: # the OTLP receiver the app is sending logs to protocols: - grpc: - endpoint: 0.0.0.0:4317 + http: + endpoint: 0.0.0.0:4318 processors: batch: diff --git a/content/en/docs/collector/internal-telemetry.md b/content/en/docs/collector/internal-telemetry.md new file mode 100644 index 000000000000..9405568798a1 --- /dev/null +++ b/content/en/docs/collector/internal-telemetry.md @@ -0,0 +1,115 @@ +--- +title: Internal telemetry +weight: 25 +cSpell:ignore: journalctl kube otecol pprof tracez zpages +--- + +You can monitor the health of any OpenTelemetry Collector instance by checking +its own internal telemetry. Read on to learn how to configure this telemetry to +help you [troubleshoot](/docs/collector/troubleshooting/) Collector issues. + +## Activate internal telemetry in the Collector + +By default, the Collector exposes its own telemetry in two ways: + +- Internal [metrics](#configure-internal-metrics) are exposed using a Prometheus + interface which defaults to port `8888`. +- [Logs](#configure-internal-logs) are emitted to `stderr` by default. + +### Configure internal metrics + +You can configure how internal metrics are generated and exposed by the +Collector. By default, the Collector generates basic metrics about itself and +exposes them for scraping at `http://127.0.0.1:8888/metrics`. You can expose the +endpoint to one specific or all network interfaces when needed. For +containerized environments, you might want to expose this port on a public +interface. + +Set the address in the config `service::telemetry::metrics`: + +```yaml +service: + telemetry: + metrics: + address: '0.0.0.0:8888' +``` + +You can enhance the metrics telemetry level using the `level` field. The +following is a list of all possible values and their explanations. + +- `none` indicates that no telemetry data should be collected. +- `basic` is the recommended value and covers the basics of the service + telemetry. +- `normal` adds other indicators on top of basic. +- `detailed` adds dimensions and views to the previous levels. + +For example: + +```yaml +service: + telemetry: + metrics: + level: detailed + address: ':8888' +``` + +The Collector can also be configured to scrape its own metrics and send them +through configured pipelines. For example: + +```yaml +receivers: + prometheus: + config: + scrape_configs: + - job_name: 'otelcol' + scrape_interval: 10s + static_configs: + - targets: ['0.0.0.0:8888'] + metric_relabel_configs: + - source_labels: [__name__] + regex: '.*grpc_io.*' + action: drop +exporters: + debug: +service: + pipelines: + metrics: + receivers: [prometheus] + exporters: [debug] +``` + +{{% alert title="Caution" color="warning" %}} + +Self-monitoring is a risky practice. If an issue arises, the source of the +problem is unclear and the telemetry is unreliable. + +{{% /alert %}} + +### Configure internal logs + +You can find log output in `stderr`. The verbosity level for logs defaults to +`INFO`, but you can adjust it in the config `service::telemetry::logs`: + +```yaml +service: + telemetry: + logs: + level: 'debug' +``` + +You can also see logs for the Collector on a Linux systemd system using +`journalctl`: + +{{< tabpane text=true >}} {{% tab "All logs" %}} + +```sh +journalctl | grep otelcol +``` + +{{% /tab %}} {{% tab "Errors only" %}} + +```sh +journalctl | grep otelcol | grep Error +``` + +{{% /tab %}} {{< /tabpane >}} diff --git a/content/en/docs/collector/troubleshooting.md b/content/en/docs/collector/troubleshooting.md index d83b7cdb821e..8278d00b678b 100644 --- a/content/en/docs/collector/troubleshooting.md +++ b/content/en/docs/collector/troubleshooting.md @@ -8,6 +8,12 @@ This page describes some options when troubleshooting the health or performance of the OpenTelemetry Collector. The Collector provides a variety of metrics, logs, and extensions for debugging issues. +## Internal telemetry + +You can configure and use the Collector's own +[internal telemetry](/docs/collector/internal-telemetry/) to monitor its +performance. + ## Sending test data For certain types of issues, particularly verifying configuration and debugging diff --git a/content/en/docs/concepts/glossary.md b/content/en/docs/concepts/glossary.md index 387cf3fad7bb..751e3d163f9d 100644 --- a/content/en/docs/concepts/glossary.md +++ b/content/en/docs/concepts/glossary.md @@ -227,12 +227,6 @@ Short form for [OpenTelemetry Collector](#collector). Short for [OpenTelemetry Protocol](/docs/specs/otlp/). -### **Processor** - -The operation performed on data between being received and being exported. For -example, batching. Used by the -[Collector](/docs/collector/configuration/#processors). - ### **Propagators** Used to serialize and deserialize specific parts of telemetry data such as span diff --git a/content/en/docs/concepts/signals/traces.md b/content/en/docs/concepts/signals/traces.md index 03a464945fee..1ea0b8bc4e00 100644 --- a/content/en/docs/concepts/signals/traces.md +++ b/content/en/docs/concepts/signals/traces.md @@ -12,6 +12,14 @@ sophisticated mesh of services, traces are essential to understanding the full Let's explore this with three units of work, represented as [Spans](#spans): +{{% alert title="Note" %}} + +The following JSON examples do not represent a specific format, and especially +not [OTLP/JSON](/docs/specs/otlp/#json-protobuf-encoding), which is more +verbose. + +{{% /alert %}} + `hello` span: ```json @@ -110,7 +118,7 @@ that matches the `span_id` of the `hello` span. ``` This span represents the third operation in this trace and, like the previous -one, it's a child of the 'hello' Span. That also makes it a sibling of the +one, it's a child of the `hello` span. That also makes it a sibling of the `hello-greetings` span. These three blocks of JSON all share the same `trace_id`, and the `parent_id` diff --git a/content/en/docs/contributing/_index.md b/content/en/docs/contributing/_index.md index 864531771913..3c0d35a670f9 100644 --- a/content/en/docs/contributing/_index.md +++ b/content/en/docs/contributing/_index.md @@ -6,8 +6,17 @@ weight: 200 cSpell:ignore: prepopulated spacewhite --- -You can open an issue about OpenTelemetry documentation, or contribute a change -with a pull request (PR) to the +The following guide describes how to contribute to OpenTelemetry documentation. +For guidance on how to contribute to the OpenTelemetry project in general, see +the +[OpenTelemetry Contributor Guide](https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md) +, which provides details on the Contributor License Agreement and the Code of +Conduct. In extent, every language implementation, collector, and conventions +[repository](https://github.com/open-telemetry/) has their own specific +contributing guides. + +For documentation, you can open an issue about OpenTelemetry, or contribute a +change with a pull request (PR) to the [`opentelemetry.io` GitHub repository](https://github.com/open-telemetry/opentelemetry.io). OpenTelemetry documentation contributors: @@ -17,11 +26,6 @@ OpenTelemetry documentation contributors: - Update the OpenTelemetry Registry. - Improve the code that builds the site. -See also the general -[OpenTelemetry Contributor Guide](https://github.com/open-telemetry/community/blob/main/CONTRIBUTING.md) -, which provides details on the Contributor License Agreement and the Code of -Conduct. - ## Requirements To contribute, you need to be familiar with the following techs and tools: @@ -72,7 +76,7 @@ class first,second white _Figure 1. Contributing new content._ -The previous figure presents the basic steps for new docs contributions. +The previous figure illustrates how to contribute new documentation. To contribute new content pages or improve existing content pages, open a pull request (PR): @@ -82,6 +86,14 @@ request (PR): - If your changes are large, read [Work from a local fork](#fork-the-repo) to learn how to make changes locally on your computer. +{{% alert title="Tip" %}} + +Turn your pull request into a draft to signal that the content still isn't ready +for review. Maintainers may still comment or do high-level reviews, though they +won't review the content in full until you remove the draft status. + +{{% /alert %}} + ### Changes using GitHub {#changes-using-github} If you're less experienced with Git workflows, here's an easier method of @@ -120,12 +132,12 @@ _Figure 2. Steps for opening a PR using GitHub._ 1. On the page where you see the issue, select the **Edit this page** option in the right-hand side navigation panel. -1. If you're not a member of the project, GitHub will offer to create a fork of - the repository. Select **Fork this repository**. +1. If you're not a member of the project, GitHub offers to create a fork of the + repository. Select **Fork this repository**. 1. Make your changes in the GitHub editor. -1. Below the editor, fill in the **Propose file change** form. +1. Fill in the **Propose file change** form. 1. Select **Propose file change**. diff --git a/content/en/docs/demo/_index.md b/content/en/docs/demo/_index.md index cb35886fbb6d..b09e5ec46468 100644 --- a/content/en/docs/demo/_index.md +++ b/content/en/docs/demo/_index.md @@ -52,6 +52,7 @@ found here: - [Quote Service](services/quote/) - [Recommendation Service](services/recommendation/) - [Shipping Service](services/shipping/) +- [Image Provider Service](services/imageprovider/) ## Scenarios diff --git a/content/en/docs/demo/architecture.md b/content/en/docs/demo/architecture.md index 26c706ff4a37..1b22adcacced 100644 --- a/content/en/docs/demo/architecture.md +++ b/content/en/docs/demo/architecture.md @@ -22,6 +22,7 @@ emailservice(Email Service):::ruby frauddetectionservice(Fraud Detection Service):::kotlin frontend(Frontend):::typescript frontendproxy(Frontend Proxy
(Envoy)):::cpp +imageprovider(Image Provider
(nginx)):::cpp loadgenerator([Load Generator]):::python paymentservice(Payment Service):::javascript productcatalogservice(Product Catalog Service):::golang @@ -33,6 +34,7 @@ queue[(queue
(Kafka))] Internet -->|HTTP| frontendproxy frontendproxy -->|HTTP| frontend loadgenerator -->|HTTP| frontendproxy +frontendproxy -->|HTTP| imageprovider queue -->|TCP| accountingservice queue -->|TCP| frauddetectionservice diff --git a/content/en/docs/demo/feature-flags.md b/content/en/docs/demo/feature-flags.md index f3c49f1dfa96..e41cc68e7273 100644 --- a/content/en/docs/demo/feature-flags.md +++ b/content/en/docs/demo/feature-flags.md @@ -10,8 +10,8 @@ cSpell:ignore: flagd loadgenerator OLJCESPC7Z The demo provides several feature flags that you can use to simulate different scenarios. These flags are managed by [`flagd`](https://flagd.dev), a simple feature flag service that supports [OpenFeature](https://openfeature.dev). Flag -values are stored in the `demo.flagd.json` file. To enable a flag, change the -`defaultVariant` value in the config file for a given flag to "on". +values are stored in the `src/flagd/demo.flagd.json` file. To enable a flag, +change the `defaultVariant` value in the config file for a given flag to "on". | Feature Flag | Service(s) | Description | | ----------------------------------- | ---------------- | --------------------------------------------------------------------------------------------------------- | @@ -24,6 +24,7 @@ values are stored in the `demo.flagd.json` file. To enable a flag, change the | `paymentServiceFailure` | Payment Service | Generate an error when calling the `charge` method. | | `paymentServiceUnreachable` | Checkout Service | Use a bad address when calling the PaymentService to make it seem like the PaymentService is unavailable. | | `loadgeneratorFloodHomepage` | Loadgenerator | Start flooding the homepage with a huge amount of requests, configurable by changing flagd JSON on state. | +| `kafkaQueueProblems` | Kafka | Overloads Kafka queue while simultaneously introducing a consumer side delay leading to a lag spike. | ## Feature Flag Architecture diff --git a/content/en/docs/demo/services/imageprovider.md b/content/en/docs/demo/services/imageprovider.md new file mode 100644 index 000000000000..0c597a14f866 --- /dev/null +++ b/content/en/docs/demo/services/imageprovider.md @@ -0,0 +1,10 @@ +--- +title: Image Provider Service +linkTitle: Image Provider +--- + +This service provides the images which are used in the frontend. The images are +statically hosted on a NGINX instance. The NGINX server is instrumented with the +[nginx-otel module](https://github.com/nginxinc/nginx-otel/tree/main). + +[Image Provider service source](https://github.com/open-telemetry/opentelemetry-demo/blob/main/src/imageprovider/) diff --git a/content/en/docs/demo/services/quote.md b/content/en/docs/demo/services/quote.md index ce3157297668..5d04345e8e41 100644 --- a/content/en/docs/demo/services/quote.md +++ b/content/en/docs/demo/services/quote.md @@ -92,8 +92,34 @@ $span->addEvent('Quote processed, response sent back', [ ## Metrics -TBD +In this demo, metrics are emitted by the batch trace and logs processors. The +metrics describe the internal state of the processor, such as number of exported +spans or logs, the queue limit, and queue usage. + +You can enable metrics by setting the environment variable +`OTEL_PHP_INTERNAL_METRICS_ENABLED` to `true`. + +A manual metric is also emitted, which counts the number of quotes generated, +including an attribute for the number of items. + +A counter is created from the globally configured Meter Provider, and is +incremented each time a quote is generated: + +```php +static $counter; +$counter ??= Globals::meterProvider() + ->getMeter('quotes') + ->createCounter('quotes', 'quotes', 'number of quotes calculated'); +$counter->add(1, ['number_of_items' => $numberOfItems]); +``` + +Metrics accumulate and are exported periodically based on the value configured +in `OTEL_METRIC_EXPORT_INTERVAL`. ## Logs -TBD +The quote service emits a log message after a quote is calculated. The Monolog +logging package is configured with a +[Logs Bridge](/docs/concepts/signals/logs/#log-appender--bridge) which converts +Monolog logs into the OpenTelemetry format. Logs sent to this logger will be +exported via the globally configured OpenTelemetry logger. diff --git a/content/en/docs/demo/telemetry-features/trace-coverage.md b/content/en/docs/demo/telemetry-features/trace-coverage.md index 4fcf56e1b1eb..e97581476de8 100644 --- a/content/en/docs/demo/telemetry-features/trace-coverage.md +++ b/content/en/docs/demo/telemetry-features/trace-coverage.md @@ -12,7 +12,7 @@ aliases: [trace_service_features, trace-features, ../trace-features] | Checkout | Go | ✅ | ✅ | ✅ | 🔕 | 🔕 | 🔕 | ✅ | | Currency | C++ | 🔕 | ✅ | ✅ | ✅ | 🔕 | 🔕 | 🚧 | | Email | Ruby | ✅ | ✅ | ✅ | 🔕 | 🔕 | 🔕 | 🚧 | -| Fraud Detection | Kotlin | ✅ | 🚧 | 🚧 | 🚧 | 🚧 | 🚧 | 🚧 | +| Fraud Detection | Kotlin | ✅ | 🚧 | 🚧 | 🚧 | ✅ | 🚧 | 🚧 | | Frontend | JavaScript | ✅ | ✅ | ✅ | 🔕 | ✅ | ✅ | ✅ | | Payment | JavaScript | ✅ | ✅ | ✅ | 🔕 | 🔕 | ✅ | ✅ | | Product Catalog | Go | ✅ | 🔕 | ✅ | 🔕 | 🔕 | 🔕 | 🚧 | diff --git a/content/en/docs/kubernetes/collector/components.md b/content/en/docs/kubernetes/collector/components.md index 6d623f11fccd..9394c4cd2f1e 100644 --- a/content/en/docs/kubernetes/collector/components.md +++ b/content/en/docs/kubernetes/collector/components.md @@ -563,7 +563,7 @@ To see which objects are available for collection run in your cluster run ```console -kubeclt api-resources +kubectl api-resources NAME SHORTNAMES APIVERSION NAMESPACED KIND bindings v1 true Binding componentstatuses cs v1 false ComponentStatus diff --git a/content/en/docs/kubernetes/getting-started.md b/content/en/docs/kubernetes/getting-started.md index 4033cebf5d9a..f394c26cd9d8 100644 --- a/content/en/docs/kubernetes/getting-started.md +++ b/content/en/docs/kubernetes/getting-started.md @@ -156,6 +156,9 @@ The following `values.yaml` is what we'll use ```yaml mode: daemonset +image: + repository: otel/opentelemetry-collector-k8s + presets: # enables the k8sattributesprocessor and adds it to the traces, metrics, and logs pipelines kubernetesAttributes: @@ -240,6 +243,9 @@ The following `values.yaml` is what we'll use: ```yaml mode: deployment +image: + repository: otel/opentelemetry-collector-k8s + # We only want one of these collectors - any more and we'd produce duplicate data replicaCount: 1 diff --git a/content/en/docs/kubernetes/helm/collector.md b/content/en/docs/kubernetes/helm/collector.md index f3e5b299858b..35ca41f770b1 100644 --- a/content/en/docs/kubernetes/helm/collector.md +++ b/content/en/docs/kubernetes/helm/collector.md @@ -23,7 +23,8 @@ following commands: ```sh helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts helm install my-opentelemetry-collector open-telemetry/opentelemetry-collector \ - --set mode= + --set image.repository="otel/opentelemetry-collector-k8s" \ + --set mode= \ ``` ### Configuration diff --git a/content/en/docs/kubernetes/helm/operator.md b/content/en/docs/kubernetes/helm/operator.md index b82816a4a293..39ec637131b1 100644 --- a/content/en/docs/kubernetes/helm/operator.md +++ b/content/en/docs/kubernetes/helm/operator.md @@ -22,8 +22,9 @@ following commands: ```console helm repo add open-telemetry https://open-telemetry.github.io/opentelemetry-helm-charts helm install my-opentelemetry-operator open-telemetry/opentelemetry-operator \ + --set "manager.collectorImage.repository=otel/opentelemetry-collector-k8s" \ --set admissionWebhooks.certManager.enabled=false \ - --set admissionWebhooks.certManager.autoGenerateCert.enabled=true + --set admissionWebhooks.autoGenerateCert.enabled=true ``` This will install an OpenTelemetry Operator with a self-signed certificate and diff --git a/content/en/docs/kubernetes/operator/automatic.md b/content/en/docs/kubernetes/operator/automatic.md index 10899e528c46..f620ec2a37a7 100644 --- a/content/en/docs/kubernetes/operator/automatic.md +++ b/content/en/docs/kubernetes/operator/automatic.md @@ -282,12 +282,24 @@ must be able to receive OTLP over `grpc`. Therefore, the example uses #### Excluding auto-instrumentation {#js-excluding-auto-instrumentation} -By default, the Node.js auto-instrumentation ships with -[many instrumentation libraries](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/README.md#supported-instrumentations). -At the moment, there is no way to opt-in to only specific packages or disable -specific packages. If you don't want to use a package included by the default -image you must either supply your own image that includes only the packages you -want or use manual instrumentation. +By default, the Node.js auto-instrumentation has all the instrumentation +libraries enabled. + +To enable only specific instrumentations you can use the +`OTEL_NODE_ENABLED_INSTRUMENTATIONS` environment variable as documented in the +[Node.js auto-instrumentation documentation](/docs/languages/js/automatic/configuration/#excluding-auto-instrumentation). + +```yaml +apiVersion: opentelemetry.io/v1alpha1 +kind: Instrumentation +# ... other fields skipped from this example +spec: + # ... other fields skipped from this example + nodejs: + env: + - name: OTEL_NODE_ENABLED_INSTRUMENTATIONS + value: http,nestjs-core # comma-separated list of the instrumentation package names without the `@opentelemetry/instrumentation-` prefix. +``` #### Learn more {#js-learn-more} diff --git a/content/en/docs/languages/cpp/getting-started.md b/content/en/docs/languages/cpp/getting-started.md index b725a64822c3..f51ed335a1c9 100644 --- a/content/en/docs/languages/cpp/getting-started.md +++ b/content/en/docs/languages/cpp/getting-started.md @@ -17,7 +17,7 @@ Ensure that you have the following installed locally: - Git - C++ compiler supporting C++ version >= 14 - Make -- CMake version >= 3.20 +- CMake version >= 3.25 ## Example Application @@ -51,10 +51,11 @@ To begin, install Oat++ locally using the git clone https://github.com/oatpp/oatpp.git ``` -2. Navigate to the `oatpp` directory. +2. Navigate to the `oatpp` directory and switch to 1.3.0 version for now: ```bash cd oatpp + git checkout 1.3.0-latest ``` 3. Create a `build` subdirectory and navigate into it. @@ -113,24 +114,30 @@ using CMake, following these steps: ``` 4. In the `build` directory run CMake, to configure and generate the build - system. + system without enabling tests: ```bash - cmake .. + cmake -DBUILD_TESTING=OFF .. ``` Or, if the `cmake --build` fails, you can also try: ```bash - cmake -DWITH_ABSEIL=ON .. + cmake -DBUILD_TESTING=OFF -DWITH_ABSEIL=ON .. ``` -5. Execute the build process. +5. Execute the build process: ```bash cmake --build . ``` +6. Install OpenTelemetry C++ in otel-cpp-starter/otel-cpp: + + ```bash + cmake --install . --prefix ../../otel-cpp + ``` + With Oat++ and OpenTelemetry C++ ready, you can continue with creating the HTTP Server, that we want to instrument eventually. @@ -140,12 +147,13 @@ In your `otel-cpp-starter` folder, create a subfolder `roll-dice`, where the Oat++ library will be used by referencing the oatpp headers and linking them when compiling your project. -Create a file called `CMakeLists.txt` to define the Oat++ library directories, -include paths, and link against Oat++ during the compilation process. +Create a file called `CMakeLists.txt` inside `roll-dice` to define the Oat++ +library directories, include paths, and link against Oat++ during the +compilation process. ```cmake +cmake_minimum_required(VERSION 3.25) project(RollDiceServer) -cmake_minimum_required(VERSION 3.1) # Set C++ standard (e.g., C++17) set(CMAKE_CXX_STANDARD 17) set(project_name roll-dice-server) @@ -208,7 +216,7 @@ void run() { auto connectionHandler = oatpp::web::server::HttpConnectionHandler::createShared(router); auto connectionProvider = oatpp::network::tcp::server::ConnectionProvider::createShared({"localhost", 8080, oatpp::network::Address::IP_4}); oatpp::network::Server server(connectionProvider, connectionHandler); - OATPP_LOGI("Dice Server", "Server running on port %s", connectionProvider->getProperty("port").getData()); + OATPP_LOGI("Dice Server", "Server running on port %s", static_cast(connectionProvider->getProperty("port").getData())); server.run(); } @@ -245,8 +253,8 @@ To add OpenTelemetry to your application, update the `CMakeLists.txt` file with the following additional dependencies. ```cmake +cmake_minimum_required(VERSION 3.25) project(RollDiceServer) -cmake_minimum_required(VERSION 3.1) # Set C++ standard (e.g., C++17) set(CMAKE_CXX_STANDARD 17) set(project_name roll-dice-server) @@ -259,7 +267,7 @@ set(SOURCES add_executable(dice-server ${SOURCES}) set(OATPP_ROOT ../oatpp) -set(OPENTELEMETRY_ROOT ../opentelemetry-cpp) +set(opentelemetry-cpp_DIR ../otel-cpp/lib/cmake/opentelemetry-cpp) find_library(OATPP_LIB NAMES liboatpp.a HINTS "${OATPP_ROOT}/build/src/" NO_DEFAULT_PATH) if (NOT OATPP_LIB) message(SEND_ERROR "Did not find oatpp library ${OATPP_ROOT}/build/src") @@ -267,23 +275,13 @@ endif() # set the path to the directory containing "oatpp" package configuration files include_directories(${OATPP_ROOT}/src) -include_directories(${OPENTELEMETRY_ROOT}/api/include) -include_directories(${OPENTELEMETRY_ROOT}/sdk/include) -include_directories(${OPENTELEMETRY_ROOT}/sdk/src) -include_directories(${OPENTELEMETRY_ROOT}/exporters/ostream/include) - -find_library(OPENTELEMETRY_COMMON_LIB NAMES libopentelemetry_common.a HINTS "${OPENTELEMETRY_ROOT}/build/sdk/src/common" NO_DEFAULT_PATH) -find_library(OPENTELEMETRY_TRACE_LIB NAMES libopentelemetry_trace.a HINTS "${OPENTELEMETRY_ROOT}/build/sdk/src/trace" NO_DEFAULT_PATH) -find_library(OPENTELEMETRY_EXPORTER_LIB NAMES libopentelemetry_exporter_ostream_span.a HINTS "${OPENTELEMETRY_ROOT}/build/exporters/ostream" NO_DEFAULT_PATH) -find_library(OPENTELEMETRY_RESOURCE_LIB NAMES libopentelemetry_resources.a HINTS "${OPENTELEMETRY_ROOT}/build/sdk/src/resource" NO_DEFAULT_PATH) - -if(OPENTELEMETRY_COMMON_LIB AND OPENTELEMETRY_TRACE_LIB AND OPENTELEMETRY_EXPORTER_LIB AND OPENTELEMETRY_RESOURCE_LIB) - message(STATUS "Found opentelemetry libraries") -else() - message(SEND_ERROR "Did not find opentelemetry libraries") -endif() +# Use find_package to include OpenTelemetry C++ +find_package(opentelemetry-cpp CONFIG REQUIRED NO_DEFAULT_PATH) -target_link_libraries(dice-server PRIVATE ${OATPP_LIB} ${OPENTELEMETRY_COMMON_LIB} ${OPENTELEMETRY_TRACE_LIB} ${OPENTELEMETRY_EXPORTER_LIB} ${OPENTELEMETRY_RESOURCE_LIB}) +# Link against each OpenTelemetry C++ library +target_link_libraries(dice-server PRIVATE + ${OATPP_LIB} + ${OPENTELEMETRY_CPP_LIBRARIES}) ``` Update the `main.cpp` file with the following code to initialize a tracer and to @@ -347,7 +345,7 @@ void run() { auto connectionHandler = oatpp::web::server::HttpConnectionHandler::createShared(router); auto connectionProvider = oatpp::network::tcp::server::ConnectionProvider::createShared({"localhost", 8080, oatpp::network::Address::IP_4}); oatpp::network::Server server(connectionProvider, connectionHandler); - OATPP_LOGI("Dice Server", "Server running on port %s", connectionProvider->getProperty("port").getData()); + OATPP_LOGI("Dice Server", "Server running on port %s", static_cast(connectionProvider->getProperty("port").getData())); server.run(); } diff --git a/content/en/docs/languages/erlang/libraries.md b/content/en/docs/languages/erlang/libraries.md new file mode 100644 index 000000000000..271a72f78336 --- /dev/null +++ b/content/en/docs/languages/erlang/libraries.md @@ -0,0 +1,55 @@ +--- +title: Using instrumentation libraries +linkTitle: Libraries +weight: 40 +cSpell:ignore: Ecto Hex +--- + +{{% docs/languages/libraries-intro "Erlang" %}} + +## Use instrumentation libraries + +If a library doesn't include OpenTelemetry support, you can use +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +to generate telemetry data for a library or framework. + +For example, +[the instrumentation library for Ecto](https://github.com/open-telemetry/opentelemetry-erlang-contrib/tree/main/instrumentation/opentelemetry_ecto) +automatically creates [spans](/docs/concepts/signals/traces/#spans) based on +queries. + +## Setup + +Each instrumentation library is distributed as a Hex package. To install an +instrumentation, add the dependency to your `mix.exs` file. For example: + +```elixir +def deps do + [ + {:opentelemetry_{package}, "~> 1.0"} + ] +end +``` + +Where `{package}` is the name of the instrumentation. + +Note that some instrumentation packages might have prerequisites. Check the +documentation of each instrumentation package for further instructions. + +## Available instrumentation libraries + +For a full list of instrumentation libraries, see the +[list of Hex packages](https://hex.pm/packages?search=opentelemetry&sort=recent_downloads). + +You can also find more instrumentations available in the +[registry](/ecosystem/registry/?language=erlang&component=instrumentation). + +## Next steps + +After you have set up instrumentation libraries, you might want to add your own +[instrumentation](/docs/languages/erlang/instrumentation) to your code, to +collect custom telemetry data. + +You might also want to configure an appropriate exporter to +[export your telemetry data](/docs/languages/erlang/exporters) to one or more +telemetry backends. diff --git a/content/en/docs/languages/go/exporters.md b/content/en/docs/languages/go/exporters.md index 7214a2b2d615..954b371fc866 100644 --- a/content/en/docs/languages/go/exporters.md +++ b/content/en/docs/languages/go/exporters.md @@ -3,7 +3,7 @@ title: Exporters aliases: [exporting_data] weight: 50 # prettier-ignore -cSpell:ignore: otlpmetric otlpmetricgrpc otlpmetrichttp otlptrace otlptracegrpc otlptracehttp promhttp stdouttrace +cSpell:ignore: otlplog otlploghttp otlpmetric otlpmetricgrpc otlpmetrichttp otlptrace otlptracegrpc otlptracehttp promhttp stdoutlog stdouttrace --- {{% docs/languages/exporters/intro go %}} @@ -15,8 +15,9 @@ simplest to set up. ### Console traces +The [`go.opentelemetry.io/otel/exporters/stdout/stdouttrace`](https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdouttrace) -contains an implementation of the console trace exporter. +package contains an implementation of the console trace exporter. Here's how you can create an exporter with default configuration: @@ -31,10 +32,11 @@ func newExporter() (trace.SpanExporter, error) { } ``` -### Console metrics (Experimental) +### Console metrics +The [`go.opentelemetry.io/otel/exporters/stdout/stdoutmetric`](https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutmetric) -contains an implementation of the console metrics exporter. +package contains an implementation of the console metrics exporter. Here's how you can create an exporter with default configuration: @@ -49,6 +51,25 @@ func newExporter() (metric.Exporter, error) { } ``` +### Console logs (Experimental) {#console-logs} + +The +[`go.opentelemetry.io/otel/exporters/stdout/stdoutlog`](https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutlog) +package contains an implementation of the console log exporter. + +Here's how you can create an exporter with default configuration: + +```go +import ( + "go.opentelemetry.io/otel/exporters/stdout/stdoutlog" + "go.opentelemetry.io/otel/sdk/log" +) + +func newExporter() (log.Exporter, error) { + return stdoutlog.New() +} +``` + ## OTLP To send trace data to an OTLP endpoint (like the [collector](/docs/collector) or @@ -73,7 +94,7 @@ import ( ) func newExporter(ctx context.Context) (trace.SpanExporter, error) { - return otlptracehttp.New(ctx, client) + return otlptracehttp.New(ctx) } ``` @@ -91,7 +112,7 @@ import ( ) func newExporter(ctx context.Context) (trace.SpanExporter, error) { - return otlptracegrpc.New(ctx, client) + return otlptracegrpc.New(ctx) } ``` @@ -173,3 +194,22 @@ func newExporter(ctx context.Context) (metric.Reader, error) { To learn more on how to use the Prometheus exporter, try the [prometheus example](https://github.com/open-telemetry/opentelemetry-go/tree/main/example/prometheus) + +### OTLP logs over HTTP (Experimental) + +[`go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp`](https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp) +contains an implementation of OTLP logs exporter using HTTP with binary protobuf +payloads. + +Here's how you can create an exporter with default configuration: + +```go +import ( + "go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp" + "go.opentelemetry.io/otel/sdk/log" +) + +func newExporter(ctx context.Context) (log.Exporter, error) { + return otlploghttp.New(ctx) +} +``` diff --git a/content/en/docs/languages/java/_index.md b/content/en/docs/languages/java/_index.md index 10d92d8759b6..e93d9e45532c 100644 --- a/content/en/docs/languages/java/_index.md +++ b/content/en/docs/languages/java/_index.md @@ -6,8 +6,8 @@ description: >- aliases: [/java, /java/metrics, /java/tracing] cascade: vers: - instrumentation: 2.2.0 - otel: 1.37.0 + instrumentation: 2.3.0 + otel: 1.38.0 semconv: 1.25.0 weight: 18 --- diff --git a/content/en/docs/languages/java/automatic/configuration.md b/content/en/docs/languages/java/automatic/configuration.md index 06c4b9a1867e..4badcceeb420 100644 --- a/content/en/docs/languages/java/automatic/configuration.md +++ b/content/en/docs/languages/java/automatic/configuration.md @@ -30,6 +30,14 @@ specific portions of the SDK & agent: - [Span limits](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure/README.md#span-limits) - [Using SPI to further configure the SDK](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure/README.md#customizing-the-opentelemetry-sdk) +{{% alert title="Important" color="warning" %}} + +Unlike the SDK autoconfiguration, versions 2.0+ of the Java agent and +OpenTelemetry Spring Boot starter use `http/protobuf` as the default protocol, +not `grpc`. + +{{% /alert %}} + ### Enable Resource Providers that are disabled by default In addition to the resource configuration from the SDK autoconfiguration, you diff --git a/content/en/docs/languages/java/automatic/spring-boot.md b/content/en/docs/languages/java/automatic/spring-boot.md index ed27a927939f..b63ac5f20c73 100644 --- a/content/en/docs/languages/java/automatic/spring-boot.md +++ b/content/en/docs/languages/java/automatic/spring-boot.md @@ -137,10 +137,10 @@ The OpenTelemetry starter uses OpenTelemetry Spring Boot ```xml - - io.opentelemetry.instrumentation - opentelemetry-spring-boot-starter - + + io.opentelemetry.instrumentation + opentelemetry-spring-boot-starter + ``` @@ -165,14 +165,18 @@ IDE. The OpenTelemetry Starter supports all the [SDK Autoconfiguration](/docs/languages/java/automatic/configuration/#sdk-autoconfiguration) -(since 2.2.0). You can set properties in the `application.properties` or the -`application.yaml` file, or use environment variables. +(since 2.2.0). + +You can update the configuration with properties in the `application.properties` +or the `application.yaml` file, or with environment variables. `application.properties` example: ```properties otel.propagators=tracecontext,b3 -otel.resource.attributes=environment=dev,xyz=foo +otel.resource.attributes.deployment.environment=dev +otel.resource.attributes.service.name=cart +otel.resource.attributes.service.namespace=shop ``` `application.yaml` example: @@ -184,18 +188,49 @@ otel: - b3 resource: attributes: - environment: dev - xyz: foo + deployment.environment: dev + service: + name: cart + namespace: shop ``` Environment variables example: ```shell export OTEL_PROPAGATORS="tracecontext,b3" -export OTEL_RESOURCE_ATTRIBUTES="environment=dev,xyz=foo" +export OTEL_RESOURCE_ATTRIBUTES="deployment.environment=dev,service.name=cart,service.namespace=shop" +``` + +#### Overriding Resource Attributes + +As usual in Spring Boot, you can override properties in the +`application.properties` and `application.yaml` files with environment +variables. + +For example, you can set or override the `deployment.environment` resource +attribute (not changing `service.name` or `service.namespace`) by setting the +standard `OTEL_RESOURCE_ATTRIBUTES` environment variable: + +```shell +export OTEL_RESOURCE_ATTRIBUTES="deployment.environment=prod" +``` + +Alternatively, you can use the `OTEL_RESOURCE_ATTRIBUTES_DEPLOYMENT_ENVIRONMENT` +environment variable to set or override a single resource attribute: + +```shell +export OTEL_RESOURCE_ATTRIBUTES_DEPLOYMENT_ENVIRONMENT="prod" ``` -Disable the OpenTelemetry Starter: +The second option supports +[SpEL](https://docs.spring.io/spring-framework/docs/3.2.x/spring-framework-reference/html/expressions.html) +expressions. + +Note that `DEPLOYMENT_ENVIRONMENT` gets converted to `deployment.environment` by +Spring Boot's +[Relaxed Binding](https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables). + +#### Disable the OpenTelemetry Starter {{% config_option name="otel.sdk.disabled" %}} @@ -218,11 +253,11 @@ from tracing: ```xml - - io.opentelemetry.contrib - opentelemetry-samplers + + io.opentelemetry.contrib + opentelemetry-samplers 1.33.0-alpha - + ``` @@ -245,7 +280,7 @@ import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; @Configuration -public class Application { +public class OpenTelemetryConfig { @Bean public AutoConfigurationCustomizerProvider otelCustomizer() { @@ -259,11 +294,56 @@ public class Application { } ``` +##### Configure the exporter programmatically + +You can also configure OTLP exporters programmatically. This configuration +replaces the default OTLP exporter and adds a custom header to the requests. + +```java +import io.opentelemetry.exporter.otlp.http.trace.OtlpHttpSpanExporter; +import io.opentelemetry.sdk.autoconfigure.spi.AutoConfigurationCustomizerProvider; +import java.util.Collections; +import java.util.Map; +import org.springframework.context.annotation.Bean; +import org.springframework.context.annotation.Configuration; + +@Configuration +public class OpenTelemetryConfig { + + @Bean + public AutoConfigurationCustomizerProvider otelCustomizer() { + return p -> + p.addSpanExporterCustomizer( + (exporter, config) -> { + if (exporter instanceof OtlpHttpSpanExporter) { + return ((OtlpHttpSpanExporter) exporter) + .toBuilder().setHeaders(this::headers).build(); + } + return exporter; + }); + } + + private Map headers() { + return Collections.singletonMap("Authorization", "Bearer " + refreshToken()); + } + + private String refreshToken() { + // e.g. read the token from a kubernetes secret + return "token"; + } +} +``` + #### Resource Providers -The OpenTelemetry Starter includes -[common Resource Providers](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/resources/library) -and the following Spring Boot specific Resource Providers: +The OpenTelemetry Starter includes the same resource providers as the Java +agent: + +- [Common resource providers](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/resources/library) +- [Resource providers that are disabled by default](/docs/languages/java/automatic/configuration/#enable-resource-providers-that-are-disabled-by-default) + +In addition, the OpenTelemetry Starter includes the following Spring Boot +specific resource providers: ##### Distribution Resource Provider @@ -285,79 +365,6 @@ FQN: | `service.name` | `spring.application.name` or `build.version` from `build-info.properties` (see [Service name](#service-name)) | | `service.version` | `build.name` from `build-info.properties` | -##### AWS Resource Provider - -The -[AWS Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/aws-resources) -can be added as a dependency: - -{{< tabpane text=true >}} {{% tab header="Maven (`pom.xml`)" lang=Maven %}} - -```xml - - - io.opentelemetry.contrib - opentelemetry-aws-resources - 1.33.0-alpha - - - com.fasterxml.jackson.core - jackson-core - - - com.squareup.okhttp3 - okhttp - - - - -``` - -{{% /tab %}} {{% tab header="Gradle (`gradle.build`)" lang=Gradle %}} - -```kotlin -implementation("io.opentelemetry.contrib:opentelemetry-aws-resources:1.33.0-alpha") { - exclude("com.fasterxml.jackson.core", "jackson-core") - exclude("com.squareup.okhttp3", "okhttp") -} -``` - -{{% /tab %}} {{< /tabpane>}} - -##### GCP Resource Provider - -The -[GCP Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources) -can be added as a dependency: - -{{< tabpane text=true >}} {{% tab header="Maven (`pom.xml`)" lang=Maven %}} - -```xml - - - io.opentelemetry.contrib - opentelemetry-gcp-resources - 1.33.0-alpha - - - com.fasterxml.jackson.core - jackson-core - - - - -``` - -{{% /tab %}} {{% tab header="Gradle (`gradle.build`)" lang=Gradle %}} - -```kotlin -implementation("io.opentelemetry.contrib:opentelemetry-gcp-resources:1.33.0-alpha") { - exclude("com.fasterxml.jackson.core", "jackson-core") -} -``` - -{{% /tab %}} {{< /tabpane>}} - #### Service name Using these resource providers, the service name is determined by the following @@ -443,26 +450,26 @@ appender in your `logback.xml` or `logback-spring.xml` file: ```xml - - - - %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n - - - - - false - true - true - true - true - * - - - - - + + + + %d{HH:mm:ss.SSS} [%thread] %-5level %logger{36} - %msg%n + + + + + false + true + true + true + true + * + + + + + ``` @@ -476,6 +483,36 @@ supported for spring web versions 3.1+. To learn more about the OpenTelemetry `RestTemplate` interceptor, see [opentelemetry-spring-web-3.1](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-web/spring-web-3.1/library). +The following ways of creating a `RestTemplate` are supported: + +```java +@Bean +public RestTemplate restTemplate() { + return new RestTemplate(); +} +``` + +```java +public MyService(RestTemplateBuilder restTemplateBuilder) { + this.restTemplate = restTemplateBuilder.build(); +} +``` + +The following ways of creating a `RestClient` are supported: + +```java +@Bean +public RestClient restClient() { + return RestClient.create(); +} +``` + +```java +public MyService(RestClient.Builder restClientBuilder) { + this.restClient = restClientBuilder.build(); +} +``` + #### Spring Web MVC Autoconfiguration This feature autoconfigures instrumentation for Spring WebMVC controllers by @@ -498,6 +535,21 @@ processor. This feature is supported for spring webflux versions 5.0+. For details, see [opentelemetry-spring-webflux-5.3](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-webflux/spring-webflux-5.3/library). +The following ways of creating a `WebClient` are supported: + +```java +@Bean +public WebClient webClient() { + return WebClient.create(); +} +``` + +```java +public MyService(WebClient.Builder webClientBuilder) { + this.webClient = webClientBuilder.build(); +} +``` + ### Additional Instrumentations #### JDBC Instrumentation @@ -541,10 +593,10 @@ With the datasource configuration, you need to add the following dependency: ```xml - - io.opentelemetry.instrumentation - opentelemetry-jdbc - + + io.opentelemetry.instrumentation + opentelemetry-jdbc + ``` @@ -565,14 +617,14 @@ You have to add the OpenTelemetry appender to your `log4j2.xml` file: ```xml - - - - - - - - + + + + + + + + ``` diff --git a/content/en/docs/languages/java/instrumentation.md b/content/en/docs/languages/java/instrumentation.md index c4e690ed7f14..23c65b802715 100644 --- a/content/en/docs/languages/java/instrumentation.md +++ b/content/en/docs/languages/java/instrumentation.md @@ -42,6 +42,15 @@ manual instrumentation. You don't have to use the example app: if you want to instrument your own app or library, follow the instructions here to adapt the process to your own code. +### Prerequisites + +For running the example app, ensure that you have the following installed +locally: + +- Java JDK 17+, due to the use of Spring Boot 3. OpenTelemetry Java itself only + [requires Java 8+][java-vers]. +- [Gradle](https://gradle.org/). + ### Dependencies {#example-app-dependencies} To begin, set up an environment in a new directory called `java-simple`. Within @@ -641,7 +650,7 @@ public class Dice { } public Dice(int min, int max) { - this(min, max, OpenTelemetry.noop()) + this(min, max, OpenTelemetry.noop()); } // ... @@ -975,18 +984,16 @@ HTTP headers. ### Context propagation between threads -THe following example demonstrates how to propagate the context between threads: +The following example demonstrates how to propagate the context between threads: ```java io.opentelemetry.context.Context context = io.opentelemetry.context.Context.current(); -Thread thread = new Thread(new Runnable() { +Thread thread = new Thread(context.wrap(new Runnable() { @Override public void run() { - try (Scope scope = context.makeCurrent()) { - // Code for which you want to propagate the context - } + // Code for which you want to propagate the context } -}); +})); thread.start(); ``` @@ -1822,6 +1829,8 @@ io.opentelemetry.sdk.trace.export.BatchSpanProcessor = io.opentelemetry.extensio https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk/trace/src/main/java/io/opentelemetry/sdk/trace/samplers/AlwaysOnSampler.java [httpexchange]: https://docs.oracle.com/javase/8/docs/jre/api/net/httpserver/spec/com/sun/net/httpserver/HttpExchange.html +[java-vers]: + https://github.com/open-telemetry/opentelemetry-java/blob/main/VERSIONING.md#language-version-compatibility [instrumentation library]: /docs/specs/otel/glossary/#instrumentation-library [instrumented library]: /docs/specs/otel/glossary/#instrumented-library [logs bridge API]: /docs/specs/otel/logs/bridge-api diff --git a/content/en/docs/languages/java/libraries.md b/content/en/docs/languages/java/libraries.md index d3192ccd1382..80bf521549f2 100644 --- a/content/en/docs/languages/java/libraries.md +++ b/content/en/docs/languages/java/libraries.md @@ -5,14 +5,13 @@ weight: 40 cSpell:ignore: getenv httpclient println --- -When you develop an app, you use third-party libraries and frameworks to -accelerate your work and avoid duplicated efforts. If you instrument your app -with OpenTelemetry, you don't want to spend additional time on manually adding -traces, logs, and metrics to those libraries and frameworks. - -Use libraries that come with OpenTelemetry support natively or an -[Instrumentation Library](/docs/concepts/instrumentation/libraries/) to generate -telemetry data for a library or framework. +{{% docs/languages/libraries-intro "Java" %}} + +## Use Instrumentation Libraries + +If a library does not come with OpenTelemetry out of the box, you can use +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +in order to generate telemetry data for a library or framework. The Java agent for automatic instrumentation includes instrumentation libraries for many common Java frameworks. Most are turned on by default. If you need to diff --git a/content/en/docs/languages/java/sampling.md b/content/en/docs/languages/java/sampling.md new file mode 100644 index 000000000000..4f6d2ff58be2 --- /dev/null +++ b/content/en/docs/languages/java/sampling.md @@ -0,0 +1,45 @@ +--- +title: Sampling +weight: 80 +--- + +[Sampling](/docs/concepts/sampling/) is a process that restricts the amount of +spans that are generated by a system. Which sampler to use depends on your +needs. In general, decide which sampler to use at the start of a trace and allow +the sampling decision to propagate to other services. + +A sampler can be set on the tracer provider using the `setSampler` method, as +follows: + +```java +import io.opentelemetry.sdk.trace.SdkTracerProvider; +import io.opentelemetry.sdk.trace.samplers.Sampler; + +public class Example { + public static void main(String[] args) { + // Configure the tracer provider with the desired sampler + SdkTracerProvider tracerProvider = SdkTracerProvider.builder() + .setSampler(Sampler.alwaysOn()) // Set to always sample traces + // or + .setSampler(Sampler.alwaysOff()) // Set to never sample traces + // or + .setSampler(Sampler.traceIdRatioBased(0.5)) // Set to sample a fraction of traces + .build(); + } +} +``` + +The `alwaysOn` value means that every span is sampled, while `alwaysOff` means +that no span is sampled. When you’re getting started, or in a development +environment, use `alwaysOn`. + +Other samplers include: + +- `traceIdRatioBased`, which samples a fraction of spans, based on the fraction + given to the sampler. If you set `0.5`, half of all the spans are sampled. +- `parentBased`, which uses the parent span to make sampling decisions, if + present. By default, the tracer provider uses a parentBased sampler with the + `alwaysOn` sampler. + +When in a production environment, consider using the `parentBased` sampler with +the `traceIdRatioBased` sampler. diff --git a/content/en/docs/languages/js/automatic/configuration.md b/content/en/docs/languages/js/automatic/configuration.md index df0c7a12bc06..bae19452406b 100644 --- a/content/en/docs/languages/js/automatic/configuration.md +++ b/content/en/docs/languages/js/automatic/configuration.md @@ -4,6 +4,7 @@ linkTitle: Configuration description: Learn how to configure Automatic Instrumentation for Node.js aliases: [module-config] weight: 10 +cSpell:ignore: serviceinstance --- This module is highly configurable by setting @@ -27,9 +28,11 @@ detectors, or completely disable them: - `host` - `os` - `process` +- `serviceinstance` - `container` - `alibaba` - `aws` +- `azure` - `gcp` - `all` - enables all resource detectors - `none` - disables resource detection @@ -39,3 +42,22 @@ For example, to only enable the `env` and `host` detectors, you can set: ```shell OTEL_NODE_RESOURCE_DETECTORS=env,host ``` + +### Excluding auto-instrumentation + +By default, all +[supported instrumentation libraries](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/metapackages/auto-instrumentations-node/README.md#supported-instrumentations) +are enabled, but you can use the environment variable +`OTEL_NODE_ENABLED_INSTRUMENTATIONS` to enable only certain instrumentations by +providing a comma-separated list of the instrumentation package names without +the `@opentelemetry/instrumentation-` prefix. + +For example, to enable only +[@opentelemetry/instrumentation-http](https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-instrumentation-http) +and +[@opentelemetry/instrumentation-express](https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/opentelemetry-instrumentation-express) +instrumentations: + +```shell +OTEL_NODE_ENABLED_INSTRUMENTATIONS="http,express" +``` diff --git a/content/en/docs/languages/net/automatic/_index.md b/content/en/docs/languages/net/automatic/_index.md index a4aad11c69f9..6737c97b3519 100644 --- a/content/en/docs/languages/net/automatic/_index.md +++ b/content/en/docs/languages/net/automatic/_index.md @@ -235,7 +235,7 @@ You can also use the ## Configuring the agent To see the full range of configuration options, see -[Configuration and settings](./config). +[Configuration and settings](./configuration). ## Log to trace correlation diff --git a/content/en/docs/languages/net/automatic/config.md b/content/en/docs/languages/net/automatic/configuration.md similarity index 99% rename from content/en/docs/languages/net/automatic/config.md rename to content/en/docs/languages/net/automatic/configuration.md index 6a6cc998b8ea..f73c7752952b 100644 --- a/content/en/docs/languages/net/automatic/config.md +++ b/content/en/docs/languages/net/automatic/configuration.md @@ -2,6 +2,7 @@ title: Configuration and settings linkTitle: Configuration weight: 20 +aliases: [config] # prettier-ignore cSpell:ignore: AZUREAPPSERVICE Bitness CLSID CORECLR dylib NETFX PROCESSRUNTIME UNHANDLEDEXCEPTION --- diff --git a/content/en/docs/languages/net/automatic/getting-started.md b/content/en/docs/languages/net/automatic/getting-started.md index 15b04d4fbf23..612dd083c0f3 100644 --- a/content/en/docs/languages/net/automatic/getting-started.md +++ b/content/en/docs/languages/net/automatic/getting-started.md @@ -297,7 +297,7 @@ Value: Sum: 1330.4766000000002 Count: 5 Min: 50.0333 Max: 465.7936 For more: - To configure exporters, samplers, resources and more, see - [Configuration and settings](../config) + [Configuration and settings](../configuration) - See the list of [available instrumentations](../instrumentations) - If you want to combine automatic and manual instrumentation, learn how you [can create custom traces and metrics](../custom) @@ -306,7 +306,7 @@ For more: [traces]: /docs/concepts/signals/traces/ [metrics]: /docs/concepts/signals/metrics/ [logs]: /docs/concepts/signals/logs/ -[configure .NET Automatic Instrumentation]: ../config +[configure .NET Automatic Instrumentation]: ../configuration [console exporter]: https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md#internal-logs [releases]: diff --git a/content/en/docs/languages/net/automatic/instrumentations.md b/content/en/docs/languages/net/automatic/instrumentations.md index 361b5783fbe9..284ed130efc4 100644 --- a/content/en/docs/languages/net/automatic/instrumentations.md +++ b/content/en/docs/languages/net/automatic/instrumentations.md @@ -112,8 +112,11 @@ enabled without using the .NET CLR Profiler by setting the ### Instrumentation options -| Environment variable | Description | Default value | Status | -| --------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | --------------------------------------------------------- | -| `OTEL_DOTNET_AUTO_ENTITYFRAMEWORKCORE_SET_DBSTATEMENT_FOR_TEXT` | Whether the Entity Framework Core instrumentation can pass SQL statements through the `db.statement` attribute. Queries might contain sensitive information. If set to `false`, `db.statement` is recorded only for executing stored procedures. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | -| `OTEL_DOTNET_AUTO_GRAPHQL_SET_DOCUMENT` | Whether the GraphQL instrumentation can pass raw queries through the `graphql.document` attribute. Queries might contain sensitive information. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | -| `OTEL_DOTNET_AUTO_SQLCLIENT_SET_DBSTATEMENT_FOR_TEXT` | Whether the SQL Client instrumentation can pass SQL statements through the `db.statement` attribute. Queries might contain sensitive information. If set to `false`, `db.statement` is recorded only for executing stored procedures. **Not supported on .NET Framework for System.Data.SqlClient.** | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| Environment variable | Description | Default value | Status | +| ----------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | --------------------------------------------------------- | +| `OTEL_DOTNET_AUTO_ENTITYFRAMEWORKCORE_SET_DBSTATEMENT_FOR_TEXT` | Whether the Entity Framework Core instrumentation can pass SQL statements through the `db.statement` attribute. Queries might contain sensitive information. If set to `false`, `db.statement` is recorded only for executing stored procedures. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| `OTEL_DOTNET_AUTO_GRAPHQL_SET_DOCUMENT` | Whether the GraphQL instrumentation can pass raw queries through the `graphql.document` attribute. Queries might contain sensitive information. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| `OTEL_DOTNET_AUTO_SQLCLIENT_SET_DBSTATEMENT_FOR_TEXT` | Whether the SQL Client instrumentation can pass SQL statements through the `db.statement` attribute. Queries might contain sensitive information. If set to `false`, `db.statement` is recorded only for executing stored procedures. **Not supported on .NET Framework for System.Data.SqlClient.** | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| `OTEL_DOTNET_EXPERIMENTAL_ASPNETCORE_DISABLE_URL_QUERY_REDACTION` | Whether the ASP.NET Core instrumentation turns off redaction of the `url.query` attribute value. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| `OTEL_DOTNET_EXPERIMENTAL_HTTPCLIENT_DISABLE_URL_QUERY_REDACTION` | Whether the HTTP client instrumentation turns off redaction of the `url.full` attribute value. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | +| `OTEL_DOTNET_EXPERIMENTAL_ASPNET_DISABLE_URL_QUERY_REDACTION` | Whether the ASP.NET instrumentation turns off redaction of the `url.query` attribute value. | `false` | [Experimental](/docs/specs/otel/versioning-and-stability) | diff --git a/content/en/docs/languages/net/automatic/nuget-packages.md b/content/en/docs/languages/net/automatic/nuget-packages.md index f909d2e310e4..dcaa41b8751d 100644 --- a/content/en/docs/languages/net/automatic/nuget-packages.md +++ b/content/en/docs/languages/net/automatic/nuget-packages.md @@ -46,7 +46,7 @@ you to either add the missing instrumentation package or to skip the instrumentation of the corresponding package: ```terminal -~packages/opentelemetry.autoinstrumentation.buildtasks/1.5.0/build/OpenTelemetry.AutoInstrumentation.BuildTasks.targets(29,5): error : OpenTelemetry.AutoInstrumentation: add a reference to the instrumentation package 'MongoDB.Driver.Core.Extensions.DiagnosticSources' version 1.4.0 or add 'MongoDB.Driver.Core' to the property 'SkippedInstrumentations' to suppress this error. +~packages/opentelemetry.autoinstrumentation.buildtasks/1.6.0/build/OpenTelemetry.AutoInstrumentation.BuildTasks.targets(29,5): error : OpenTelemetry.AutoInstrumentation: add a reference to the instrumentation package 'MongoDB.Driver.Core.Extensions.DiagnosticSources' version 1.4.0 or add 'MongoDB.Driver.Core' to the property 'SkippedInstrumentations' to suppress this error. ``` To resolve the error either add the recommended instrumentation package or skip diff --git a/content/en/docs/languages/net/automatic/troubleshooting.md b/content/en/docs/languages/net/automatic/troubleshooting.md index 9ce563159ab0..618b3a71d919 100644 --- a/content/en/docs/languages/net/automatic/troubleshooting.md +++ b/content/en/docs/languages/net/automatic/troubleshooting.md @@ -16,12 +16,12 @@ Detailed debug logs can help you troubleshoot instrumentation issues, and can be attached to issues in this project to facilitate investigation. To get the detailed logs from the OpenTelemetry .NET Automatic Instrumentation, -set the [`OTEL_LOG_LEVEL`](../config#internal-logs) environment variable to -`debug` before the instrumented process starts. +set the [`OTEL_LOG_LEVEL`](../configuration#internal-logs) environment variable +to `debug` before the instrumented process starts. By default, the library writes the log files under predefined -[locations](../config#internal-logs). If needed, change the default location by -updating the `OTEL_DOTNET_AUTO_LOG_DIRECTORY` environment variable. +[locations](../configuration#internal-logs). If needed, change the default +location by updating the `OTEL_DOTNET_AUTO_LOG_DIRECTORY` environment variable. After obtaining the logs, remove the `OTEL_LOG_LEVEL` environment variable, or set it to less verbose level to avoid unnecessary overhead. @@ -45,7 +45,8 @@ Then restart the application to collect the logs. ### No telemetry is produced There is no telemetry generated. There are no logs in OpenTelemetry .NET -Automatic Instrumentation internal logs [location](../config#internal-logs). +Automatic Instrumentation internal logs +[location](../configuration#internal-logs). It might occur that the .NET Profiler is unable to attach and therefore no logs would be emitted. @@ -59,7 +60,7 @@ When adding the NuGet packages to your project you get an error message similar to: ```txt -Could not install package 'OpenTelemetry.AutoInstrumentation.Runtime.Native 1.5.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. +Could not install package 'OpenTelemetry.AutoInstrumentation.Runtime.Native 1.6.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.7.2', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. ``` The NuGet packages don't support old-style `csproj` projects. Either deploy the @@ -73,8 +74,9 @@ instrumentation globally by setting the environment variables at system or user scope. If the usage of system or user scope is intentional, use the -[`OTEL_DOTNET_AUTO_EXCLUDE_PROCESSES`](../config#global-settings) environment -variables to exclude applications from the automatic instrumentation. +[`OTEL_DOTNET_AUTO_EXCLUDE_PROCESSES`](../configuration#global-settings) +environment variables to exclude applications from the automatic +instrumentation. ### `dotnet` CLI tool is crashing @@ -141,7 +143,7 @@ Find their versions in the following locations: By default, assembly references for .NET Framework applications are redirected during runtime to the versions used by the automatic instrumentation. This behavior can be controlled through the -[`OTEL_DOTNET_AUTO_NETFX_REDIRECT_ENABLED`](../config) setting. +[`OTEL_DOTNET_AUTO_NETFX_REDIRECT_ENABLED`](../configuration) setting. If the application already ships binding redirection for assemblies used by automatic instrumentation this automatic redirection may fail, see diff --git a/content/en/docs/languages/net/exporters.md b/content/en/docs/languages/net/exporters.md index 4e9f20cf541b..1b26686a7b9a 100644 --- a/content/en/docs/languages/net/exporters.md +++ b/content/en/docs/languages/net/exporters.md @@ -5,74 +5,56 @@ weight: 50 {{% docs/languages/exporters/intro dotnet %}} -{{% alert title="Note" color="info" %}} +### Dependencies {#otlp-dependencies} -If you use the OpenTelemetry .NET Automatic Instrumentation for -[automatic instrumentation](/docs/languages/net/automatic) you can learn how to -setup exporters following the -[Configuration Guide](/docs/languages/net/automatic/config) +If you want to send telemetry data to an OTLP endpoint (like the +[OpenTelemetry Collector](#collector-setup), [Jaeger](#jaeger) or +[Prometheus](#prometheus)), you can choose between two different protocols to +transport your data: -{{% /alert %}} - -## Console exporter +- HTTP/protobuf +- gRPC -The console exporter is useful for development and debugging tasks, and is the -simplest to set up. +Start by installing the +[`OpenTelemetry.Exporter.OpenTelemetryProtocol`](https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol/) +package as a dependency for your project: ```sh -dotnet add package OpenTelemetry.Exporter.Console -dotnet add package OpenTelemetry.Extensions.Hosting -``` - -If you're using ASP.NET Core, configure the exporter in your ASP.NET Core -services: - -```csharp -var builder = WebApplication.CreateBuilder(args); - -builder.Services.AddOpenTelemetry().WithTracing(b => -{ - b.AddConsoleExporter() - // The rest of your setup code goes here too -}); -``` - -Otherwise, configure the exporter when creating a tracer provider: - -```csharp -using var tracerProvider = Sdk.CreateTracerProviderBuilder() - .AddConsoleExporter() - - // Other setup code, like setting a resource goes here too - - .Build(); +dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol ``` -## OTLP endpoint - -To send trace data to an OTLP endpoint (like the [collector](/docs/collector) or -Jaeger) you'll want to configure an OTLP exporter that sends to your endpoint. +If you're using ASP.NET Core install the +[`OpenTelemetry.Extensions.Hosting`](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) +package as well: ```sh -dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol dotnet add package OpenTelemetry.Extensions.Hosting ``` -If you're using ASP.NET Core, configure the exporter in your ASP.NET Core -services: +### Usage + +#### ASP.NET Core + +Configure the exporters in your ASP.NET Core services: ```csharp var builder = WebApplication.CreateBuilder(args); builder.Services.AddOpenTelemetry() - .WithTracing(b => - { - b.AddOtlpExporter() - // The rest of your setup code goes here too - }); + .WithTracing(tracing => tracing + // The rest of your setup code goes here + .AddOtlpExporter()) + .WithMetrics(metrics => metrics + // The rest of your setup code goes here + .AddOtlpExporter()); + +builder.Logging.AddOpenTelemetry(logging => { + // The rest of your setup code goes here + logging.AddOtlpExporter(); +}); ``` -This will, by default, send traces using gRPC to , to +This will, by default, send telemetry using gRPC to , to customize this to use HTTP and the protobuf format, you can add options like this: @@ -80,163 +62,175 @@ this: var builder = WebApplication.CreateBuilder(args); builder.Services.AddOpenTelemetry() - .WithTracing(b => -{ - b - .AddOtlpExporter(opt => + .WithTracing(tracing => tracing + // The rest of your setup code goes here + .AddOtlpExporter(options => + { + options.Endpoint = new Uri("your-endpoint-here/v1/traces"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; + })) + .WithMetrics(metrics => metrics + // The rest of your setup code goes here + .AddOtlpExporter(options => + { + options.Endpoint = new Uri("your-endpoint-here/v1/metrics"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; + })); + +builder.Logging.AddOpenTelemetry(logging => { + // The rest of your setup code goes here + logging.AddOtlpExporter(options => { - opt.Endpoint = new Uri("your-endpoint-here/v1/traces"); - opt.Protocol = OtlpExportProtocol.HttpProtobuf; - }) - // The rest of your setup code goes here too + options.Endpoint = new Uri("your-endpoint-here/v1/logs"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; + }); }); ``` -Otherwise, configure the exporter when creating a tracer provider: +#### Non-ASP.NET Core + +Configure the exporter when creating a `TracerProvider`, `MeterProvider` or +`LoggerFactory`: ```csharp -using var tracerProvider = Sdk.CreateTracerProviderBuilder() - .AddOtlpExporter(opt => +var tracerProvider = Sdk.CreateTracerProviderBuilder() + // Other setup code, like setting a resource goes here too + .AddOtlpExporter(options => { - opt.Endpoint = new Uri("your-endpoint-here/v1/traces"); - opt.Protocol = OtlpExportProtocol.HttpProtobuf; + options.Endpoint = new Uri("your-endpoint-here/v1/traces"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; }) + .Build(); +var meterProvider = Sdk.CreateMeterProviderBuilder() // Other setup code, like setting a resource goes here too - + .AddOtlpExporter(options => + { + options.Endpoint = new Uri("your-endpoint-here/v1/metrics"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; + }) .Build(); + +var loggerFactory = LoggerFactory.Create(builder => +{ + builder.AddOpenTelemetry(logging => + { + logging.AddOtlpExporter(options => + { + options.Endpoint = new Uri("your-endpoint-here/v1/logs"); + options.Protocol = OtlpExportProtocol.HttpProtobuf; + }) + }); +}); ``` Use environment variables to set values like headers and an endpoint URL for production. -### Note for .NET Core 3.1 and below and gRPC - -Note: Versions below .NET 6 are not officially supported by -opentelemetry-dotnet, therefore this section is here to help, but may not work -as the library progresses. - -If you're not using ASP.NET Core gRPC and you are running on .NET Core 3.x, -you'll need to add the following at application startup - -```csharp -AppContext.SetSwitch("System.Net.Http.SocketsHttpHandler.Http2UnencryptedSupport", true); -``` +## Console -If you are using .NET 5 or higher, the previous code sample is not required. +### Dependencies -### Jaeger - -To try out the OTLP exporter, you can run -[Jaeger](https://www.jaegertracing.io/) as an OTLP endpoint and for trace -visualization in a docker container: +The console exporter is useful for development and debugging tasks, and is the +simplest to set up. Start by installing the +[`OpenTelemetry.Exporter.Console`](https://www.nuget.org/packages/OpenTelemetry.Exporter.Console/) +package as a dependency for your project: -```shell -docker run -d --name jaeger \ - -e COLLECTOR_OTLP_ENABLED=true \ - -p 16686:16686 \ - -p 4317:4317 \ - -p 4318:4318 \ - jaegertracing/all-in-one:latest +```sh +dotnet add package OpenTelemetry.Exporter.Console ``` -## Zipkin - -If you are using [Zipkin](https://zipkin.io/) to visualize trace data, you'll -need to set it up first. This is how to run it in a docker container: +If you're using ASP.NET Core install the +[`OpenTelemetry.Extensions.Hosting`](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) +package as well: -```shell -docker run --rm -d -p 9411:9411 --name zipkin openzipkin/zipkin +```sh +dotnet add package OpenTelemetry.Extensions.Hosting ``` -Next, install the Zipkin exporter package: +### Usage {#console-usage} -```shell -dotnet add package OpenTelemetry.Exporter.Zipkin -dotnet add package OpenTelemetry.Extensions.Hosting -``` +#### ASP.NET Core {#console-usage-asp-net-core} -If you're using ASP.NET Core, configure the exporter in your ASP.NET Core -services: +Configure the exporter in your ASP.NET Core services: ```csharp var builder = WebApplication.CreateBuilder(args); builder.Services.AddOpenTelemetry() - .WithTracing(b => - { - b.AddZipkinExporter(o => - { - o.Endpoint = new Uri("your-zipkin-uri-here"); - }) - // The rest of your setup code goes here too - }); + .WithTracing(tracing => tracing + // The rest of your setup code goes here + .AddConsoleExporter() + ) + .WithMetrics(metrics => metrics + // The rest of your setup code goes here + .AddConsoleExporter() + ); + +builder.Logging.AddOpenTelemetry(logging => { + // The rest of your setup code goes here + logging.AddConsoleExporter(); +}); ``` -Otherwise, configure the exporter when creating a tracer provider: - -```csharp -using var tracerProvider = Sdk.CreateTracerProviderBuilder() - .AddZipkinExporter(o => - { - o.Endpoint = new Uri("your-zipkin-uri-here"); - }) +#### Non-ASP.NET Core {#console-usage-non-asp-net-core} - // Other setup code, like setting a resource goes here too +Configure the exporter when creating a `TracerProvider`, `MeterProvider` or +`LoggerFactory`: +```csharp +var tracerProvider = Sdk.CreateTracerProviderBuilder() + // The rest of your setup code goes here + .AddConsoleExporter() .Build(); -``` - -## Prometheus (Experimental) -**\*Note:** this is experimental and dependent on the OpenTelemetry -specification to be made stable before it will be a released package. For now, -we recommend using the OTLP exporter and using the OpenTelemetry Collector to -send metrics to Prometheus\* +var meterProvider = Sdk.CreateMeterProviderBuilder() + // The rest of your setup code goes here + .AddConsoleExporter() + .Build(); -If you're using Prometheus to visualize metrics data, you'll need to set it up -first. Here's how to do it using a docker container: +var loggerFactory = LoggerFactory.Create(builder => +{ + builder.AddOpenTelemetry(logging => + { + logging.AddConsoleExporter(); + }); +}); +``` -First, you'll need a `prometheus.yml` file to configure your Prometheus backend, -such as the following: +{{% docs/languages/exporters/jaeger %}} -```yml -global: - scrape_interval: 1s - evaluation_interval: 1s +{{% docs/languages/exporters/prometheus-setup %}} -scrape_configs: - - job_name: prometheus - static_configs: - - targets: [localhost:9090] -``` +### Dependencies {#prometheus-dependencies} -Next, run the following docker command to set up Prometheus: +Install the +[exporter package](https://www.nuget.org/packages/OpenTelemetry.Exporter.Prometheus.AspNetCore) +as a dependency for your application: ```shell -docker run \ - -p 9090:9090 \ - -v ${PWD}/prometheus.yml:/etc/prometheus/prometheus.yml \ - prom/prometheus +dotnet add package OpenTelemetry.Exporter.Prometheus.AspNetCore --version {{% version-from-registry exporter-dotnet-prometheus-aspnetcore %}} ``` -Next, install the Prometheus exporter: - -### ASP.NET +If you're using ASP.NET Core install the +[`OpenTelemetry.Extensions.Hosting`](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) +package as well: -```shell -dotnet add package OpenTelemetry.Exporter.Prometheus.AspNetCore --version 1.4.0-rc.4 +```sh dotnet add package OpenTelemetry.Extensions.Hosting ``` -If you're using ASP.NET Core, configure the exporter in your ASP.NET Core -services: +### Usage {#prometheus-usage} + +#### ASP.NET Core {#prometheus-asp-net-core-usage} + +Configure the exporter in your ASP.NET Core services: ```csharp var builder = WebApplication.CreateBuilder(args); builder.Services.AddOpenTelemetry() - .WithMetrics(b => b.AddPrometheusExporter()); + .WithMetrics(metrics => metrics.AddPrometheusExporter()); ``` You'll then need to add the endpoint so that Prometheus can scrape your site. @@ -254,13 +248,25 @@ app.UseOpenTelemetryPrometheusScrapingEndpoint(); await app.RunAsync(); ``` -### Non-ASP.NET Core +#### Non-ASP.NET Core {#prometheus-non-asp-net-core-usage} + +{{% alert color="warning" title="Warning" %}} + +This component is intended for dev inner-loop, there is no plan to make it +production ready. Production environments should use +[`OpenTelemetry.Exporter.Prometheus.AspNetCore`](#prometheus-asp-net-core-usage), +or a combination of +[`OpenTelemetry.Exporter.OpenTelemetryProtocol`](#aspnet-core) and +[OpenTelemetry Collector](/docs/collector). + +{{% /alert %}} For applications not using ASP.NET Core, you can use the `HttpListener` version -which is available in a different package: +which is available in a +[different package](https://www.nuget.org/packages/OpenTelemetry.Exporter.Prometheus.HttpListener): ```shell -dotnet add package OpenTelemetry.Exporter.Prometheus.HttpListener --version 1.4.0-rc.4 +dotnet add package OpenTelemetry.Exporter.Prometheus.HttpListener --version {{% version-from-registry exporter-dotnet-prometheus-httplistener %}} ``` Then this is setup directly on the `MeterProviderBuilder`: @@ -269,7 +275,7 @@ Then this is setup directly on the `MeterProviderBuilder`: var meterProvider = Sdk.CreateMeterProviderBuilder() .AddMeter(MyMeter.Name) .AddPrometheusHttpListener( - options => options.UriPrefixes = new string[] { "http://localhost:9090/" }) + options => options.UriPrefixes = new string[] { "http://localhost:9464/" }) .Build(); ``` @@ -286,16 +292,54 @@ app.UseOpenTelemetryPrometheusScrapingEndpoint(); Further details on configuring the Prometheus exporter can be found [here](https://github.com/open-telemetry/opentelemetry-dotnet/blob/main/src/OpenTelemetry.Exporter.Prometheus.AspNetCore/README.md). -## Next steps +{{% docs/languages/exporters/zipkin-setup %}} + +### Dependencies {#zipkin-dependencies} + +To send your trace data to [Zipkin](https://zipkin.io/), install the +[exporter package](https://www.nuget.org/packages/OpenTelemetry.Exporter.Zipkin) +as a dependency for your application: + +```shell +dotnet add package OpenTelemetry.Exporter.Zipkin +``` + +If you're using ASP.NET Core install the +[`OpenTelemetry.Extensions.Hosting`](https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting) +package as well: + +```sh +dotnet add package OpenTelemetry.Extensions.Hosting +``` -To ensure you're getting the most data as easily as possible, install -[instrumentation libraries](/docs/languages/net/libraries) to generate -observability data. +### Usage {#zipkin-usage} -Additionally, enriching your codebase with -[manual instrumentation](/docs/languages/net/instrumentation) gives you -customized observability data. +#### ASP.NET Core {#zipkin-asp-net-core-usage} -You can also check the -[automatic instrumentation for .NET](/docs/languages/net/automatic), which is -currently in beta. +Configure the exporter in your ASP.NET Core services: + +```csharp +var builder = WebApplication.CreateBuilder(args); + +builder.Services.AddOpenTelemetry() + .WithTracing(tracing => tracing + // The rest of your setup code goes here + .AddZipkinExporter(options => + { + options.Endpoint = new Uri("your-zipkin-uri-here"); + })); +``` + +#### Non-ASP.NET Core {#zipkin-non-asp-net-core-usage} + +Configure the exporter when creating a tracer provider: + +```csharp +var tracerProvider = Sdk.CreateTracerProviderBuilder() + // The rest of your setup code goes here + .AddZipkinExporter(options => + { + options.Endpoint = new Uri("your-zipkin-uri-here"); + }) + .Build(); +``` diff --git a/content/en/docs/languages/php/instrumentation.md b/content/en/docs/languages/php/instrumentation.md index fa395b75b3d0..f4e70fbfd8b5 100644 --- a/content/en/docs/languages/php/instrumentation.md +++ b/content/en/docs/languages/php/instrumentation.md @@ -404,7 +404,7 @@ class Dice { private function rollOnce() { $result = random_int(1, 6); - return $result + return $result; } } ``` diff --git a/content/en/docs/languages/php/libraries.md b/content/en/docs/languages/php/libraries.md new file mode 100644 index 000000000000..2b21f6f61ad9 --- /dev/null +++ b/content/en/docs/languages/php/libraries.md @@ -0,0 +1,55 @@ +--- +title: Using instrumentation libraries +linkTitle: Libraries +weight: 40 +cSpell:ignore: Packagist +--- + +{{% docs/languages/libraries-intro "PHP" %}} + +## Use instrumentation libraries + +If a library doesn't include OpenTelemetry support, you can use +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +to generate telemetry data for a library or framework. + +The OpenTelemetry PHP extension includes instrumentation libraries for many +common PHP frameworks. For example, +[the Laravel instrumentation](https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/Laravel) +automatically creates [spans](/docs/concepts/signals/traces/#spans) based on the +application activity. + +## Setup + +Each instrumentation library is a Composer package. To install it, run the +following command: + +```sh +php composer.phar install {name-of-instrumentation}:{version-number} +``` + +Where `{name-of-instrumentation}` is the Packagist reference for the specific +instrumentation you want to use. + +You can turn off any instrumentation by adding its identifier to the +`OTEL_PHP_DISABLED_INSTRUMENTATIONS` environment variable. + +## Available instrumentation libraries + +For a list of available instrumentations, see +[OpenTelemetry instrumentation packages](https://packagist.org/search/?query=open-telemetry&tags=instrumentation) +on Packagist. + +## Next steps + +After you've set up instrumentation libraries, you might want to add +[additional instrumentation](/docs/languages/php/instrumentation) to collect +custom telemetry data. + +You might also want to configure an appropriate exporter to +[export your telemetry data](/docs/languages/php/exporters) to one or more +telemetry backends. + +You can also check the +[automatic instrumentation for PHP](/docs/languages/php/automatic) for existing +library instrumentations. diff --git a/content/en/docs/languages/python/libraries.md b/content/en/docs/languages/python/libraries.md new file mode 100644 index 000000000000..faeade39fc33 --- /dev/null +++ b/content/en/docs/languages/python/libraries.md @@ -0,0 +1,110 @@ +--- +title: Using instrumentation libraries +linkTitle: Libraries +weight: 40 +cSpell:ignore: HTTPX httpx instrumentor uninstrument +--- + +{{% docs/languages/libraries-intro "Python" %}} + +## Use instrumentation libraries + +If a library does not ship with native OpenTelemetry support, you can use +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +to generate telemetry data for a library or framework. + +For example, +[the instrumentation library for HTTPX](https://pypi.org/project/opentelemetry-instrumentation-httpx/) +automatically creates [spans](/docs/concepts/signals/traces/#spans) based on +HTTP requests. + +## Setup + +You can install each instrumentation library separately using pip. For example: + +```sh +pip install opentelemetry-instrumentation-{instrumented-library} +``` + +In the previous example, `{instrumented-library}` is the name of the +instrumentation. + +To install a development version, clone or fork the +`opentelemetry-python-contrib` repository and run the following command to do an +editable installation: + +```sh +pip install -e ./instrumentation/opentelemetry-instrumentation-{integration} +``` + +After installation, you will need to initialize the instrumentation library. +Each library typically has its own way to initialize. + +## Example with HTTPX instrumentation + +Here's how you can instrument HTTP requests made using the `httpx` library. + +First, install the instrumentation library using pip: + +```sh +pip install opentelemetry-instrumentation-httpx +``` + +Next, use the instrumentor to automatically trace requests from all clients: + +```python +import httpx +from opentelemetry.instrumentation.httpx import HTTPXClientInstrumentor + +url = "https://some.url/get" +HTTPXClientInstrumentor().instrument() + +with httpx.Client() as client: + response = client.get(url) + +async with httpx.AsyncClient() as client: + response = await client.get(url) +``` + +### Turn off instrumentations + +If needed, you can uninstrument specific clients or all clients using the +`uninstrument_client` method. For example: + +```python +import httpx +from opentelemetry.instrumentation.httpx import HTTPXClientInstrumentor + +HTTPXClientInstrumentor().instrument() +client = httpx.Client() + +# Uninstrument a specific client +HTTPXClientInstrumentor.uninstrument_client(client) + +# Uninstrument all clients +HTTPXClientInstrumentor().uninstrument() +``` + +## Available instrumentation libraries + +A full list of instrumentation libraries produced by OpenTelemetry is available +from the [opentelemetry-python-contrib][] repository. + +You can also find more instrumentations available in the +[registry](/ecosystem/registry/?language=python&component=instrumentation). + +## Next steps + +After you have set up instrumentation libraries, you might want to add your own +[instrumentation](/docs/languages/python/instrumentation) to your code, to +collect custom telemetry data. + +You might also want to configure an appropriate exporter to +[export your telemetry data](/docs/languages/python/exporters) to one or more +telemetry backends. + +You can also check the +[automatic instrumentation for Python](/docs/languages/python/automatic). + +[opentelemetry-python-contrib]: + https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation#readme diff --git a/content/en/docs/languages/rust/getting-started.md b/content/en/docs/languages/rust/getting-started.md index 5b3b10ee21e7..019b27c81fc4 100644 --- a/content/en/docs/languages/rust/getting-started.md +++ b/content/en/docs/languages/rust/getting-started.md @@ -109,7 +109,8 @@ Stdout Exporter [`opentelemetry-stdout`](https://crates.io/crates/opentelemetry-stdout): ```toml -opentelemetry = { version = "{{% version-from-registry otel-rust %}}", features = ["trace"] } +opentelemetry = "{{% version-from-registry otel-rust %}}" +opentelemetry_sdk = "{{% version-from-registry otel-rust-sdk %}}" opentelemetry-stdout = { version = "{{% version-from-registry exporter-rust-stdout %}}", features = ["trace"] } ``` @@ -123,8 +124,9 @@ use rand::Rng; use std::{convert::Infallible, net::SocketAddr}; use opentelemetry::global::ObjectSafeSpan; use opentelemetry::trace::{SpanKind, Status}; -use opentelemetry::sdk::trace::TracerProvider; -use opentelemetry::{global, sdk::propagation::TraceContextPropagator, trace::Tracer}; +use opentelemetry::{global, trace::Tracer}; +use opentelemetry_sdk::propagation::TraceContextPropagator; +use opentelemetry_sdk::trace::TracerProvider; use opentelemetry_stdout::SpanExporter; async fn handle(req: Request) -> Result, Infallible> { diff --git a/content/en/docs/languages/swift/libraries.md b/content/en/docs/languages/swift/libraries.md index 75ab8c8a3311..1fe339be9f1b 100644 --- a/content/en/docs/languages/swift/libraries.md +++ b/content/en/docs/languages/swift/libraries.md @@ -1,15 +1,29 @@ --- title: Instrumentation Libraries linkTitle: Libraries -description: How to use Swift instrumentation libraries weight: 40 cSpell:ignore: darwin inout iphone NSURL wifi --- -OpenTelemetry-Swift provides several instrumentation libraries that generate -instrumentation for you when they're installed and initialized. +{{% docs/languages/libraries-intro "Swift" %}} + +## Use instrumentation libraries + +OpenTelemetry-Swift provides several +[instrumentation libraries](/docs/specs/otel/glossary/#instrumentation-library) +that generate instrumentation for you when they're installed and initialized. + +For example, +[the NSURLSession instrumentation](https://github.com/open-telemetry/opentelemetry-swift/tree/main/Sources/Instrumentation/URLSession) +automatically creates [spans](/docs/concepts/signals/traces/#spans) for all +network requests made with NSURLSessions. + +## Setup + +All instrumentation libraries are available in OpenTelemetry Swift. To turn on +an instrumentation, follow its usage instructions. ## `SDKResourceExtension` @@ -57,7 +71,7 @@ values to the appropriate | `os.version` | `15.4.0` | `ProcessInfo.processInfo.operatingSystemVersion` | | `os.description` | `iOS Version 15.4 (Build 19E240)` | A combination of os name, version and build. | -## `NSURLSession` Instrumentation +## `NSURLSession` instrumentation This instrumentation creates spans for all network requests made with NSURLSessions. It also injects distributed tracing headers in instrumented @@ -147,10 +161,26 @@ events. This functionality is shown in `Simple Exporter` example. ### Usage -Just add SignpostIntegration as any other Span Processor (see the +Add SignpostIntegration as any other Span Processor (see the [manual instrumentation](../instrumentation/)) docs for details on configuring your providers: ```swift OpenTelemetry.instance.tracerProvider.addSpanProcessor(SignPostIntegration()) ``` + +## Available instrumentation libraries + +A full list of instrumentation libraries produced by OpenTelemetry is available +from the +[opentelemetry-swift](https://github.com/open-telemetry/opentelemetry-swift/tree/main/Sources/Instrumentation) +repository. + +You can also find more instrumentations available in the +[registry](/ecosystem/registry/?language=swift&component=instrumentation). + +## Next steps + +After you have set up instrumentation libraries, you might want to add your own +[instrumentation](/docs/languages/swift/instrumentation) to your code, to +collect custom telemetry data. diff --git a/content/en/ecosystem/registry/_index.md b/content/en/ecosystem/registry/_index.md index e3e00247be74..0b671e5499d2 100644 --- a/content/en/ecosystem/registry/_index.md +++ b/content/en/ecosystem/registry/_index.md @@ -15,7 +15,7 @@ aliases: [/registry/*] type: default layout: registry outputs: [html, json] -body_class: registry +body_class: registry td-content weight: 20 --- diff --git a/content/en/status.md b/content/en/status.md index 55aac19db39f..a8b214215edf 100644 --- a/content/en/status.md +++ b/content/en/status.md @@ -36,6 +36,15 @@ core collector components currently have mixed stability documented in its `README.md`. You can find a list of all available collector components in the [registry](/ecosystem/registry/?language=collector). +## Kubernetes Operator + +The OpenTelemetry Operator status is +[mixed](/docs/specs/otel/document-status/#mixed), since it deploys components of +differing statuses. + +The Operator itself is in a [mixed](/docs/specs/otel/document-status/#mixed) +state with components in `v1alpha1` and `v1beta1` states. + ## Specifications For the development status, or maturity level, of the diff --git a/content/zh/_index.md b/content/zh/_index.md new file mode 100644 index 000000000000..f762389978f9 --- /dev/null +++ b/content/zh/_index.md @@ -0,0 +1,89 @@ +--- +title: OpenTelemetry +description: >- + 高质量、普遍适用和可移植的遥测助你实现有效的可观测 +show_banner: true +developer_note: + 下文所用的 blocks/cover 短代码将使用文件名中包含 "background" + 的图像文件作为背景图。 +cascade: + draft: true +--- + +
+ +{{< blocks/cover image_anchor="top" height="max" color="primary" >}} + + +![OpenTelemetry](/img/logos/opentelemetry-horizontal-color.svg) +{.otel-logo} + + +{{% param description %}} +{.display-6} + +
+ +- [了解更多](/docs/what-is-opentelemetry/) +- [尝试 Demo](/docs/demo/) +- [探索集成组件](/ecosystem/integrations) + +
+ +
+为各种角色定制的入门指南 +
+
+ +- [开发人员](/docs/getting-started/dev/) +- [运维人员](/docs/getting-started/ops/) + +
+{{< /blocks/cover >}} + +{{% blocks/lead color="white" %}} + +OpenTelemetry 是各类 API、SDK 和工具形成的集合。可用于插桩、生成、采集和导出遥测数据（链路、指标和日志），帮助你分析软件的性能和行为。 + +> OpenTelemetry 在[多种编程语言](/docs/languages/)均达到 **GA** 级别，普适性很高。 + +{{% /blocks/lead %}} + +{{% blocks/section color="dark" type="row" %}} + +{{% blocks/feature icon="fas fa-chart-line" title="链路、指标、日志" %}} + +从你的服务和软件中生成并采集遥测数据，然后将其转发给各种分析工具。 + +{{% /blocks/feature %}} + +{{% blocks/feature icon="fas fa-magic" title="现成的插桩支持" %}} + +OpenTelemetry 与流行的库和框架集成，例如 [Spring](https://spring.io)、 +[ASP.NET Core](https://docs.microsoft.com/aspnet/core)、 +[Express](https://expressjs.com)、 [Quarkus](https://quarkus.io) 等等！ +安装和集成可能只需要几行代码。 + +{{% /blocks/feature %}} + +{{% blocks/feature icon="fab fa-github" title="开源、厂商中立" %}} + +OpenTelemetry 是 100% 免费和开源的， +得到了可观测性领域[众多行业领导者](/ecosystem/vendors/)的采用和支持。 + +{{% /blocks/feature %}} + +{{% /blocks/section %}} + +{{% blocks/section color="secondary" type="cncf" %}} + +**OpenTelemetry 是一个 [CNCF][] [孵化级][]项目**。
这个项目是由 +OpenTracing 和 OpenCensus 项目合并而诞生的。 + +[![CNCF logo][]][cncf] + +[cncf]: https://cncf.io +[cncf logo]: /img/logos/cncf-white.svg +[孵化级]: https://www.cncf.io/projects/ + +{{% /blocks/section %}} diff --git a/data/ecosystem/distributions.yaml b/data/ecosystem/distributions.yaml index a9f73c0a941d..f3996d60753f 100644 --- a/data/ecosystem/distributions.yaml +++ b/data/ecosystem/distributions.yaml @@ -83,3 +83,19 @@ url: https://github.com/signalfx/splunk-otel-go docsUrl: https://docs.splunk.com/observability/en/gdi/get-data-in/application/go/get-started.html components: [Go] +- name: Azure Monitor Distribution of OpenTelemetry ASP.NET Core + url: https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.OpenTelemetry.AspNetCore + docsUrl: https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable?tabs=aspnetcore + components: [.NET] +- name: Azure Monitor Distribution of OpenTelemetry Java + url: https://github.com/microsoft/ApplicationInsights-Java + docsUrl: https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable?tabs=java + components: [Java] +- name: Azure Monitor Distribution of OpenTelemetry Node.js + url: https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry + docsUrl: https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable?tabs=nodejs + components: [Node] +- name: Azure Monitor Distribution of OpenTelemetry Python + url: https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-opentelemetry + docsUrl: https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable?tabs=python + components: [Python] diff --git a/data/ecosystem/integrations.yaml b/data/ecosystem/integrations.yaml index 9af287587aa2..c91395d9563e 100644 --- a/data/ecosystem/integrations.yaml +++ b/data/ecosystem/integrations.yaml @@ -1,4 +1,4 @@ -# cSpell:ignore containerd buildx Quarkus Cerbos flagd flipt KEDA Kyverno Dapr rustup GORM Otterize Dubbo Microcks +# cSpell:ignore containerd buildx Quarkus Cerbos flagd flipt KEDA Kyverno Dapr rustup GORM Otterize Dubbo Microcks Kuma - name: containerd url: https://containerd.io/ docsUrl: https://github.com/containerd/containerd/blob/main/docs/tracing.md @@ -18,6 +18,7 @@ url: https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/index.html docsUrl: https://www.elastic.co/guide/en/elasticsearch/client/java-api-client/current/opentelemetry.html components: [Java] + native: true # Elasticsearch Java API Client provides a native integration of the OpenTelemetry API oss: true - name: Kubernetes url: https://kubernetes.io/ @@ -201,3 +202,28 @@ docsUrl: https://github.com/fluentci-io/fluentci-engine#-opentelemetry-tracing components: [Rust] oss: true +- name: KrakenD API Gateway + url: https://www.krakend.io + docsUrl: https://www.krakend.io/docs/telemetry/opentelemetry/ + components: [Go] + oss: true +- name: Azure SDKs + url: https://github.com/Azure/azure-sdk-for-net + docsUrl: https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable + components: [.NET] + oss: true +- name: MassTransit .NET client + url: https://github.com/MassTransit/MassTransit + docsUrl: https://masstransit.io/documentation/configuration/observability + components: [.NET] + oss: true +- name: Kuma + url: https://kuma.io/ + docsUrl: https://kuma.io/docs/2.7.x/guides/otel-metrics/ + components: [Go] + oss: true +- name: Kong Mesh + url: https://konghq.com/products/kong-mesh + docsUrl: https://docs.konghq.com/mesh/latest/guides/otel-metrics/ + components: [Go] + oss: false diff --git a/data/ecosystem/vendors.yaml b/data/ecosystem/vendors.yaml index 2c9b001963ee..1579c7ebc4a4 100644 --- a/data/ecosystem/vendors.yaml +++ b/data/ecosystem/vendors.yaml @@ -22,6 +22,12 @@ contact: oss: false commercial: true +- name: Axiom + nativeOTLP: true + url: https://axiom.co/docs/send-data/opentelemetry + contact: https://axiom.co/contact + oss: false + commercial: true - name: Azure nativeOTLP: false url: https://docs.microsoft.com/azure/azure-monitor/app/opentelemetry-overview @@ -164,8 +170,8 @@ commercial: true - name: ServiceNow Cloud Observability (Lightstep) nativeOTLP: true - url: https://github.com/lightstep?q=launcher - contact: + url: https://docs.lightstep.com/docs/about-sending-data + contact: https://github.com/cartersocha oss: false commercial: true - name: LogicMonitor @@ -234,6 +240,12 @@ contact: skotagiri@opentext.com oss: false commercial: true +- name: OpenLIT + nativeOTLP: false + url: https://docs.openlit.io/ + contact: contact@openlit.io + oss: true + commercial: false - name: Oracle nativeOTLP: true url: https://docs.oracle.com/en-us/iaas/application-performance-monitoring/doc/configure-open-source-tracing-systems.html#GUID-4D941163-F357-4839-8B06-688876D4C61F @@ -308,9 +320,9 @@ commercial: true - name: Uptrace nativeOTLP: true - url: https://uptrace.dev + url: https://uptrace.dev/get/open-source-apm.html contact: - oss: false + oss: true commercial: true - name: Apache SkyWalking nativeOTLP: true @@ -393,7 +405,7 @@ commercial: true - name: Embrace nativeOTLP: true - url: 'https://github.com/embrace-io/embrace-apple-sdk/blob/main/GETTING_STARTED.md#exporting-logs-and-traces-to-opentelemetry-vendors' + url: 'https://embrace.io/opentelemetry-for-mobile/' contact: 'product@embrace.io' oss: true commercial: true diff --git a/data/instrumentation.yaml b/data/instrumentation.yaml index ad6288e0161d..452ac8ed381a 100644 --- a/data/instrumentation.yaml +++ b/data/instrumentation.yaml @@ -26,7 +26,7 @@ go: status: traces: stable metrics: stable - logs: in development + logs: alpha java: name: Java status: diff --git a/data/registry/collector-builder.yml b/data/registry/collector-builder.yml index ba723d257878..a06eac63029e 100644 --- a/data/registry/collector-builder.yml +++ b/data/registry/collector-builder.yml @@ -17,5 +17,5 @@ createdAt: 2023-12-18 package: registry: go name: go.opentelemetry.io/collector/cmd/builder - version: v0.98.0 + version: v0.100.0 quickInstall: false diff --git a/data/registry/collector-exporter-alertmanager.yml b/data/registry/collector-exporter-alertmanager.yml index 3b03b4214966..fb749d0f376c 100644 --- a/data/registry/collector-exporter-alertmanager.yml +++ b/data/registry/collector-exporter-alertmanager.yml @@ -17,7 +17,7 @@ authors: package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/alertmanagerexporter - version: v0.98.0 + version: v0.100.0 urls: repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/alertmanagerexporter createdAt: 2023-12-05 diff --git a/data/registry/collector-exporter-alibaba-cloud-log-service.yml b/data/registry/collector-exporter-alibaba-cloud-log-service.yml index 9657a2af2be2..0d39d2a1ffce 100644 --- a/data/registry/collector-exporter-alibaba-cloud-log-service.yml +++ b/data/registry/collector-exporter-alibaba-cloud-log-service.yml @@ -17,4 +17,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/alibabacloudlogserviceexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-aws-xray.yml b/data/registry/collector-exporter-aws-xray.yml index 94b874128786..84b41357d7ba 100644 --- a/data/registry/collector-exporter-aws-xray.yml +++ b/data/registry/collector-exporter-aws-xray.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsxrayexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-awscloudwatchlogs.yml b/data/registry/collector-exporter-awscloudwatchlogs.yml index 5f107a6a8a98..430c5879de33 100644 --- a/data/registry/collector-exporter-awscloudwatchlogs.yml +++ b/data/registry/collector-exporter-awscloudwatchlogs.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awscloudwatchlogsexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-awsemf.yml b/data/registry/collector-exporter-awsemf.yml index 40c0cf3ffc82..e1a05117f753 100644 --- a/data/registry/collector-exporter-awsemf.yml +++ b/data/registry/collector-exporter-awsemf.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awsemfexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-awss3.yml b/data/registry/collector-exporter-awss3.yml index 24d784fe9ae9..4a6c07db1f04 100644 --- a/data/registry/collector-exporter-awss3.yml +++ b/data/registry/collector-exporter-awss3.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/awss3exporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-azure-monitor.yml b/data/registry/collector-exporter-azure-monitor.yml index c1540aba1fa6..45585f7c72a0 100644 --- a/data/registry/collector-exporter-azure-monitor.yml +++ b/data/registry/collector-exporter-azure-monitor.yml @@ -9,11 +9,11 @@ tags: license: Apache 2.0 description: The Azure Monitor Exporter for the OpenTelemetry Collector. authors: - - name: Microsoft + - name: OpenTelemetry Authors urls: repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/azuremonitorexporter createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azuremonitorexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-azuredataexplorer.yml b/data/registry/collector-exporter-azuredataexplorer.yml index 8bcb0a5b4b69..9116700115af 100644 --- a/data/registry/collector-exporter-azuredataexplorer.yml +++ b/data/registry/collector-exporter-azuredataexplorer.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azuredataexplorerexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-carbon.yml b/data/registry/collector-exporter-carbon.yml index 11e7a2e43eeb..7e4ceb050693 100644 --- a/data/registry/collector-exporter-carbon.yml +++ b/data/registry/collector-exporter-carbon.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/carbonexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-cassandra.yml b/data/registry/collector-exporter-cassandra.yml index ee69a5bb1fa2..280422071cc2 100644 --- a/data/registry/collector-exporter-cassandra.yml +++ b/data/registry/collector-exporter-cassandra.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/cassandraexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-clickhouse.yml b/data/registry/collector-exporter-clickhouse.yml index c9ee12261d12..576a6193e176 100644 --- a/data/registry/collector-exporter-clickhouse.yml +++ b/data/registry/collector-exporter-clickhouse.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/clickhouseexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-coralogix.yml b/data/registry/collector-exporter-coralogix.yml index 6e2c6f1a4e3d..cbd423f8f5c2 100644 --- a/data/registry/collector-exporter-coralogix.yml +++ b/data/registry/collector-exporter-coralogix.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/coralogixexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-datadog.yml b/data/registry/collector-exporter-datadog.yml index d15fcb1c744a..f2e392974be0 100644 --- a/data/registry/collector-exporter-datadog.yml +++ b/data/registry/collector-exporter-datadog.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/datadogexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-dataset.yml b/data/registry/collector-exporter-dataset.yml index 37cbe7704108..031bec57e38c 100644 --- a/data/registry/collector-exporter-dataset.yml +++ b/data/registry/collector-exporter-dataset.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/datasetexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-debug.yml b/data/registry/collector-exporter-debug.yml index 022d5f0bed4f..45db44b57d0f 100644 --- a/data/registry/collector-exporter-debug.yml +++ b/data/registry/collector-exporter-debug.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: go.opentelemetry.io/collector/exporter/debugexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-dynatrace.yml b/data/registry/collector-exporter-dynatrace.yml deleted file mode 100644 index 67b547bd3a1c..000000000000 --- a/data/registry/collector-exporter-dynatrace.yml +++ /dev/null @@ -1,19 +0,0 @@ -# cSpell:ignore dynatraceexporter -title: Dynatrace Collector Exporter -registryType: exporter -language: collector -tags: - - go - - exporter - - collector -license: Apache 2.0 -description: The Dynatrace Exporter for the OpenTelemetry Collector. -authors: - - name: Dynatrace -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/dynatraceexporter -createdAt: 2020-06-06 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/dynatraceexporter - version: v0.98.0 diff --git a/data/registry/collector-exporter-elasticsearch.yml b/data/registry/collector-exporter-elasticsearch.yml index c5be72f7dedc..01830ef7081c 100644 --- a/data/registry/collector-exporter-elasticsearch.yml +++ b/data/registry/collector-exporter-elasticsearch.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/elasticsearchexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-f5cloud.yml b/data/registry/collector-exporter-f5cloud.yml deleted file mode 100644 index fe53131f8e2f..000000000000 --- a/data/registry/collector-exporter-f5cloud.yml +++ /dev/null @@ -1,19 +0,0 @@ -# cSpell:ignore f5cloudexporter -title: F5 Cloud Exporter -registryType: exporter -language: collector -tags: - - go - - exporter - - collector -license: Apache 2.0 -description: The OpenTelemetry Collector Exporter for F5 Cloud -authors: - - name: F5 -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/f5cloudexporter -createdAt: 2020-10-22 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/f5cloudexporter - version: v0.95.0 diff --git a/data/registry/collector-exporter-file.yml b/data/registry/collector-exporter-file.yml index 0e2395ba0147..05d7a8a61faf 100644 --- a/data/registry/collector-exporter-file.yml +++ b/data/registry/collector-exporter-file.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/fileexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-googlecloud.yml b/data/registry/collector-exporter-googlecloud.yml index 2232dd9832a2..eac0d4d1bfeb 100644 --- a/data/registry/collector-exporter-googlecloud.yml +++ b/data/registry/collector-exporter-googlecloud.yml @@ -17,4 +17,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlecloudexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-googlecloudpubsub.yml b/data/registry/collector-exporter-googlecloudpubsub.yml index 54d214ff028a..f59d9f48b98f 100644 --- a/data/registry/collector-exporter-googlecloudpubsub.yml +++ b/data/registry/collector-exporter-googlecloudpubsub.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlecloudpubsubexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-googlemanagedprometheus.yml b/data/registry/collector-exporter-googlemanagedprometheus.yml index 357307ef99cc..c5fef07b1730 100644 --- a/data/registry/collector-exporter-googlemanagedprometheus.yml +++ b/data/registry/collector-exporter-googlemanagedprometheus.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/googlemanagedprometheusexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-honeycombmarker.yml b/data/registry/collector-exporter-honeycombmarker.yml index 755eac5d2086..1afc0a544dca 100644 --- a/data/registry/collector-exporter-honeycombmarker.yml +++ b/data/registry/collector-exporter-honeycombmarker.yml @@ -18,4 +18,4 @@ createdAt: 2023-10-17 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/honeycombmarkerexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-influxdb.yml b/data/registry/collector-exporter-influxdb.yml index 4ba596c1c461..91e83d076748 100644 --- a/data/registry/collector-exporter-influxdb.yml +++ b/data/registry/collector-exporter-influxdb.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/influxdbexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-instana.yml b/data/registry/collector-exporter-instana.yml index 2514e99d1d08..f094a038a4f1 100644 --- a/data/registry/collector-exporter-instana.yml +++ b/data/registry/collector-exporter-instana.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/instanaexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-kafka.yml b/data/registry/collector-exporter-kafka.yml index 1c463ea8c762..6604cadcac1f 100644 --- a/data/registry/collector-exporter-kafka.yml +++ b/data/registry/collector-exporter-kafka.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kafkaexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-kinetica.yml b/data/registry/collector-exporter-kinetica.yml index 119612973b19..bb9110da9787 100644 --- a/data/registry/collector-exporter-kinetica.yml +++ b/data/registry/collector-exporter-kinetica.yml @@ -18,4 +18,4 @@ createdAt: 2023-09-19 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/kineticaexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-load-balancing.yml b/data/registry/collector-exporter-load-balancing.yml index 28789fa16ca2..a30461dfde5e 100644 --- a/data/registry/collector-exporter-load-balancing.yml +++ b/data/registry/collector-exporter-load-balancing.yml @@ -16,4 +16,4 @@ createdAt: 2020-10-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/loadbalancingexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-logicmonitor.yml b/data/registry/collector-exporter-logicmonitor.yml index 7906cea580ac..cb1158356321 100644 --- a/data/registry/collector-exporter-logicmonitor.yml +++ b/data/registry/collector-exporter-logicmonitor.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/logicmonitorexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-logzio.yml b/data/registry/collector-exporter-logzio.yml index 0c3fd0b39030..b02138382b36 100644 --- a/data/registry/collector-exporter-logzio.yml +++ b/data/registry/collector-exporter-logzio.yml @@ -16,4 +16,4 @@ createdAt: 2020-10-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/logzioexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-loki.yml b/data/registry/collector-exporter-loki.yml index d02fc3bb16be..c7c78a05b9f3 100644 --- a/data/registry/collector-exporter-loki.yml +++ b/data/registry/collector-exporter-loki.yml @@ -16,4 +16,4 @@ createdAt: 2020-10-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/lokiexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-mezmo.yml b/data/registry/collector-exporter-mezmo.yml index fa1422cd8e94..22d65c5910e5 100644 --- a/data/registry/collector-exporter-mezmo.yml +++ b/data/registry/collector-exporter-mezmo.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/mezmoexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-nop.yml b/data/registry/collector-exporter-nop.yml new file mode 100644 index 000000000000..2403269995c8 --- /dev/null +++ b/data/registry/collector-exporter-nop.yml @@ -0,0 +1,22 @@ +# cSpell:ignore nopexporter +title: No-op Exporter +registryType: exporter +language: collector +tags: + - nop + - exporter + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/nopexporter +license: Apache 2.0 +description: + Serves as a placeholder exporter in a pipeline. This can be useful if you want + to e.g. start a Collector with only extensions enabled, or for testing + Collector pipeline throughput without worrying about an exporter. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: go.opentelemetry.io/collector/exporter/nopexporter + version: v0.100.0 diff --git a/data/registry/collector-exporter-opencensus.yml b/data/registry/collector-exporter-opencensus.yml index 6c3a4e0c9fb4..3ac6d4a3616b 100644 --- a/data/registry/collector-exporter-opencensus.yml +++ b/data/registry/collector-exporter-opencensus.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/opencensusexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-opensearch.yml b/data/registry/collector-exporter-opensearch.yml index 6e7021d266f9..a20273831cd6 100644 --- a/data/registry/collector-exporter-opensearch.yml +++ b/data/registry/collector-exporter-opensearch.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/opensearchexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-otelarrow.yml b/data/registry/collector-exporter-otelarrow.yml index c5d1e42ddb37..6c78235842e4 100644 --- a/data/registry/collector-exporter-otelarrow.yml +++ b/data/registry/collector-exporter-otelarrow.yml @@ -21,4 +21,4 @@ createdAt: 2024-02-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/otelarrowexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-otlp.yml b/data/registry/collector-exporter-otlp.yml index 97ac21e5c046..65687631983e 100644 --- a/data/registry/collector-exporter-otlp.yml +++ b/data/registry/collector-exporter-otlp.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: go.opentelemetry.io/collector/exporter/otlpexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-prometheus-remote-write.yml b/data/registry/collector-exporter-prometheus-remote-write.yml index 33ffe11fe1f9..186fab9cc8b1 100644 --- a/data/registry/collector-exporter-prometheus-remote-write.yml +++ b/data/registry/collector-exporter-prometheus-remote-write.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusremotewriteexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-prometheus.yml b/data/registry/collector-exporter-prometheus.yml index 3410a3c45f4d..ec38a728cafa 100644 --- a/data/registry/collector-exporter-prometheus.yml +++ b/data/registry/collector-exporter-prometheus.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/prometheusexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-pulsar.yml b/data/registry/collector-exporter-pulsar.yml index 6692ef2711ab..2ce26065ed9b 100644 --- a/data/registry/collector-exporter-pulsar.yml +++ b/data/registry/collector-exporter-pulsar.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/pulsarexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-rabbitmq.yml b/data/registry/collector-exporter-rabbitmq.yml new file mode 100644 index 000000000000..2d132b78e73a --- /dev/null +++ b/data/registry/collector-exporter-rabbitmq.yml @@ -0,0 +1,20 @@ +# cSpell:ignore rabbitmq amqp rabbitmqexporter +title: RabbitMQ Exporter +registryType: exporter +language: collector +tags: + - rabbitmq + - exporter + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/rabbitmqexporter +license: Apache 2.0 +description: + Exports metrics, traces, and logs to RabbitMQ using the AMQP 0.9.1 protocol +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/rabbitmqexporter + version: v0.100.0 diff --git a/data/registry/collector-exporter-sapm.yml b/data/registry/collector-exporter-sapm.yml index 4238de45e2e4..1e2717df75ed 100644 --- a/data/registry/collector-exporter-sapm.yml +++ b/data/registry/collector-exporter-sapm.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-sentry.yml b/data/registry/collector-exporter-sentry.yml index 5f3b2fa2cd14..11818b1edba9 100644 --- a/data/registry/collector-exporter-sentry.yml +++ b/data/registry/collector-exporter-sentry.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sentryexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-signalfx.yml b/data/registry/collector-exporter-signalfx.yml index 6f40b4b8aa19..4b52f4100a8e 100644 --- a/data/registry/collector-exporter-signalfx.yml +++ b/data/registry/collector-exporter-signalfx.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/signalfxexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-skywalking.yml b/data/registry/collector-exporter-skywalking.yml index 7efb79c2b518..f401eac3f68f 100644 --- a/data/registry/collector-exporter-skywalking.yml +++ b/data/registry/collector-exporter-skywalking.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/skywalkingexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-splunk-hec.yml b/data/registry/collector-exporter-splunk-hec.yml index e899cde6cf7a..de7f0966e697 100644 --- a/data/registry/collector-exporter-splunk-hec.yml +++ b/data/registry/collector-exporter-splunk-hec.yml @@ -18,4 +18,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/splunkhecexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-splunk-sapm.yml b/data/registry/collector-exporter-splunk-sapm.yml index e9a0734f5014..be0b758779a7 100644 --- a/data/registry/collector-exporter-splunk-sapm.yml +++ b/data/registry/collector-exporter-splunk-sapm.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-sumologic.yml b/data/registry/collector-exporter-sumologic.yml index 2d1884918ba8..a317dee2d664 100644 --- a/data/registry/collector-exporter-sumologic.yml +++ b/data/registry/collector-exporter-sumologic.yml @@ -16,4 +16,4 @@ createdAt: 2020-10-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sumologicexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-syslog.yml b/data/registry/collector-exporter-syslog.yml index 9ea8880badd8..20f48d392e37 100644 --- a/data/registry/collector-exporter-syslog.yml +++ b/data/registry/collector-exporter-syslog.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/syslogexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-tanzu-observability.yml b/data/registry/collector-exporter-tanzu-observability.yml deleted file mode 100644 index f1d70e4d628e..000000000000 --- a/data/registry/collector-exporter-tanzu-observability.yml +++ /dev/null @@ -1,20 +0,0 @@ -# cSpell:ignore tanzu tanzuobservabilityexporter -title: Tanzu Observability Collector Traces Exporter -registryType: exporter -language: collector -tags: - - go - - exporter - - collector -license: Apache 2.0 -description: - The Tanzu Observability (Wavefront) Exporter for the OpenTelemetry Collector. -authors: - - name: Tanzu Observability -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/tanzuobservabilityexporter -createdAt: 2021-05-27 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/tanzuobservabilityexporter - version: v0.91.0 diff --git a/data/registry/collector-exporter-tencentcloudlogservice.yml b/data/registry/collector-exporter-tencentcloudlogservice.yml index 0bd6550520a8..3f473416de5d 100644 --- a/data/registry/collector-exporter-tencentcloudlogservice.yml +++ b/data/registry/collector-exporter-tencentcloudlogservice.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-27 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/tencentcloudlogserviceexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-exporter-zipkin.yml b/data/registry/collector-exporter-zipkin.yml index b4c286caa8ca..28e0307262ed 100644 --- a/data/registry/collector-exporter-zipkin.yml +++ b/data/registry/collector-exporter-zipkin.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/zipkinexporter - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-ack.yml b/data/registry/collector-extension-ack.yml new file mode 100644 index 000000000000..7eca5ba99930 --- /dev/null +++ b/data/registry/collector-extension-ack.yml @@ -0,0 +1,21 @@ +# cSpell:ignore acking ackextension +title: Ack Extension +registryType: extension +language: collector +tags: + - ack + - extension + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/ackextension +license: Apache 2.0 +description: + This extension allows acking of data upon successful processing. The upstream + agent can choose to send event again if ack fails. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/ackextension + version: v0.100.0 diff --git a/data/registry/collector-extension-asapauth.yml b/data/registry/collector-extension-asapauth.yml index 11589dc6843b..db06b81118ee 100644 --- a/data/registry/collector-extension-asapauth.yml +++ b/data/registry/collector-extension-asapauth.yml @@ -19,4 +19,4 @@ createdAt: 2022-11-07 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/asapauthextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-basicauth.yml b/data/registry/collector-extension-basicauth.yml index 5f5a7c33cb44..b9d31bba856c 100644 --- a/data/registry/collector-extension-basicauth.yml +++ b/data/registry/collector-extension-basicauth.yml @@ -19,4 +19,4 @@ createdAt: 2022-11-07 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/basicauthextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-bearertokenauth.yml b/data/registry/collector-extension-bearertokenauth.yml index 32195789e667..7c8e4c4eb36d 100644 --- a/data/registry/collector-extension-bearertokenauth.yml +++ b/data/registry/collector-extension-bearertokenauth.yml @@ -18,4 +18,4 @@ createdAt: 2021-06-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/bearertokenauthextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-encoding.yml b/data/registry/collector-extension-encoding.yml index c2279d65b345..ec36ce419902 100644 --- a/data/registry/collector-extension-encoding.yml +++ b/data/registry/collector-extension-encoding.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/encoding - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-googleclientauth.yml b/data/registry/collector-extension-googleclientauth.yml new file mode 100644 index 000000000000..1d8ecd390d14 --- /dev/null +++ b/data/registry/collector-extension-googleclientauth.yml @@ -0,0 +1,21 @@ +# cSpell:ignore googleclientauthextension +title: Google Client Auth Extension +registryType: extension +language: collector +tags: + - google + - client + - auth + - extension + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/googleclientauthextension +license: Apache 2.0 +description: +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/googleclientauthextension + version: v0.100.0 diff --git a/data/registry/collector-extension-headerssetter.yml b/data/registry/collector-extension-headerssetter.yml index 54f8a2e300da..c333bb376cc6 100644 --- a/data/registry/collector-extension-headerssetter.yml +++ b/data/registry/collector-extension-headerssetter.yml @@ -20,4 +20,4 @@ createdAt: 2022-11-07 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/headerssetterextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-healthcheck.yml b/data/registry/collector-extension-healthcheck.yml index cac9279cf5cc..a3137fc16b91 100644 --- a/data/registry/collector-extension-healthcheck.yml +++ b/data/registry/collector-extension-healthcheck.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-http-forwarder.yml b/data/registry/collector-extension-http-forwarder.yml index 25e9b374492c..ed51bb65000d 100644 --- a/data/registry/collector-extension-http-forwarder.yml +++ b/data/registry/collector-extension-http-forwarder.yml @@ -1,4 +1,4 @@ -# cSpell:ignore httpforwarder +# cSpell:ignore httpforwarderextension title: HTTP Forwarder Collector Extension registryType: extension language: collector @@ -13,9 +13,9 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/httpforwarder + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/httpforwarderextension createdAt: 2021-02-24 package: registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarder - version: v0.95.0 + name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarderextension + version: v0.100.0 diff --git a/data/registry/collector-extension-jaegerremotesampling.yml b/data/registry/collector-extension-jaegerremotesampling.yml index e56053ffeb7c..79769fb14083 100644 --- a/data/registry/collector-extension-jaegerremotesampling.yml +++ b/data/registry/collector-extension-jaegerremotesampling.yml @@ -19,4 +19,4 @@ createdAt: 2022-11-07 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/jaegerremotesampling - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-memorylimiter.yml b/data/registry/collector-extension-memorylimiter.yml new file mode 100644 index 000000000000..4e79b11970ab --- /dev/null +++ b/data/registry/collector-extension-memorylimiter.yml @@ -0,0 +1,21 @@ +# cSpell:ignore memorylimiterextension +title: Memory Limiter Extension +registryType: extension +language: collector +tags: + - memory + - limiter + - extension + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector/tree/main/extension/memorylimiterextension +license: Apache 2.0 +description: + The memory limiter extension is used to prevent out of memory situations on +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: go.opentelemetry.io/collector/extension/memorylimiterextension + version: v0.100.0 diff --git a/data/registry/collector-extension-oauth2clientauth.yml b/data/registry/collector-extension-oauth2clientauth.yml index 2ef7865de41e..8cc79295821d 100644 --- a/data/registry/collector-extension-oauth2clientauth.yml +++ b/data/registry/collector-extension-oauth2clientauth.yml @@ -18,4 +18,4 @@ createdAt: 2021-06-22 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/oauth2clientauthextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-oidcauth.yml b/data/registry/collector-extension-oidcauth.yml index b7a48040a493..f631685b9d0f 100644 --- a/data/registry/collector-extension-oidcauth.yml +++ b/data/registry/collector-extension-oidcauth.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/oidcauthextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-opamp.yml b/data/registry/collector-extension-opamp.yml index e97262629ac2..78476ac12f4e 100644 --- a/data/registry/collector-extension-opamp.yml +++ b/data/registry/collector-extension-opamp.yml @@ -16,4 +16,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/opampextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-pprof.yml b/data/registry/collector-extension-pprof.yml index a9376ce7709f..ac1570ba6e4a 100644 --- a/data/registry/collector-extension-pprof.yml +++ b/data/registry/collector-extension-pprof.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/pprofextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-remotetap.yml b/data/registry/collector-extension-remotetap.yml index 628b91360421..d2220366b7cb 100644 --- a/data/registry/collector-extension-remotetap.yml +++ b/data/registry/collector-extension-remotetap.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/remotetapextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-sigv4auth.yml b/data/registry/collector-extension-sigv4auth.yml index 2e589fe4669b..737617db383e 100644 --- a/data/registry/collector-extension-sigv4auth.yml +++ b/data/registry/collector-extension-sigv4auth.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/sigv4authextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-solarwindsapmsettings.yml b/data/registry/collector-extension-solarwindsapmsettings.yml index fd1252c24630..ac93abc57eca 100644 --- a/data/registry/collector-extension-solarwindsapmsettings.yml +++ b/data/registry/collector-extension-solarwindsapmsettings.yml @@ -21,4 +21,4 @@ createdAt: 2024-02-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/solarwindsapmsettingsextension - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-extension-sumologic.yml b/data/registry/collector-extension-sumologic.yml new file mode 100644 index 000000000000..b9d2b93a5e27 --- /dev/null +++ b/data/registry/collector-extension-sumologic.yml @@ -0,0 +1,21 @@ +# cSpell:ignore sumologic sumologicextension +title: Sumo Logic Extension +registryType: extension +language: collector +tags: + - sumologic + - extension + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/extension/sumologicextension +license: Apache 2.0 +description: + This extension is to be used in conjunction with the Sumo Logic Exporter in + order to export telemetry data to Sumo Logic. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/sumologicextension + version: v0.100.0 diff --git a/data/registry/collector-processor-attributes.yml b/data/registry/collector-processor-attributes.yml index 801ac8f30aa4..1f740e38d5de 100644 --- a/data/registry/collector-processor-attributes.yml +++ b/data/registry/collector-processor-attributes.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/attributesprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-batch.yml b/data/registry/collector-processor-batch.yml index f15dbf14057d..56639f1ae626 100644 --- a/data/registry/collector-processor-batch.yml +++ b/data/registry/collector-processor-batch.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: go.opentelemetry.io/collector/processor/batchprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-cumulativetodelta.yml b/data/registry/collector-processor-cumulativetodelta.yml index c83e527c003a..6cde028339a1 100644 --- a/data/registry/collector-processor-cumulativetodelta.yml +++ b/data/registry/collector-processor-cumulativetodelta.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/cumulativetodeltaprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-datadog.yml b/data/registry/collector-processor-datadog.yml deleted file mode 100644 index 1c1231cfda80..000000000000 --- a/data/registry/collector-processor-datadog.yml +++ /dev/null @@ -1,20 +0,0 @@ -# cSpell:ignore datadogprocessor -title: Datadog Processor -registryType: processor -language: collector -tags: - - datadog - - processor - - collector -license: Apache 2.0 -description: - The Datadog Processor can be used to compute Datadog APM Stats pre-sampling. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/datadogprocessor -createdAt: 2020-11-05 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/datadogprocessor - version: v0.93.0 diff --git a/data/registry/collector-processor-deltatocumulative.yml b/data/registry/collector-processor-deltatocumulative.yml index bf6c8a16626f..9a367d50e633 100644 --- a/data/registry/collector-processor-deltatocumulative.yml +++ b/data/registry/collector-processor-deltatocumulative.yml @@ -19,4 +19,4 @@ createdAt: 2024-02-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-deltatorate.yml b/data/registry/collector-processor-deltatorate.yml index 2fefd10ccf9a..0b0651839e33 100644 --- a/data/registry/collector-processor-deltatorate.yml +++ b/data/registry/collector-processor-deltatorate.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatorateprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-filter.yml b/data/registry/collector-processor-filter.yml index 6adc401894d5..8997aea5df7b 100644 --- a/data/registry/collector-processor-filter.yml +++ b/data/registry/collector-processor-filter.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/filterprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-group-by-trace.yml b/data/registry/collector-processor-group-by-trace.yml index 5febbe9311b7..341581c744c0 100644 --- a/data/registry/collector-processor-group-by-trace.yml +++ b/data/registry/collector-processor-group-by-trace.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbytraceprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-groupbyattrs.yml b/data/registry/collector-processor-groupbyattrs.yml index 0ad8365d6c20..be7f23a4e462 100644 --- a/data/registry/collector-processor-groupbyattrs.yml +++ b/data/registry/collector-processor-groupbyattrs.yml @@ -20,4 +20,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/groupbyattrsprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-interval.yml b/data/registry/collector-processor-interval.yml index bcad3365b916..8448dc3f0a2d 100644 --- a/data/registry/collector-processor-interval.yml +++ b/data/registry/collector-processor-interval.yml @@ -18,4 +18,4 @@ createdAt: 2024-02-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/intervalprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-k8sattributes.yml b/data/registry/collector-processor-k8sattributes.yml index acf661d75800..c16b06938b06 100644 --- a/data/registry/collector-processor-k8sattributes.yml +++ b/data/registry/collector-processor-k8sattributes.yml @@ -19,4 +19,4 @@ createdAt: 2022-03-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/k8sattributesprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-logstransform.yml b/data/registry/collector-processor-logstransform.yml index dc2a8c57dc0a..35022b86d542 100644 --- a/data/registry/collector-processor-logstransform.yml +++ b/data/registry/collector-processor-logstransform.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/logstransformprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-metrics-transform.yml b/data/registry/collector-processor-metrics-transform.yml index fd42a61e5d17..7e68606a4208 100644 --- a/data/registry/collector-processor-metrics-transform.yml +++ b/data/registry/collector-processor-metrics-transform.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/metricstransformprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-metricsgeneration.yml b/data/registry/collector-processor-metricsgeneration.yml index ff1820fe00f2..3f4a42f073a3 100644 --- a/data/registry/collector-processor-metricsgeneration.yml +++ b/data/registry/collector-processor-metricsgeneration.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/metricsgenerationprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-probabilisticsampler.yml b/data/registry/collector-processor-probabilisticsampler.yml index 0262ea7ff5c6..6f7fdae8950b 100644 --- a/data/registry/collector-processor-probabilisticsampler.yml +++ b/data/registry/collector-processor-probabilisticsampler.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/probabilisticsamplerprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-redaction.yml b/data/registry/collector-processor-redaction.yml index 53e5dc46a4b7..30b9cbdf69c4 100644 --- a/data/registry/collector-processor-redaction.yml +++ b/data/registry/collector-processor-redaction.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/redactionprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-remotetap.yml b/data/registry/collector-processor-remotetap.yml index 8479d854a92b..5f90cd58b5dc 100644 --- a/data/registry/collector-processor-remotetap.yml +++ b/data/registry/collector-processor-remotetap.yml @@ -20,4 +20,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/remotetapprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-resource-detection.yml b/data/registry/collector-processor-resource-detection.yml index 999b164cdc42..561b848af320 100644 --- a/data/registry/collector-processor-resource-detection.yml +++ b/data/registry/collector-processor-resource-detection.yml @@ -20,4 +20,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-resource.yml b/data/registry/collector-processor-resource.yml index 787125b42ad6..22399ef5951a 100644 --- a/data/registry/collector-processor-resource.yml +++ b/data/registry/collector-processor-resource.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourceprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-routing.yml b/data/registry/collector-processor-routing.yml index d2b7e35a5581..413eb997415c 100644 --- a/data/registry/collector-processor-routing.yml +++ b/data/registry/collector-processor-routing.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/routingprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-schema.yml b/data/registry/collector-processor-schema.yml index 4e0f8ac1e801..d04b6b5c8309 100644 --- a/data/registry/collector-processor-schema.yml +++ b/data/registry/collector-processor-schema.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/schemaprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-servicegraph.yml b/data/registry/collector-processor-servicegraph.yml deleted file mode 100644 index 9425d512d4da..000000000000 --- a/data/registry/collector-processor-servicegraph.yml +++ /dev/null @@ -1,21 +0,0 @@ -# cSpell:ignore servicegraphprocessor -title: Service graph processor -registryType: processor -language: collector -tags: - - go - - processor - - collector -license: Apache 2.0 -description: - The service graphs processor is a traces processor that builds a map - representing the interrelationships between various services in a system. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/servicegraphprocessor -createdAt: 2022-10-26 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/servicegraphprocessor - version: v0.93.0 diff --git a/data/registry/collector-processor-span-metrics.yml b/data/registry/collector-processor-span-metrics.yml deleted file mode 100644 index 1ba7bc9844e4..000000000000 --- a/data/registry/collector-processor-span-metrics.yml +++ /dev/null @@ -1,21 +0,0 @@ -# cSpell:ignore spanmetricsprocessor -title: Span Metrics Processor -registryType: processor -language: collector -tags: - - go - - processor - - collector -license: Apache 2.0 -description: - The Span Metrics Processor for the OpenTelemetry Collector aggregates Request, - Error and Duration (R.E.D) metrics from span data. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/spanmetricsprocessor -createdAt: 2021-02-24 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/spanmetricsprocessor - version: v0.95.0 diff --git a/data/registry/collector-processor-span.yml b/data/registry/collector-processor-span.yml index 20d86351bd73..a1c6e4ad0206 100644 --- a/data/registry/collector-processor-span.yml +++ b/data/registry/collector-processor-span.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/spanprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-sumologic.yml b/data/registry/collector-processor-sumologic.yml index 72da9a25e0a1..1060f11b7062 100644 --- a/data/registry/collector-processor-sumologic.yml +++ b/data/registry/collector-processor-sumologic.yml @@ -20,4 +20,4 @@ createdAt: 2023-12-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/sumologicprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-tail-sampling.yml b/data/registry/collector-processor-tail-sampling.yml index e4f50682b1cd..e2b858951aab 100644 --- a/data/registry/collector-processor-tail-sampling.yml +++ b/data/registry/collector-processor-tail-sampling.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/tailsamplingprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-processor-transform.yml b/data/registry/collector-processor-transform.yml index 0906c3378837..f4db5284ac8f 100644 --- a/data/registry/collector-processor-transform.yml +++ b/data/registry/collector-processor-transform.yml @@ -20,4 +20,4 @@ createdAt: 2022-10-11 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-activedirectoryds.yml b/data/registry/collector-receiver-activedirectoryds.yml index 1dc982e18e61..213c2df284b3 100644 --- a/data/registry/collector-receiver-activedirectoryds.yml +++ b/data/registry/collector-receiver-activedirectoryds.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/activedirectorydsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-aerospike.yml b/data/registry/collector-receiver-aerospike.yml index 4ce2544fe42d..d376249e11f0 100644 --- a/data/registry/collector-receiver-aerospike.yml +++ b/data/registry/collector-receiver-aerospike.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/aerospikereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-apache.yml b/data/registry/collector-receiver-apache.yml index 6121d0655d7f..9ab4acc5d5fa 100644 --- a/data/registry/collector-receiver-apache.yml +++ b/data/registry/collector-receiver-apache.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/apachereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-apachespark.yml b/data/registry/collector-receiver-apachespark.yml index 69237f2b2278..9105c97878a8 100644 --- a/data/registry/collector-receiver-apachespark.yml +++ b/data/registry/collector-receiver-apachespark.yml @@ -19,4 +19,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/apachesparkreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-aws-ecs-container-metrics.yml b/data/registry/collector-receiver-aws-ecs-container-metrics.yml index ff45786989e3..64fed5e59694 100644 --- a/data/registry/collector-receiver-aws-ecs-container-metrics.yml +++ b/data/registry/collector-receiver-aws-ecs-container-metrics.yml @@ -20,4 +20,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsecscontainermetricsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-aws-xray.yml b/data/registry/collector-receiver-aws-xray.yml index cf1378baa231..8cd37f875d3a 100644 --- a/data/registry/collector-receiver-aws-xray.yml +++ b/data/registry/collector-receiver-aws-xray.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsxrayreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-awscloudwatch.yml b/data/registry/collector-receiver-awscloudwatch.yml index 40273bf06785..ca0ec367e1f2 100644 --- a/data/registry/collector-receiver-awscloudwatch.yml +++ b/data/registry/collector-receiver-awscloudwatch.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscloudwatchreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-awscloudwatchmetrics.yml b/data/registry/collector-receiver-awscloudwatchmetrics.yml index 8781e3e0a149..b06866a02ef7 100644 --- a/data/registry/collector-receiver-awscloudwatchmetrics.yml +++ b/data/registry/collector-receiver-awscloudwatchmetrics.yml @@ -20,4 +20,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscloudwatchmetricsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-awscontainerinsight.yml b/data/registry/collector-receiver-awscontainerinsight.yml index e73d81424230..7ec83ca2a8dc 100644 --- a/data/registry/collector-receiver-awscontainerinsight.yml +++ b/data/registry/collector-receiver-awscontainerinsight.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-awsfirehose.yml b/data/registry/collector-receiver-awsfirehose.yml index 78075167197e..778a8d4f01f3 100644 --- a/data/registry/collector-receiver-awsfirehose.yml +++ b/data/registry/collector-receiver-awsfirehose.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsfirehosereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-awss3.yml b/data/registry/collector-receiver-awss3.yml new file mode 100644 index 000000000000..b7a63f21bc32 --- /dev/null +++ b/data/registry/collector-receiver-awss3.yml @@ -0,0 +1,21 @@ +# cSpell:ignore awss3receiver +title: AWS S3 Receiver +registryType: receiver +language: collector +tags: + - aws + - s3 + - receiver + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awss3receiver +license: Apache 2.0 +description: + Receiver for retrieving trace previously stored in S3 by the AWS S3 Exporter. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awss3receiver + version: v0.100.0 diff --git a/data/registry/collector-receiver-azureblob.yml b/data/registry/collector-receiver-azureblob.yml index 3027aaf69624..9354d4bd0369 100644 --- a/data/registry/collector-receiver-azureblob.yml +++ b/data/registry/collector-receiver-azureblob.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azureblobreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-azureeventhub.yml b/data/registry/collector-receiver-azureeventhub.yml index 293fc3dd5edc..2201f72b4ce9 100644 --- a/data/registry/collector-receiver-azureeventhub.yml +++ b/data/registry/collector-receiver-azureeventhub.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azureeventhubreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-azuremonitor.yml b/data/registry/collector-receiver-azuremonitor.yml index e5b27e51f91b..253d71caec80 100644 --- a/data/registry/collector-receiver-azuremonitor.yml +++ b/data/registry/collector-receiver-azuremonitor.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/azuremonitorreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-bigip.yml b/data/registry/collector-receiver-bigip.yml index 85f0b73e97f1..8b2c4a74e1b3 100644 --- a/data/registry/collector-receiver-bigip.yml +++ b/data/registry/collector-receiver-bigip.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/bigipreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-carbon.yml b/data/registry/collector-receiver-carbon.yml index a07896dae6c8..fa28872c7415 100644 --- a/data/registry/collector-receiver-carbon.yml +++ b/data/registry/collector-receiver-carbon.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/carbonreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-chrony.yml b/data/registry/collector-receiver-chrony.yml index fb57964aede9..af769b841180 100644 --- a/data/registry/collector-receiver-chrony.yml +++ b/data/registry/collector-receiver-chrony.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/chronyreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-cloudflare.yml b/data/registry/collector-receiver-cloudflare.yml index 354169e7823b..36df2436d77b 100644 --- a/data/registry/collector-receiver-cloudflare.yml +++ b/data/registry/collector-receiver-cloudflare.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/cloudflarereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-cloudfoundry.yml b/data/registry/collector-receiver-cloudfoundry.yml index a201a4799aea..5841b76e5056 100644 --- a/data/registry/collector-receiver-cloudfoundry.yml +++ b/data/registry/collector-receiver-cloudfoundry.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/cloudfoundryreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-collectd.yml b/data/registry/collector-receiver-collectd.yml index 6405e75074db..f86aa49fbf45 100644 --- a/data/registry/collector-receiver-collectd.yml +++ b/data/registry/collector-receiver-collectd.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/collectdreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-couchdb.yml b/data/registry/collector-receiver-couchdb.yml index bb610242abc3..d1a51c761667 100644 --- a/data/registry/collector-receiver-couchdb.yml +++ b/data/registry/collector-receiver-couchdb.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/couchdbreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-database.yml b/data/registry/collector-receiver-database.yml deleted file mode 100644 index aa8723450d99..000000000000 --- a/data/registry/collector-receiver-database.yml +++ /dev/null @@ -1,17 +0,0 @@ -# cSpell:ignore ODCD -title: OTel based Data Collector for Databases (ODCD) -registryType: utilities -language: java -tags: - - receiver - - database - - instana -license: MIT -description: - A tool or template to generate OpenTelemetry metrics for various databases. -authors: - - name: Rui Liu - url: https://github.com/liurui-1 -urls: - repo: https://github.com/instana/otel-database-dc -createdAt: 2023-11-13 diff --git a/data/registry/collector-receiver-datadog.yml b/data/registry/collector-receiver-datadog.yml index 92bc994dc70c..848bb55438ae 100644 --- a/data/registry/collector-receiver-datadog.yml +++ b/data/registry/collector-receiver-datadog.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/datadogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-docker-stats.yml b/data/registry/collector-receiver-docker-stats.yml index ebc9f31ada5b..30c7144fe273 100644 --- a/data/registry/collector-receiver-docker-stats.yml +++ b/data/registry/collector-receiver-docker-stats.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/dockerstatsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-elasticsearch.yml b/data/registry/collector-receiver-elasticsearch.yml index e0134bd2f5a0..1b28edfe9d4b 100644 --- a/data/registry/collector-receiver-elasticsearch.yml +++ b/data/registry/collector-receiver-elasticsearch.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/elasticsearchreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-expvar.yml b/data/registry/collector-receiver-expvar.yml index fd7a772acb1d..29927d3a2679 100644 --- a/data/registry/collector-receiver-expvar.yml +++ b/data/registry/collector-receiver-expvar.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/expvarreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-filelog.yml b/data/registry/collector-receiver-filelog.yml index 14e1422fb074..2c567e0c3e9e 100644 --- a/data/registry/collector-receiver-filelog.yml +++ b/data/registry/collector-receiver-filelog.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filelogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-filestats.yml b/data/registry/collector-receiver-filestats.yml index 0e7cc31912bd..1ef39729cefe 100644 --- a/data/registry/collector-receiver-filestats.yml +++ b/data/registry/collector-receiver-filestats.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filestatsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-flinkmetrics.yml b/data/registry/collector-receiver-flinkmetrics.yml index 48ec052ff9f8..8dabad0346df 100644 --- a/data/registry/collector-receiver-flinkmetrics.yml +++ b/data/registry/collector-receiver-flinkmetrics.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/flinkmetricsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-fluent-forward.yml b/data/registry/collector-receiver-fluent-forward.yml index 6ef1bd772ba8..35963f5a3c9d 100644 --- a/data/registry/collector-receiver-fluent-forward.yml +++ b/data/registry/collector-receiver-fluent-forward.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/fluentforwardreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-gitprovider.yml b/data/registry/collector-receiver-gitprovider.yml index 9a7f8fae1b58..e294581e8f26 100644 --- a/data/registry/collector-receiver-gitprovider.yml +++ b/data/registry/collector-receiver-gitprovider.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/gitproviderreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-googlecloudpubsub.yml b/data/registry/collector-receiver-googlecloudpubsub.yml index 92ee56acd59b..114d11239c2d 100644 --- a/data/registry/collector-receiver-googlecloudpubsub.yml +++ b/data/registry/collector-receiver-googlecloudpubsub.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudpubsubreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-googlecloudspanner.yml b/data/registry/collector-receiver-googlecloudspanner.yml index ed164c75d335..9407360f7b8e 100644 --- a/data/registry/collector-receiver-googlecloudspanner.yml +++ b/data/registry/collector-receiver-googlecloudspanner.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/googlecloudspannerreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-haproxy.yml b/data/registry/collector-receiver-haproxy.yml index 5c6701ea2cf7..e349c6f2afed 100644 --- a/data/registry/collector-receiver-haproxy.yml +++ b/data/registry/collector-receiver-haproxy.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/haproxyreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-host-metrics.yml b/data/registry/collector-receiver-host-metrics.yml index 791a22f70790..d0526edfcbd0 100644 --- a/data/registry/collector-receiver-host-metrics.yml +++ b/data/registry/collector-receiver-host-metrics.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-httpcheck.yml b/data/registry/collector-receiver-httpcheck.yml index 0bddd979331d..5f65c92d3a30 100644 --- a/data/registry/collector-receiver-httpcheck.yml +++ b/data/registry/collector-receiver-httpcheck.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/httpcheckreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-iis.yml b/data/registry/collector-receiver-iis.yml index 197adaabe72c..39b6262070da 100644 --- a/data/registry/collector-receiver-iis.yml +++ b/data/registry/collector-receiver-iis.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/iisreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-influxdb.yml b/data/registry/collector-receiver-influxdb.yml index 1c62188d19a6..0a018a08a8cb 100644 --- a/data/registry/collector-receiver-influxdb.yml +++ b/data/registry/collector-receiver-influxdb.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/influxdbreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-jaeger.yml b/data/registry/collector-receiver-jaeger.yml index c52a26d7e5a0..d6ca3ae02214 100644 --- a/data/registry/collector-receiver-jaeger.yml +++ b/data/registry/collector-receiver-jaeger.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-jmx.yml b/data/registry/collector-receiver-jmx.yml index 7afaee87f578..676dfa8ab831 100644 --- a/data/registry/collector-receiver-jmx.yml +++ b/data/registry/collector-receiver-jmx.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jmxreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-journald.yml b/data/registry/collector-receiver-journald.yml index 354bab4db1d1..bb81ce0620fc 100644 --- a/data/registry/collector-receiver-journald.yml +++ b/data/registry/collector-receiver-journald.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/journaldreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-k8s-cluster.yml b/data/registry/collector-receiver-k8s-cluster.yml index 482c24a2d83e..9d2bed5d69e7 100644 --- a/data/registry/collector-receiver-k8s-cluster.yml +++ b/data/registry/collector-receiver-k8s-cluster.yml @@ -20,4 +20,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sclusterreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-k8sevents.yml b/data/registry/collector-receiver-k8sevents.yml index d7f0c1dba5d3..06748c56b604 100644 --- a/data/registry/collector-receiver-k8sevents.yml +++ b/data/registry/collector-receiver-k8sevents.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8seventsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-k8sobjects.yml b/data/registry/collector-receiver-k8sobjects.yml index 491b4ee810cf..d7d63d7fbba0 100644 --- a/data/registry/collector-receiver-k8sobjects.yml +++ b/data/registry/collector-receiver-k8sobjects.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/k8sobjectsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-kafka.yml b/data/registry/collector-receiver-kafka.yml index 68f702720d81..e30077b75ca1 100644 --- a/data/registry/collector-receiver-kafka.yml +++ b/data/registry/collector-receiver-kafka.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkareceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-kafkametrics.yml b/data/registry/collector-receiver-kafkametrics.yml index 65a59c23f7e1..e9276439a7cf 100644 --- a/data/registry/collector-receiver-kafkametrics.yml +++ b/data/registry/collector-receiver-kafkametrics.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kafkametricsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-kubelet-stats.yml b/data/registry/collector-receiver-kubelet-stats.yml index 05ce454bbc35..61d15ed958d8 100644 --- a/data/registry/collector-receiver-kubelet-stats.yml +++ b/data/registry/collector-receiver-kubelet-stats.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/kubeletstatsreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-loki.yml b/data/registry/collector-receiver-loki.yml index 0dd67d70b72f..5197182ff672 100644 --- a/data/registry/collector-receiver-loki.yml +++ b/data/registry/collector-receiver-loki.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/lokireceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-memcached.yml b/data/registry/collector-receiver-memcached.yml index 949a8f83bcbe..79e5cf88a27a 100644 --- a/data/registry/collector-receiver-memcached.yml +++ b/data/registry/collector-receiver-memcached.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/memcachedreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-mongodb.yml b/data/registry/collector-receiver-mongodb.yml index 93cdabadbbf7..677394337964 100644 --- a/data/registry/collector-receiver-mongodb.yml +++ b/data/registry/collector-receiver-mongodb.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mongodbreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-mongodbatlas.yml b/data/registry/collector-receiver-mongodbatlas.yml index 79fa0601724c..af8a30ed3926 100644 --- a/data/registry/collector-receiver-mongodbatlas.yml +++ b/data/registry/collector-receiver-mongodbatlas.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mongodbatlasreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-mysql.yml b/data/registry/collector-receiver-mysql.yml index 71b571c83047..15d507113d8b 100644 --- a/data/registry/collector-receiver-mysql.yml +++ b/data/registry/collector-receiver-mysql.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/mysqlreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-namedpipe.yml b/data/registry/collector-receiver-namedpipe.yml index 7343f1b10f43..5f29b8b048ff 100644 --- a/data/registry/collector-receiver-namedpipe.yml +++ b/data/registry/collector-receiver-namedpipe.yml @@ -18,4 +18,4 @@ createdAt: 2024-01-19 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/namedpipereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-nginx.yml b/data/registry/collector-receiver-nginx.yml index 46ed2180a2de..7e3057d1f858 100644 --- a/data/registry/collector-receiver-nginx.yml +++ b/data/registry/collector-receiver-nginx.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/nginxreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-nop.yml b/data/registry/collector-receiver-nop.yml new file mode 100644 index 000000000000..b578ff2e5330 --- /dev/null +++ b/data/registry/collector-receiver-nop.yml @@ -0,0 +1,21 @@ +# cSpell:ignore nopreceiver +title: No-op Receiver +registryType: receiver +language: collector +tags: + - nop + - receiver + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector/tree/main/receiver/nopreceiver +license: Apache 2.0 +description: + Serves as a placeholder receiver in a pipeline. This can be useful if you want + to e.g. start a Collector with only extensions enabled. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: go.opentelemetry.io/collector/receiver/nopreceiver + version: v0.100.0 diff --git a/data/registry/collector-receiver-nsxt.yml b/data/registry/collector-receiver-nsxt.yml index c148480625b9..814f83a2900b 100644 --- a/data/registry/collector-receiver-nsxt.yml +++ b/data/registry/collector-receiver-nsxt.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/nsxtreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-opencensus.yml b/data/registry/collector-receiver-opencensus.yml index c7a2ca2bae21..34eba650cfb6 100644 --- a/data/registry/collector-receiver-opencensus.yml +++ b/data/registry/collector-receiver-opencensus.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/opencensusreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-openllmetry.yml b/data/registry/collector-receiver-openllmetry.yml new file mode 100644 index 000000000000..3dcacf135811 --- /dev/null +++ b/data/registry/collector-receiver-openllmetry.yml @@ -0,0 +1,18 @@ +# cSpell:ignore openllmetry Instana +title: OTel based Data Collector for LLM +registryType: receiver +language: java +tags: + - java + - receiver + - collector +license: MIT +description: + OTel based Data Collector for LLM is the tool or template to generate + OpenTelemetry metrics for various LLM and LLM Applications. All implementation + are based on predefined OpenTelemetry Semantic Conventions. +authors: + - name: IBM Instana +urls: + repo: https://github.com/instana/otel-dc/tree/main/llm +createdAt: 2024-05-07 diff --git a/data/registry/collector-receiver-oracledb.yml b/data/registry/collector-receiver-oracledb.yml index 07767838b936..9c6ce5f8e27e 100644 --- a/data/registry/collector-receiver-oracledb.yml +++ b/data/registry/collector-receiver-oracledb.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/oracledbreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-osquery.yml b/data/registry/collector-receiver-osquery.yml index 3299d1151aae..135ba7359854 100644 --- a/data/registry/collector-receiver-osquery.yml +++ b/data/registry/collector-receiver-osquery.yml @@ -18,4 +18,4 @@ createdAt: 2024-01-19 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/osqueryreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-otelarrow.yml b/data/registry/collector-receiver-otelarrow.yml new file mode 100644 index 000000000000..35cdd9ae1a13 --- /dev/null +++ b/data/registry/collector-receiver-otelarrow.yml @@ -0,0 +1,21 @@ +# cSpell:ignore otelarrowreceiver +title: OpenTelemetry Protocol with Apache Arrow Receiver +registryType: receiver +language: collector +tags: + - arrow + - receiver + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/otelarrowreceiver +license: Apache 2.0 +description: + Receives telemetry data using OpenTelemetry Protocol with Apache Arrow and + standard OTLP protocol via gRPC. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: go-collector + name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otelarrowreceiver + version: v0.100.0 diff --git a/data/registry/collector-receiver-otlp.yml b/data/registry/collector-receiver-otlp.yml index 1b4377f62e2d..e7ac8f7d870b 100644 --- a/data/registry/collector-receiver-otlp.yml +++ b/data/registry/collector-receiver-otlp.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: go.opentelemetry.io/collector/receiver/otlpreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-otlpjsonfile.yml b/data/registry/collector-receiver-otlpjsonfile.yml index 6ab0d4853902..a576a003bdbc 100644 --- a/data/registry/collector-receiver-otlpjsonfile.yml +++ b/data/registry/collector-receiver-otlpjsonfile.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otlpjsonfilereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-podman.yml b/data/registry/collector-receiver-podman.yml index 30d021459d1f..d03cd4f1c84f 100644 --- a/data/registry/collector-receiver-podman.yml +++ b/data/registry/collector-receiver-podman.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/podmanreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-postgresql.yml b/data/registry/collector-receiver-postgresql.yml index 38f52f027979..40116834a8ab 100644 --- a/data/registry/collector-receiver-postgresql.yml +++ b/data/registry/collector-receiver-postgresql.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/postgresqlreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-prometheus.yml b/data/registry/collector-receiver-prometheus.yml index 86097efdabf5..6a81eeff1e03 100644 --- a/data/registry/collector-receiver-prometheus.yml +++ b/data/registry/collector-receiver-prometheus.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-pulsar.yml b/data/registry/collector-receiver-pulsar.yml index 1c07f8def1fe..fc096cf5074a 100644 --- a/data/registry/collector-receiver-pulsar.yml +++ b/data/registry/collector-receiver-pulsar.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/pulsarreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-purefa.yml b/data/registry/collector-receiver-purefa.yml index e16f0dcf429b..42e8595d14a1 100644 --- a/data/registry/collector-receiver-purefa.yml +++ b/data/registry/collector-receiver-purefa.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/purefareceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-purefb.yml b/data/registry/collector-receiver-purefb.yml index d494e6b85162..d4f7c687a4f1 100644 --- a/data/registry/collector-receiver-purefb.yml +++ b/data/registry/collector-receiver-purefb.yml @@ -19,4 +19,4 @@ createdAt: 2023-02-01 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/purefbreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-rabbitmq.yml b/data/registry/collector-receiver-rabbitmq.yml index 8bebc1223426..040786bc7993 100644 --- a/data/registry/collector-receiver-rabbitmq.yml +++ b/data/registry/collector-receiver-rabbitmq.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/rabbitmqreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-receiver-creator.yml b/data/registry/collector-receiver-receiver-creator.yml index ac0857ff2be3..4fdcc3b82fc6 100644 --- a/data/registry/collector-receiver-receiver-creator.yml +++ b/data/registry/collector-receiver-receiver-creator.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/receivercreator - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-redis.yml b/data/registry/collector-receiver-redis.yml index a54513b3ce66..a5f782c0fe0f 100644 --- a/data/registry/collector-receiver-redis.yml +++ b/data/registry/collector-receiver-redis.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/redisreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-riak.yml b/data/registry/collector-receiver-riak.yml index 78c4ad205870..40eeacd44755 100644 --- a/data/registry/collector-receiver-riak.yml +++ b/data/registry/collector-receiver-riak.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/riakreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-saphana.yml b/data/registry/collector-receiver-saphana.yml index 4027125de490..66c017b53c01 100644 --- a/data/registry/collector-receiver-saphana.yml +++ b/data/registry/collector-receiver-saphana.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/saphanareceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-sapm.yml b/data/registry/collector-receiver-sapm.yml index a8372d9d393c..d86f086a87f5 100644 --- a/data/registry/collector-receiver-sapm.yml +++ b/data/registry/collector-receiver-sapm.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sapmreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-signalfx.yml b/data/registry/collector-receiver-signalfx.yml index f8c0c7105c29..da53a9f13823 100644 --- a/data/registry/collector-receiver-signalfx.yml +++ b/data/registry/collector-receiver-signalfx.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/signalfxreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-simple-prometheus.yml b/data/registry/collector-receiver-simple-prometheus.yml index d464505b6ac6..397f67f14bde 100644 --- a/data/registry/collector-receiver-simple-prometheus.yml +++ b/data/registry/collector-receiver-simple-prometheus.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/simpleprometheusreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-skywalking.yml b/data/registry/collector-receiver-skywalking.yml index 817a035ce208..9e86ef16b1ac 100644 --- a/data/registry/collector-receiver-skywalking.yml +++ b/data/registry/collector-receiver-skywalking.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/skywalkingreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-snmp.yml b/data/registry/collector-receiver-snmp.yml index d2c54b6cc2f9..cc2cf46eda01 100644 --- a/data/registry/collector-receiver-snmp.yml +++ b/data/registry/collector-receiver-snmp.yml @@ -19,4 +19,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/snmpreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-snowflake.yml b/data/registry/collector-receiver-snowflake.yml index 399ecfe44aef..89ebe5b89219 100644 --- a/data/registry/collector-receiver-snowflake.yml +++ b/data/registry/collector-receiver-snowflake.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/snowflakereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-solace.yml b/data/registry/collector-receiver-solace.yml index b1b32ceb50e7..c74d20f410b1 100644 --- a/data/registry/collector-receiver-solace.yml +++ b/data/registry/collector-receiver-solace.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/solacereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-splunk-hec.yml b/data/registry/collector-receiver-splunk-hec.yml index 4ba95cfae5cc..e85d916d56e2 100644 --- a/data/registry/collector-receiver-splunk-hec.yml +++ b/data/registry/collector-receiver-splunk-hec.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkhecreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-splunkenterprise.yml b/data/registry/collector-receiver-splunkenterprise.yml index 3694e3657a0c..17b0e12b8a12 100644 --- a/data/registry/collector-receiver-splunkenterprise.yml +++ b/data/registry/collector-receiver-splunkenterprise.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/splunkenterprisereceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-sqlquery.yml b/data/registry/collector-receiver-sqlquery.yml index 64d4544cc9ef..d093bdd555ec 100644 --- a/data/registry/collector-receiver-sqlquery.yml +++ b/data/registry/collector-receiver-sqlquery.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlqueryreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-sqlserver.yml b/data/registry/collector-receiver-sqlserver.yml index 4d57c91412ce..7c941f2a11e7 100644 --- a/data/registry/collector-receiver-sqlserver.yml +++ b/data/registry/collector-receiver-sqlserver.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sqlserverreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-sshcheck.yml b/data/registry/collector-receiver-sshcheck.yml index f0de445be6b5..3272688556e2 100644 --- a/data/registry/collector-receiver-sshcheck.yml +++ b/data/registry/collector-receiver-sshcheck.yml @@ -19,4 +19,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/sshcheckreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-statsd.yml b/data/registry/collector-receiver-statsd.yml index ed1d26ae57c5..5caeffd3ab74 100644 --- a/data/registry/collector-receiver-statsd.yml +++ b/data/registry/collector-receiver-statsd.yml @@ -17,4 +17,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/statsdreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-syslog.yml b/data/registry/collector-receiver-syslog.yml index 6aea577b66b4..f6ca8416d3e9 100644 --- a/data/registry/collector-receiver-syslog.yml +++ b/data/registry/collector-receiver-syslog.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/syslogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-tcplog.yml b/data/registry/collector-receiver-tcplog.yml index 8c1d37abe564..e74cb8d6df7a 100644 --- a/data/registry/collector-receiver-tcplog.yml +++ b/data/registry/collector-receiver-tcplog.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/tcplogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-udplog.yml b/data/registry/collector-receiver-udplog.yml index a1dbb2451fa9..093dfa272827 100644 --- a/data/registry/collector-receiver-udplog.yml +++ b/data/registry/collector-receiver-udplog.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/udplogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-vcenter.yml b/data/registry/collector-receiver-vcenter.yml index d297dcc0fb0c..bb5b7b6f11ab 100644 --- a/data/registry/collector-receiver-vcenter.yml +++ b/data/registry/collector-receiver-vcenter.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-05 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/vcenterreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-wavefront.yml b/data/registry/collector-receiver-wavefront.yml index e3ae269ab852..b0dc6971a04b 100644 --- a/data/registry/collector-receiver-wavefront.yml +++ b/data/registry/collector-receiver-wavefront.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/wavefrontreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-webhookevent.yml b/data/registry/collector-receiver-webhookevent.yml index 1c27daa14fec..35627b7882fe 100644 --- a/data/registry/collector-receiver-webhookevent.yml +++ b/data/registry/collector-receiver-webhookevent.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/webhookeventreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-windows-perf-counters.yml b/data/registry/collector-receiver-windows-perf-counters.yml index b91d877fae7e..a14f64527872 100644 --- a/data/registry/collector-receiver-windows-perf-counters.yml +++ b/data/registry/collector-receiver-windows-perf-counters.yml @@ -19,4 +19,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/windowsperfcountersreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-windowseventlog.yml b/data/registry/collector-receiver-windowseventlog.yml index aa3018d8cd66..710c2a00690f 100644 --- a/data/registry/collector-receiver-windowseventlog.yml +++ b/data/registry/collector-receiver-windowseventlog.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-25 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/windowseventlogreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/collector-receiver-zipkin.yml b/data/registry/collector-receiver-zipkin.yml index 7baf204a1e24..639e1e6aa190 100644 --- a/data/registry/collector-receiver-zipkin.yml +++ b/data/registry/collector-receiver-zipkin.yml @@ -13,7 +13,7 @@ authors: package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver - version: v0.98.0 + version: v0.100.0 urls: repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/zipkinreceiver createdAt: 2020-11-05 diff --git a/data/registry/collector-receiver-zookeeper.yml b/data/registry/collector-receiver-zookeeper.yml index 9568dec34a55..02fad2087f28 100644 --- a/data/registry/collector-receiver-zookeeper.yml +++ b/data/registry/collector-receiver-zookeeper.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-26 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zookeeperreceiver - version: v0.98.0 + version: v0.100.0 diff --git a/data/registry/exporter-dotnet-console.yml b/data/registry/exporter-dotnet-console.yml index 2303b503d037..fde7651fdbf0 100644 --- a/data/registry/exporter-dotnet-console.yml +++ b/data/registry/exporter-dotnet-console.yml @@ -15,4 +15,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Exporter.Console - version: 1.8.0 + version: 1.8.1 diff --git a/data/registry/exporter-dotnet-geneva.yml b/data/registry/exporter-dotnet-geneva.yml index 589284392128..abed352e2caf 100644 --- a/data/registry/exporter-dotnet-geneva.yml +++ b/data/registry/exporter-dotnet-geneva.yml @@ -17,4 +17,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Exporter.Geneva - version: 1.7.0 + version: 1.8.0-rc.1 diff --git a/data/registry/exporter-dotnet-inmemory.yml b/data/registry/exporter-dotnet-inmemory.yml index a9045b5f886b..59a318c1afb7 100644 --- a/data/registry/exporter-dotnet-inmemory.yml +++ b/data/registry/exporter-dotnet-inmemory.yml @@ -17,4 +17,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Exporter.InMemory - version: 1.8.0 + version: 1.8.1 diff --git a/data/registry/exporter-dotnet-onecollector.yml b/data/registry/exporter-dotnet-onecollector.yml index 1814270ac40e..47d56670b51e 100644 --- a/data/registry/exporter-dotnet-onecollector.yml +++ b/data/registry/exporter-dotnet-onecollector.yml @@ -18,4 +18,4 @@ createdAt: 2023-03-03 package: registry: nuget name: OpenTelemetry.Exporter.OneCollector - version: 1.6.0 + version: 1.8.0 diff --git a/data/registry/exporter-dotnet-opentelemetryprotocol.yml b/data/registry/exporter-dotnet-opentelemetryprotocol.yml index 0609b52837b6..7eb64a3beb5d 100644 --- a/data/registry/exporter-dotnet-opentelemetryprotocol.yml +++ b/data/registry/exporter-dotnet-opentelemetryprotocol.yml @@ -19,4 +19,4 @@ createdAt: 2020-02-05 package: registry: nuget name: OpenTelemetry.Exporter.OpenTelemetryProtocol - version: 1.8.0 + version: 1.8.1 diff --git a/data/registry/exporter-dotnet-stackdriver.yml b/data/registry/exporter-dotnet-stackdriver.yml index 27aca2940422..91154a84eaad 100644 --- a/data/registry/exporter-dotnet-stackdriver.yml +++ b/data/registry/exporter-dotnet-stackdriver.yml @@ -16,4 +16,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Exporter.Stackdriver - version: 1.0.0-beta.5 + version: 1.0.0-beta.6 diff --git a/data/registry/exporter-java-jaeger.yml b/data/registry/exporter-java-jaeger.yml deleted file mode 100644 index 254a69055f50..000000000000 --- a/data/registry/exporter-java-jaeger.yml +++ /dev/null @@ -1,13 +0,0 @@ -title: Jaeger Exporter -registryType: exporter -language: java -tags: - - java - - exporter -license: Apache 2.0 -description: This library allows to export data using the Jaeger gRPC Protocol. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-java/tree/main/exporters/jaeger -createdAt: 2020-11-05 diff --git a/data/registry/exporter-js-azure.yml b/data/registry/exporter-js-azure.yml index 9feb7d40b81f..6bdabcd5df58 100644 --- a/data/registry/exporter-js-azure.yml +++ b/data/registry/exporter-js-azure.yml @@ -13,7 +13,7 @@ authors: package: name: '@azure/monitor-opentelemetry-exporter' registry: npm - version: 1.0.0-beta.21 + version: 1.0.0-beta.23 urls: repo: https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/monitor/monitor-opentelemetry-exporter createdAt: 2021-11-01 diff --git a/data/registry/exporter-js-google-cloud-monitoring.yml b/data/registry/exporter-js-google-cloud-monitoring.yml index ebd6933898c0..197e1993d124 100644 --- a/data/registry/exporter-js-google-cloud-monitoring.yml +++ b/data/registry/exporter-js-google-cloud-monitoring.yml @@ -14,4 +14,4 @@ createdAt: 2020-04-01 package: registry: npm name: '@google-cloud/opentelemetry-cloud-monitoring-exporter' - version: 0.17.0 + version: 0.18.0 diff --git a/data/registry/exporter-js-google-cloud-trace.yml b/data/registry/exporter-js-google-cloud-trace.yml index 458842b45dd1..ca9ab7d6767e 100644 --- a/data/registry/exporter-js-google-cloud-trace.yml +++ b/data/registry/exporter-js-google-cloud-trace.yml @@ -14,4 +14,4 @@ createdAt: 2020-04-01 package: registry: npm name: '@google-cloud/opentelemetry-cloud-trace-exporter' - version: 2.1.0 + version: 2.2.0 diff --git a/data/registry/exporter-js-instana.yml b/data/registry/exporter-js-instana.yml index 017cebe3d43d..dc718218421f 100644 --- a/data/registry/exporter-js-instana.yml +++ b/data/registry/exporter-js-instana.yml @@ -15,4 +15,4 @@ createdAt: 2022-04-18 package: registry: npm name: '@instana/opentelemetry-exporter' - version: 3.3.0 + version: 3.8.0 diff --git a/data/registry/exporter-js-jaeger.yml b/data/registry/exporter-js-jaeger.yml index f585efbd76c4..8a8956199948 100644 --- a/data/registry/exporter-js-jaeger.yml +++ b/data/registry/exporter-js-jaeger.yml @@ -14,4 +14,4 @@ createdAt: 2020-02-06 package: registry: npm name: '@opentelemetry/exporter-jaeger' - version: 1.23.0 + version: 1.24.1 diff --git a/data/registry/exporter-js-prometheus.yml b/data/registry/exporter-js-prometheus.yml index 1b63b84f1de1..74d5413e4f03 100644 --- a/data/registry/exporter-js-prometheus.yml +++ b/data/registry/exporter-js-prometheus.yml @@ -14,4 +14,4 @@ createdAt: 2020-02-06 package: registry: npm name: '@opentelemetry/exporter-prometheus' - version: 0.50.0 + version: 0.51.1 diff --git a/data/registry/exporter-js-zipkin.yml b/data/registry/exporter-js-zipkin.yml index 21fc00f593b3..f39e4eddf94f 100644 --- a/data/registry/exporter-js-zipkin.yml +++ b/data/registry/exporter-js-zipkin.yml @@ -11,7 +11,7 @@ authors: package: name: '@opentelemetry/exporter-zipkin' registry: npm - version: 1.23.0 + version: 1.24.1 urls: repo: https://github.com/open-telemetry/opentelemetry-js/tree/main/packages/opentelemetry-exporter-zipkin docs: /docs/languages/js/exporters/#zipkin diff --git a/data/registry/exporter-ruby-otlpmetrics.yml b/data/registry/exporter-ruby-otlpmetrics.yml new file mode 100644 index 000000000000..dbc1ef51b0c4 --- /dev/null +++ b/data/registry/exporter-ruby-otlpmetrics.yml @@ -0,0 +1,17 @@ +title: OTLP metrics exporter for Ruby +registryType: exporter +language: ruby +tags: + - otlp + - metrics + - exporter + - ruby +urls: + repo: https://github.com/open-telemetry/opentelemetry-ruby/tree/main/exporter/otlp-metrics +license: Apache 2.0 +description: + The `opentelemetry-exporter-otlp-metrics` gem provides an OTLP metrics + exporter for OpenTelemetry for Ruby. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/exporter-rust-stdout.yml b/data/registry/exporter-rust-stdout.yml index 3fdeba8191aa..7474902f929f 100644 --- a/data/registry/exporter-rust-stdout.yml +++ b/data/registry/exporter-rust-stdout.yml @@ -16,4 +16,4 @@ createdAt: 2024-01-19 package: registry: crates name: opentelemetry-stdout - version: 0.2.0 + version: 0.3.0 diff --git a/data/registry/instrumentation-dotnet-aspnet-telemetryhttpmodule.yml b/data/registry/instrumentation-dotnet-aspnet-telemetryhttpmodule.yml index b56d291d429e..4088f6b679bf 100644 --- a/data/registry/instrumentation-dotnet-aspnet-telemetryhttpmodule.yml +++ b/data/registry/instrumentation-dotnet-aspnet-telemetryhttpmodule.yml @@ -20,4 +20,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Instrumentation.AspNet.TelemetryHttpModule - version: 1.8.0-beta.1 + version: 1.8.0-beta.2 diff --git a/data/registry/instrumentation-dotnet-aspnet.yml b/data/registry/instrumentation-dotnet-aspnet.yml index 568c524d7a1c..8c00c6a91e64 100644 --- a/data/registry/instrumentation-dotnet-aspnet.yml +++ b/data/registry/instrumentation-dotnet-aspnet.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-28 package: registry: nuget name: OpenTelemetry.Instrumentation.AspNet - version: 1.8.0-beta.1 + version: 1.8.0-beta.2 diff --git a/data/registry/instrumentation-dotnet-aspnetcore.yml b/data/registry/instrumentation-dotnet-aspnetcore.yml index 265bd3793433..85d401f367bb 100644 --- a/data/registry/instrumentation-dotnet-aspnetcore.yml +++ b/data/registry/instrumentation-dotnet-aspnetcore.yml @@ -18,4 +18,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Instrumentation.AspNetCore - version: 1.8.0 + version: 1.8.1 diff --git a/data/registry/instrumentation-dotnet-aws.yml b/data/registry/instrumentation-dotnet-aws.yml index c2d954e6ed22..170f515e7f4a 100644 --- a/data/registry/instrumentation-dotnet-aws.yml +++ b/data/registry/instrumentation-dotnet-aws.yml @@ -19,4 +19,4 @@ createdAt: 2022-10-28 package: registry: nuget name: OpenTelemetry.Instrumentation.AWS - version: 1.1.0-beta.3 + version: 1.1.0-beta.4 diff --git a/data/registry/instrumentation-dotnet-http.yml b/data/registry/instrumentation-dotnet-http.yml index a15f6c7b05c4..80b1fcbf4cb3 100644 --- a/data/registry/instrumentation-dotnet-http.yml +++ b/data/registry/instrumentation-dotnet-http.yml @@ -18,4 +18,4 @@ createdAt: 2022-11-07 package: registry: nuget name: OpenTelemetry.Instrumentation.Http - version: 1.8.0 + version: 1.8.1 diff --git a/data/registry/instrumentation-dotnet-instrumentation-aws.yml b/data/registry/instrumentation-dotnet-instrumentation-aws.yml index 3b6a34d1b627..4bbe2df1847c 100644 --- a/data/registry/instrumentation-dotnet-instrumentation-aws.yml +++ b/data/registry/instrumentation-dotnet-instrumentation-aws.yml @@ -15,4 +15,4 @@ createdAt: 2022-10-28 package: registry: nuget name: OpenTelemetry.Instrumentation.AWS - version: 1.1.0-beta.3 + version: 1.1.0-beta.4 diff --git a/data/registry/instrumentation-dotnet-kafkaflow.yml b/data/registry/instrumentation-dotnet-kafkaflow.yml index f9be006be945..7deb2137ed01 100644 --- a/data/registry/instrumentation-dotnet-kafkaflow.yml +++ b/data/registry/instrumentation-dotnet-kafkaflow.yml @@ -20,4 +20,4 @@ isFirstParty: true package: name: KafkaFlow.OpenTelemetry registry: nuget - version: 3.0.6 + version: 3.8.0 diff --git a/data/registry/instrumentation-dotnet-owin.yml b/data/registry/instrumentation-dotnet-owin.yml index d91c35644355..0bad2de40dc2 100644 --- a/data/registry/instrumentation-dotnet-owin.yml +++ b/data/registry/instrumentation-dotnet-owin.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-28 package: registry: nuget name: OpenTelemetry.Instrumentation.Owin - version: 1.0.0-rc.4 + version: 1.0.0-rc.6 diff --git a/data/registry/instrumentation-erlang-bandit.yml b/data/registry/instrumentation-erlang-bandit.yml new file mode 100644 index 000000000000..8df810ac7929 --- /dev/null +++ b/data/registry/instrumentation-erlang-bandit.yml @@ -0,0 +1,20 @@ +title: OpentelemetryBandit +registryType: instrumentation +language: erlang +tags: + - bandit + - instrumentation + - erlang +urls: + repo: https://github.com/open-telemetry/opentelemetry-erlang-contrib/tree/main/instrumentation/opentelemetry_bandit +license: Apache 2.0 +description: + Telemetry handler that creates OpenTelemetry spans from [Bandit + events](https://hexdocs.pm/bandit/Bandit.Telemetry.html#content). +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: hex + name: opentelemetry_bandit + version: 0.1.4 diff --git a/data/registry/instrumentation-go-xsam-database-sql.yml b/data/registry/instrumentation-go-xsam-database-sql.yml index 0cdf89d12705..987327613d81 100644 --- a/data/registry/instrumentation-go-xsam-database-sql.yml +++ b/data/registry/instrumentation-go-xsam-database-sql.yml @@ -15,7 +15,7 @@ authors: package: name: github.com/XSAM/otelsql registry: go - version: v0.29.0 + version: v0.31.0 urls: repo: https://github.com/XSAM/otelsql createdAt: 2021-10-12 diff --git a/data/registry/instrumentation-java-finaglehttp.yml b/data/registry/instrumentation-java-finaglehttp.yml new file mode 100644 index 000000000000..38f6c9433ad7 --- /dev/null +++ b/data/registry/instrumentation-java-finaglehttp.yml @@ -0,0 +1,17 @@ +title: Finagle HTTP Instrumentation +registryType: instrumentation +language: java +tags: + - finagle + - http + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/finagle-http-23.11 +license: Apache 2.0 +description: + This library provides a Finagle HTTP Instrumentation to track requests through + OpenTelemetry. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-java-graphqljava.yml b/data/registry/instrumentation-java-graphqljava.yml index c9f6ebee5103..cb0e327dd028 100644 --- a/data/registry/instrumentation-java-graphqljava.yml +++ b/data/registry/instrumentation-java-graphqljava.yml @@ -10,5 +10,5 @@ description: This package provides an instrumentation library for GraphQL Java authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/graphql-java-12.0 + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/graphql-java createdAt: 2022-10-27 diff --git a/data/registry/instrumentation-java-mybatis.yml b/data/registry/instrumentation-java-mybatis.yml new file mode 100644 index 000000000000..f7033f504652 --- /dev/null +++ b/data/registry/instrumentation-java-mybatis.yml @@ -0,0 +1,15 @@ +# cSpell:ignore batis mybatis +title: MyBatis Instrumentation +registryType: instrumentation +language: java +tags: + - mybatis + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/mybatis-3.2 +license: Apache 2.0 +description: Instrumentation for MyBatis +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-java-pekkoactor.yml b/data/registry/instrumentation-java-pekkoactor.yml index 7aa78b1df249..aaa8a37c0371 100644 --- a/data/registry/instrumentation-java-pekkoactor.yml +++ b/data/registry/instrumentation-java-pekkoactor.yml @@ -12,5 +12,5 @@ description: This library provides an Apache Pekko Actor instrumentation. authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/pekko-actor-1.0 + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/pekko/pekko-actor-1.0 createdAt: 2022-10-27 diff --git a/data/registry/instrumentation-java-pekkohttp.yml b/data/registry/instrumentation-java-pekkohttp.yml index ada654c7b6e2..84e44182a523 100644 --- a/data/registry/instrumentation-java-pekkohttp.yml +++ b/data/registry/instrumentation-java-pekkohttp.yml @@ -12,5 +12,5 @@ description: This library provides an Apache Pekko HTTP instrumentation authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/pekko-http-1.0 + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/pekko/pekko-http-1.0 createdAt: 2020-11-05 diff --git a/data/registry/instrumentation-java-xxljob.yml b/data/registry/instrumentation-java-xxljob.yml new file mode 100644 index 000000000000..2362482dd177 --- /dev/null +++ b/data/registry/instrumentation-java-xxljob.yml @@ -0,0 +1,14 @@ +title: XXL-JOB Instrumentation +registryType: instrumentation +language: java +tags: + - xxl-job + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/xxl-job +license: Apache 2.0 +description: Instrumentation for XXL-JOB +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-js-amqplib.yml b/data/registry/instrumentation-js-amqplib.yml index 67a0fef7bce7..fb1054a0c014 100644 --- a/data/registry/instrumentation-js-amqplib.yml +++ b/data/registry/instrumentation-js-amqplib.yml @@ -14,7 +14,7 @@ authors: package: name: '@opentelemetry/instrumentation-amqplib' registry: npm - version: 0.36.0 + version: 0.37.0 urls: repo: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/instrumentation-amqplib createdAt: 2020-06-15 diff --git a/data/registry/instrumentation-js-angular.yml b/data/registry/instrumentation-js-angular.yml index 12806cebdf68..dd446493e075 100644 --- a/data/registry/instrumentation-js-angular.yml +++ b/data/registry/instrumentation-js-angular.yml @@ -18,4 +18,4 @@ createdAt: 2020-06-30 package: name: '@jufab/opentelemetry-angular-interceptor' registry: npm - version: 1.8.0-2 + version: 1.8.0-3 diff --git a/data/registry/instrumentation-js-aws-lambda.yml b/data/registry/instrumentation-js-aws-lambda.yml index ec79551d99f2..cd3b11a05621 100644 --- a/data/registry/instrumentation-js-aws-lambda.yml +++ b/data/registry/instrumentation-js-aws-lambda.yml @@ -15,4 +15,4 @@ createdAt: 2021-07-08 package: name: '@opentelemetry/instrumentation-aws-lambda' registry: npm - version: 0.40.0 + version: 0.41.0 diff --git a/data/registry/instrumentation-js-aws-sdk.yml b/data/registry/instrumentation-js-aws-sdk.yml index 3aac6a579424..e7a6513efb92 100644 --- a/data/registry/instrumentation-js-aws-sdk.yml +++ b/data/registry/instrumentation-js-aws-sdk.yml @@ -21,4 +21,4 @@ createdAt: 2020-06-15 package: name: '@opentelemetry/instrumentation-aws-sdk' registry: npm - version: 0.40.0 + version: 0.41.0 diff --git a/data/registry/instrumentation-js-bunyan.yml b/data/registry/instrumentation-js-bunyan.yml index 0f2b7c1c536a..510f9cf75f9c 100644 --- a/data/registry/instrumentation-js-bunyan.yml +++ b/data/registry/instrumentation-js-bunyan.yml @@ -16,4 +16,4 @@ createdAt: 2021-07-08 package: name: '@opentelemetry/instrumentation-bunyan' registry: npm - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-cassandra-driver.yml b/data/registry/instrumentation-js-cassandra-driver.yml index b0598a1b25eb..5418094ed682 100644 --- a/data/registry/instrumentation-js-cassandra-driver.yml +++ b/data/registry/instrumentation-js-cassandra-driver.yml @@ -16,4 +16,4 @@ createdAt: 2021-07-08 package: name: '@opentelemetry/instrumentation-cassandra-driver' registry: npm - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-cassandra.yml b/data/registry/instrumentation-js-cassandra.yml index 49fcdf367811..a708a54e7044 100644 --- a/data/registry/instrumentation-js-cassandra.yml +++ b/data/registry/instrumentation-js-cassandra.yml @@ -17,4 +17,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-cassandra-driver' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-cerbos.yml b/data/registry/instrumentation-js-cerbos.yml index 2d9d1a0c90e7..2633948f75c6 100644 --- a/data/registry/instrumentation-js-cerbos.yml +++ b/data/registry/instrumentation-js-cerbos.yml @@ -18,5 +18,5 @@ createdAt: 2023-09-13 package: name: '@cerbos/opentelemetry' registry: npm - version: 0.4.4 + version: 0.4.6 isFirstParty: true diff --git a/data/registry/instrumentation-js-connect.yml b/data/registry/instrumentation-js-connect.yml index 03b0c536fbe6..03fdb79a4142 100644 --- a/data/registry/instrumentation-js-connect.yml +++ b/data/registry/instrumentation-js-connect.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: name: '@opentelemetry/instrumentation-connect' registry: npm - version: 0.35.0 + version: 0.36.0 diff --git a/data/registry/instrumentation-js-cucumber.yml b/data/registry/instrumentation-js-cucumber.yml index 39c8eb382e60..43a8de86e53d 100644 --- a/data/registry/instrumentation-js-cucumber.yml +++ b/data/registry/instrumentation-js-cucumber.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-cucumber' - version: 0.5.0 + version: 0.6.0 diff --git a/data/registry/instrumentation-js-dataloader.yml b/data/registry/instrumentation-js-dataloader.yml index 8e3f31e53038..081dc110d472 100644 --- a/data/registry/instrumentation-js-dataloader.yml +++ b/data/registry/instrumentation-js-dataloader.yml @@ -15,4 +15,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-dataloader' - version: 0.8.0 + version: 0.9.0 diff --git a/data/registry/instrumentation-js-dns.yml b/data/registry/instrumentation-js-dns.yml index 0a885b37d5d2..26c44a4e1bde 100644 --- a/data/registry/instrumentation-js-dns.yml +++ b/data/registry/instrumentation-js-dns.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-dns' - version: 0.35.0 + version: 0.36.1 diff --git a/data/registry/instrumentation-js-document-load.yml b/data/registry/instrumentation-js-document-load.yml index 36156997e6d5..0cdc22403de8 100644 --- a/data/registry/instrumentation-js-document-load.yml +++ b/data/registry/instrumentation-js-document-load.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-document-load' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-express.yml b/data/registry/instrumentation-js-express.yml index 4c84c3ae931d..e67b32dcfc9e 100644 --- a/data/registry/instrumentation-js-express.yml +++ b/data/registry/instrumentation-js-express.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-express' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-fastify.yml b/data/registry/instrumentation-js-fastify.yml index a48ec66b3c0a..b6caa43d015a 100644 --- a/data/registry/instrumentation-js-fastify.yml +++ b/data/registry/instrumentation-js-fastify.yml @@ -15,4 +15,4 @@ createdAt: 2020-08-28 package: registry: npm name: '@opentelemetry/instrumentation-fastify' - version: 0.35.0 + version: 0.36.1 diff --git a/data/registry/instrumentation-js-fetch.yml b/data/registry/instrumentation-js-fetch.yml index a290a8a67404..ff95cee49f73 100644 --- a/data/registry/instrumentation-js-fetch.yml +++ b/data/registry/instrumentation-js-fetch.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-fetch' - version: 0.50.0 + version: 0.51.1 diff --git a/data/registry/instrumentation-js-fs.yml b/data/registry/instrumentation-js-fs.yml index 84e1cfe6b861..850204e06066 100644 --- a/data/registry/instrumentation-js-fs.yml +++ b/data/registry/instrumentation-js-fs.yml @@ -15,4 +15,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-fs' - version: 0.11.0 + version: 0.12.0 diff --git a/data/registry/instrumentation-js-generic-pool.yml b/data/registry/instrumentation-js-generic-pool.yml index 6bdeac780705..497908825ee5 100644 --- a/data/registry/instrumentation-js-generic-pool.yml +++ b/data/registry/instrumentation-js-generic-pool.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-generic-pool' - version: 0.35.0 + version: 0.36.0 diff --git a/data/registry/instrumentation-js-graphql.yml b/data/registry/instrumentation-js-graphql.yml index 11f9d8da6bcb..bcf0eca082a6 100644 --- a/data/registry/instrumentation-js-graphql.yml +++ b/data/registry/instrumentation-js-graphql.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-graphql' - version: 0.39.0 + version: 0.40.0 diff --git a/data/registry/instrumentation-js-grpc.yml b/data/registry/instrumentation-js-grpc.yml index a8729e1856fd..95716bc69966 100644 --- a/data/registry/instrumentation-js-grpc.yml +++ b/data/registry/instrumentation-js-grpc.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-grpc' - version: 0.50.0 + version: 0.51.1 diff --git a/data/registry/instrumentation-js-hapi.yml b/data/registry/instrumentation-js-hapi.yml index 970c5b87660a..9698f26d6c49 100644 --- a/data/registry/instrumentation-js-hapi.yml +++ b/data/registry/instrumentation-js-hapi.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-hapi' - version: 0.36.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-http.yml b/data/registry/instrumentation-js-http.yml index 441e61323b17..cf46f8807ce8 100644 --- a/data/registry/instrumentation-js-http.yml +++ b/data/registry/instrumentation-js-http.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-http' - version: 0.50.0 + version: 0.51.1 diff --git a/data/registry/instrumentation-js-ioredis.yml b/data/registry/instrumentation-js-ioredis.yml index 4ecfdafac291..1aed1e3b72e1 100644 --- a/data/registry/instrumentation-js-ioredis.yml +++ b/data/registry/instrumentation-js-ioredis.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-ioredis' - version: 0.39.0 + version: 0.40.0 diff --git a/data/registry/instrumentation-js-knex.yml b/data/registry/instrumentation-js-knex.yml index 64314246ad6d..84a3b46a49f1 100644 --- a/data/registry/instrumentation-js-knex.yml +++ b/data/registry/instrumentation-js-knex.yml @@ -17,4 +17,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-knex' - version: 0.35.0 + version: 0.36.1 diff --git a/data/registry/instrumentation-js-koa.yml b/data/registry/instrumentation-js-koa.yml index a61d3dac4b7d..cb2b1bbc4c71 100644 --- a/data/registry/instrumentation-js-koa.yml +++ b/data/registry/instrumentation-js-koa.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-koa' - version: 0.39.0 + version: 0.40.0 diff --git a/data/registry/instrumentation-js-long-task.yml b/data/registry/instrumentation-js-long-task.yml index 5320293b5e2f..1484467d0c81 100644 --- a/data/registry/instrumentation-js-long-task.yml +++ b/data/registry/instrumentation-js-long-task.yml @@ -14,4 +14,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-long-task' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-lru-memoizer.yml b/data/registry/instrumentation-js-lru-memoizer.yml index 8863ef4b7a24..e2be7d71c494 100644 --- a/data/registry/instrumentation-js-lru-memoizer.yml +++ b/data/registry/instrumentation-js-lru-memoizer.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-lru-memoizer' - version: 0.36.0 + version: 0.37.0 diff --git a/data/registry/instrumentation-js-memcached.yml b/data/registry/instrumentation-js-memcached.yml index 397f2fc678c2..25463a71a18e 100644 --- a/data/registry/instrumentation-js-memcached.yml +++ b/data/registry/instrumentation-js-memcached.yml @@ -15,4 +15,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-memcached' - version: 0.35.0 + version: 0.36.0 diff --git a/data/registry/instrumentation-js-mongodb.yml b/data/registry/instrumentation-js-mongodb.yml index 739df76f8c0f..b923e7ad69b2 100644 --- a/data/registry/instrumentation-js-mongodb.yml +++ b/data/registry/instrumentation-js-mongodb.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-mongodb' - version: 0.42.0 + version: 0.43.0 diff --git a/data/registry/instrumentation-js-mongoose-instrumentation.yml b/data/registry/instrumentation-js-mongoose-instrumentation.yml index f200dc9953f2..60cc9f923ff4 100644 --- a/data/registry/instrumentation-js-mongoose-instrumentation.yml +++ b/data/registry/instrumentation-js-mongoose-instrumentation.yml @@ -16,4 +16,4 @@ createdAt: 2021-02-17 package: registry: npm name: '@opentelemetry/instrumentation-mongoose' - version: 0.37.0 + version: 0.38.1 diff --git a/data/registry/instrumentation-js-mysql.yml b/data/registry/instrumentation-js-mysql.yml index 91175cc6f664..0cc0911a60cc 100644 --- a/data/registry/instrumentation-js-mysql.yml +++ b/data/registry/instrumentation-js-mysql.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-mysql' - version: 0.37.0 + version: 0.38.1 diff --git a/data/registry/instrumentation-js-mysql2.yml b/data/registry/instrumentation-js-mysql2.yml index 0578fc7ea8b7..5898a10dac3c 100644 --- a/data/registry/instrumentation-js-mysql2.yml +++ b/data/registry/instrumentation-js-mysql2.yml @@ -18,4 +18,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-mysql2' - version: 0.37.0 + version: 0.38.1 diff --git a/data/registry/instrumentation-js-nestjs-core.yml b/data/registry/instrumentation-js-nestjs-core.yml index 2de9f7a0950e..c94e856c846e 100644 --- a/data/registry/instrumentation-js-nestjs-core.yml +++ b/data/registry/instrumentation-js-nestjs-core.yml @@ -17,4 +17,4 @@ createdAt: 2021-07-09 package: registry: npm name: '@opentelemetry/instrumentation-nestjs-core' - version: 0.36.0 + version: 0.37.1 diff --git a/data/registry/instrumentation-js-nestjs.yml b/data/registry/instrumentation-js-nestjs.yml index 191ab728bb9c..ff3155566531 100644 --- a/data/registry/instrumentation-js-nestjs.yml +++ b/data/registry/instrumentation-js-nestjs.yml @@ -16,4 +16,4 @@ createdAt: 2021-07-09 package: registry: npm name: '@opentelemetry/instrumentation-nestjs-core' - version: 0.36.0 + version: 0.37.1 diff --git a/data/registry/instrumentation-js-net.yml b/data/registry/instrumentation-js-net.yml index 91b59e5307ca..9cc58eda0788 100644 --- a/data/registry/instrumentation-js-net.yml +++ b/data/registry/instrumentation-js-net.yml @@ -14,4 +14,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-net' - version: 0.35.0 + version: 0.36.0 diff --git a/data/registry/instrumentation-js-pg.yml b/data/registry/instrumentation-js-pg.yml index 5110ebc16a17..c3313aea1107 100644 --- a/data/registry/instrumentation-js-pg.yml +++ b/data/registry/instrumentation-js-pg.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-pg' - version: 0.40.0 + version: 0.41.0 diff --git a/data/registry/instrumentation-js-pillarjs-router.yml b/data/registry/instrumentation-js-pillarjs-router.yml index 0861bfd5fdc6..851f6e33f12a 100644 --- a/data/registry/instrumentation-js-pillarjs-router.yml +++ b/data/registry/instrumentation-js-pillarjs-router.yml @@ -20,4 +20,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-restify' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-pino.yml b/data/registry/instrumentation-js-pino.yml index 21f1afb0988c..dd85778f897e 100644 --- a/data/registry/instrumentation-js-pino.yml +++ b/data/registry/instrumentation-js-pino.yml @@ -16,4 +16,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-pino' - version: 0.37.0 + version: 0.39.0 diff --git a/data/registry/instrumentation-js-postgres.yml b/data/registry/instrumentation-js-postgres.yml index 56db2613caf7..43997234df7b 100644 --- a/data/registry/instrumentation-js-postgres.yml +++ b/data/registry/instrumentation-js-postgres.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-pg' - version: 0.40.0 + version: 0.41.0 diff --git a/data/registry/instrumentation-js-prisma.yml b/data/registry/instrumentation-js-prisma.yml index aef9d6ed05a8..7464d773d70e 100644 --- a/data/registry/instrumentation-js-prisma.yml +++ b/data/registry/instrumentation-js-prisma.yml @@ -17,4 +17,4 @@ createdAt: 2022-08-25 package: registry: npm name: '@prisma/instrumentation' - version: 5.12.1 + version: 5.13.0 diff --git a/data/registry/instrumentation-js-react-load.yml b/data/registry/instrumentation-js-react-load.yml index d99ba5a94659..d6cd7745e55c 100644 --- a/data/registry/instrumentation-js-react-load.yml +++ b/data/registry/instrumentation-js-react-load.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/plugin-react-load' - version: 0.30.0 + version: 0.30.1 diff --git a/data/registry/instrumentation-js-redis-4.yml b/data/registry/instrumentation-js-redis-4.yml index c5f53df2383c..7c33187bbe02 100644 --- a/data/registry/instrumentation-js-redis-4.yml +++ b/data/registry/instrumentation-js-redis-4.yml @@ -14,4 +14,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-redis-4' - version: 0.38.0 + version: 0.39.0 diff --git a/data/registry/instrumentation-js-redis.yml b/data/registry/instrumentation-js-redis.yml index def29c6e9be6..5ce587460efc 100644 --- a/data/registry/instrumentation-js-redis.yml +++ b/data/registry/instrumentation-js-redis.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-redis' - version: 0.38.0 + version: 0.39.1 diff --git a/data/registry/instrumentation-js-remix.yml b/data/registry/instrumentation-js-remix.yml index 04f3d83c3c23..7db6a301efee 100644 --- a/data/registry/instrumentation-js-remix.yml +++ b/data/registry/instrumentation-js-remix.yml @@ -17,4 +17,4 @@ createdAt: 2022-02-10 package: registry: npm name: opentelemetry-instrumentation-remix - version: 0.6.0 + version: 0.7.0 diff --git a/data/registry/instrumentation-js-restify.yml b/data/registry/instrumentation-js-restify.yml index de0262a362ce..0d5bd5b6e53e 100644 --- a/data/registry/instrumentation-js-restify.yml +++ b/data/registry/instrumentation-js-restify.yml @@ -15,4 +15,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-restify' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-router.yml b/data/registry/instrumentation-js-router.yml index f621fabfdf1b..9205e6c72b2f 100644 --- a/data/registry/instrumentation-js-router.yml +++ b/data/registry/instrumentation-js-router.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-router' - version: 0.36.0 + version: 0.37.0 diff --git a/data/registry/instrumentation-js-runtimenode.yml b/data/registry/instrumentation-js-runtimenode.yml new file mode 100644 index 000000000000..60ef87b59a3c --- /dev/null +++ b/data/registry/instrumentation-js-runtimenode.yml @@ -0,0 +1,22 @@ +title: OpenTelemetry Node.js Runtime Metrics Instrumentation +registryType: instrumentation +language: js +tags: + - runtime + - node + - instrumentation + - js +urls: + repo: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/instrumentation-runtime-node +license: Apache 2.0 +description: + This module provides automatic metric instrumentation that exposes + measurements from the [Performance measurement + APIs](https://nodejs.org/api/perf_hooks.html) (i.e. `perf_hooks`). +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: npm + name: '@opentelemetry/instrumentation-runtime-node' + version: 0.4.0 diff --git a/data/registry/instrumentation-js-socket.io.yml b/data/registry/instrumentation-js-socket.io.yml index 2a76cc319a75..2d42ac3c64ad 100644 --- a/data/registry/instrumentation-js-socket.io.yml +++ b/data/registry/instrumentation-js-socket.io.yml @@ -16,4 +16,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-socket.io' - version: 0.38.0 + version: 0.39.0 diff --git a/data/registry/instrumentation-js-tedious.yml b/data/registry/instrumentation-js-tedious.yml index e47d68abd9d8..0bebca77ca4a 100644 --- a/data/registry/instrumentation-js-tedious.yml +++ b/data/registry/instrumentation-js-tedious.yml @@ -16,4 +16,4 @@ createdAt: 2022-10-27 package: registry: npm name: '@opentelemetry/instrumentation-tedious' - version: 0.9.0 + version: 0.10.1 diff --git a/data/registry/instrumentation-js-undici.yml b/data/registry/instrumentation-js-undici.yml new file mode 100644 index 000000000000..06bef1313d43 --- /dev/null +++ b/data/registry/instrumentation-js-undici.yml @@ -0,0 +1,22 @@ +# cSpell:ignore undici +title: OpenTelemetry Undici/fetch Instrumentation for Node.js +registryType: instrumentation +language: js +tags: + - undici + - instrumentation + - js +urls: + repo: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/plugins/node/instrumentation-undici +license: Apache 2.0 +description: + This module provides automatic instrumentation for + [`undici`](https://undici.nodejs.org/) and Node.js global + [`fetch`](https://nodejs.org/docs/latest/api/globals.html#fetch) API. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: npm + name: '@opentelemetry/instrumentation-undici' + version: 0.2.0 diff --git a/data/registry/instrumentation-js-user-interaction.yml b/data/registry/instrumentation-js-user-interaction.yml index 68766b845cda..2a6609fad993 100644 --- a/data/registry/instrumentation-js-user-interaction.yml +++ b/data/registry/instrumentation-js-user-interaction.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-user-interaction' - version: 0.37.0 + version: 0.38.0 diff --git a/data/registry/instrumentation-js-winston.yml b/data/registry/instrumentation-js-winston.yml index 568dc99d657b..291ba8f5cdb4 100644 --- a/data/registry/instrumentation-js-winston.yml +++ b/data/registry/instrumentation-js-winston.yml @@ -16,4 +16,4 @@ createdAt: 2021-07-08 package: registry: npm name: '@opentelemetry/instrumentation-winston' - version: 0.36.0 + version: 0.37.0 diff --git a/data/registry/instrumentation-js-xml-http-request.yml b/data/registry/instrumentation-js-xml-http-request.yml index e91e6ac24558..7b3bbf88fad9 100644 --- a/data/registry/instrumentation-js-xml-http-request.yml +++ b/data/registry/instrumentation-js-xml-http-request.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: npm name: '@opentelemetry/instrumentation-xml-http-request' - version: 0.50.0 + version: 0.51.1 diff --git a/data/registry/instrumentation-php-httpasyncclient.yml b/data/registry/instrumentation-php-httpasyncclient.yml index aff65641b336..b355d896109e 100644 --- a/data/registry/instrumentation-php-httpasyncclient.yml +++ b/data/registry/instrumentation-php-httpasyncclient.yml @@ -16,4 +16,4 @@ createdAt: 2023-05-22 package: registry: packagist name: open-telemetry/opentelemetry-auto-http-async - version: 1.0.0beta5 + version: 1.0.0 diff --git a/data/registry/instrumentation-php-laravel.yml b/data/registry/instrumentation-php-laravel.yml index 9502051108a0..72c58f48144e 100644 --- a/data/registry/instrumentation-php-laravel.yml +++ b/data/registry/instrumentation-php-laravel.yml @@ -15,4 +15,4 @@ createdAt: 2023-05-22 package: registry: packagist name: open-telemetry/opentelemetry-auto-laravel - version: 0.0.24 + version: 0.0.25 diff --git a/data/registry/instrumentation-php-pdo.yml b/data/registry/instrumentation-php-pdo.yml index efbb5e41cc75..acbc8717eb10 100644 --- a/data/registry/instrumentation-php-pdo.yml +++ b/data/registry/instrumentation-php-pdo.yml @@ -15,4 +15,4 @@ createdAt: 2023-05-22 package: registry: packagist name: open-telemetry/opentelemetry-auto-pdo - version: 0.0.12 + version: 0.0.13 diff --git a/data/registry/instrumentation-php-psr16.yml b/data/registry/instrumentation-php-psr16.yml new file mode 100644 index 000000000000..6e83ebf8c7d4 --- /dev/null +++ b/data/registry/instrumentation-php-psr16.yml @@ -0,0 +1,20 @@ +title: OpenTelemetry PSR-16 auto-instrumentation +registryType: instrumentation +language: php +tags: + - psr16 + - instrumentation + - php +urls: + repo: https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/Psr16 +license: Apache 2.0 +description: + Auto-instrumentation hooks are registered via composer, and spans will + automatically be created for each PSR-16 cache operation. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 +package: + registry: packagist + name: open-telemetry/opentelemetry-auto-psr16 + version: 0.0.1 diff --git a/data/registry/instrumentation-php-slim.yml b/data/registry/instrumentation-php-slim.yml index e5b1b9001b30..bf2eb88bfabe 100644 --- a/data/registry/instrumentation-php-slim.yml +++ b/data/registry/instrumentation-php-slim.yml @@ -15,4 +15,4 @@ createdAt: 2022-12-14 package: registry: packagist name: open-telemetry/opentelemetry-auto-slim - version: 1.0.4 + version: 1.0.5 diff --git a/data/registry/instrumentation-php-symfony.yml b/data/registry/instrumentation-php-symfony.yml index 32840a04dac3..87afd3968906 100644 --- a/data/registry/instrumentation-php-symfony.yml +++ b/data/registry/instrumentation-php-symfony.yml @@ -15,4 +15,4 @@ createdAt: 2023-05-22 package: registry: packagist name: open-telemetry/opentelemetry-auto-symfony - version: 1.0.0beta23 + version: 1.0.0beta24 diff --git a/data/registry/instrumentation-python-asyncio.yml b/data/registry/instrumentation-python-asyncio.yml new file mode 100644 index 000000000000..2e0ad887652a --- /dev/null +++ b/data/registry/instrumentation-python-asyncio.yml @@ -0,0 +1,15 @@ +# cSpell:ignore asyncio +title: OpenTelemetry asyncio Instrumentation +registryType: instrumentation +language: python +tags: + - asyncio + - instrumentation + - python +urls: + repo: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation/opentelemetry-instrumentation-asyncio +license: Apache 2.0 +description: Tracing Requests Made by the asyncio Library +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-python-psycopg.yml b/data/registry/instrumentation-python-psycopg.yml new file mode 100644 index 000000000000..ccf8aedca146 --- /dev/null +++ b/data/registry/instrumentation-python-psycopg.yml @@ -0,0 +1,15 @@ +# cSpell:ignore psycopg +title: OpenTelemetry Psycopg Instrumentation +registryType: instrumentation +language: python +tags: + - psycopg + - instrumentation + - python +urls: + repo: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation/opentelemetry-instrumentation-psycopg +license: Apache 2.0 +description: Instrumentation for the Psycopg library +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-python-threading.yml b/data/registry/instrumentation-python-threading.yml new file mode 100644 index 000000000000..63ff975b1dd6 --- /dev/null +++ b/data/registry/instrumentation-python-threading.yml @@ -0,0 +1,16 @@ +title: OpenTelemetry threading Instrumentation +registryType: instrumentation +language: python +tags: + - threading + - instrumentation + - python +urls: + repo: https://github.com/open-telemetry/opentelemetry-python-contrib/tree/main/instrumentation/opentelemetry-instrumentation-threading +license: Apache 2.0 +description: + This library provides instrumentation for the `threading` module to ensure + that +authors: + - name: OpenTelemetry Authors +createdAt: 2024-04-18 diff --git a/data/registry/instrumentation-python-watsonx.yml b/data/registry/instrumentation-python-watsonx.yml new file mode 100644 index 000000000000..bf25e33adde5 --- /dev/null +++ b/data/registry/instrumentation-python-watsonx.yml @@ -0,0 +1,18 @@ +# cSpell:ignore watsonx Instana +title: IBM Watsonx Instrumentation +registryType: instrumentation +language: python +tags: + - python + - instrumentation + - IBM + - Watsonx + - Instana +license: Apache 2.0 +description: + Instrumentation for IBM Watsonx LLMs (prompts logging, tokens, etc.) +authors: + - name: IBM Instana +urls: + repo: https://github.com/traceloop/openllmetry/tree/main/packages/opentelemetry-instrumentation-watsonx +createdAt: 2024-01-22 diff --git a/data/registry/instrumentation-ruby-active-record.yml b/data/registry/instrumentation-ruby-active-record.yml index c39a51bb967d..8c42c4a63afe 100644 --- a/data/registry/instrumentation-ruby-active-record.yml +++ b/data/registry/instrumentation-ruby-active-record.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-active_record - version: 0.7.1 + version: 0.7.2 diff --git a/data/registry/instrumentation-ruby-aws-sdk.yml b/data/registry/instrumentation-ruby-aws-sdk.yml index 259f4c91dca7..ed6eacebeeaa 100644 --- a/data/registry/instrumentation-ruby-aws-sdk.yml +++ b/data/registry/instrumentation-ruby-aws-sdk.yml @@ -18,4 +18,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-aws_sdk - version: 0.5.1 + version: 0.5.2 diff --git a/data/registry/instrumentation-ruby-bunny.yml b/data/registry/instrumentation-ruby-bunny.yml index 499cc9e84422..7404a3960d04 100644 --- a/data/registry/instrumentation-ruby-bunny.yml +++ b/data/registry/instrumentation-ruby-bunny.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-bunny - version: 0.21.2 + version: 0.21.3 diff --git a/data/registry/instrumentation-ruby-concurrent-ruby.yml b/data/registry/instrumentation-ruby-concurrent-ruby.yml index 3fcfc2932d6c..b28d305c7120 100644 --- a/data/registry/instrumentation-ruby-concurrent-ruby.yml +++ b/data/registry/instrumentation-ruby-concurrent-ruby.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-concurrent_ruby - version: 0.21.2 + version: 0.21.3 diff --git a/data/registry/instrumentation-ruby-dalli.yml b/data/registry/instrumentation-ruby-dalli.yml index a1b87dae3fd3..ecb3a2e260a4 100644 --- a/data/registry/instrumentation-ruby-dalli.yml +++ b/data/registry/instrumentation-ruby-dalli.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-dalli - version: 0.25.0 + version: 0.25.2 diff --git a/data/registry/instrumentation-ruby-delayed-job.yml b/data/registry/instrumentation-ruby-delayed-job.yml index f42434584462..bff2d86b0dee 100644 --- a/data/registry/instrumentation-ruby-delayed-job.yml +++ b/data/registry/instrumentation-ruby-delayed-job.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-delayed_job - version: 0.22.1 + version: 0.22.2 diff --git a/data/registry/instrumentation-ruby-ethon.yml b/data/registry/instrumentation-ruby-ethon.yml index f73c77c7a9b4..5e10c103b83c 100644 --- a/data/registry/instrumentation-ruby-ethon.yml +++ b/data/registry/instrumentation-ruby-ethon.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-ethon - version: 0.21.3 + version: 0.21.5 diff --git a/data/registry/instrumentation-ruby-excon.yml b/data/registry/instrumentation-ruby-excon.yml index 509bf9e2b75b..bf6ca048c0c0 100644 --- a/data/registry/instrumentation-ruby-excon.yml +++ b/data/registry/instrumentation-ruby-excon.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-excon - version: 0.22.0 + version: 0.22.2 diff --git a/data/registry/instrumentation-ruby-faraday.yml b/data/registry/instrumentation-ruby-faraday.yml index 2caa74d9c269..67b216f798dd 100644 --- a/data/registry/instrumentation-ruby-faraday.yml +++ b/data/registry/instrumentation-ruby-faraday.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-faraday - version: 0.24.1 + version: 0.24.3 diff --git a/data/registry/instrumentation-ruby-grape.yml b/data/registry/instrumentation-ruby-grape.yml index a37a6036dbce..e4f6ceda5380 100644 --- a/data/registry/instrumentation-ruby-grape.yml +++ b/data/registry/instrumentation-ruby-grape.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-27 package: registry: gems name: opentelemetry-instrumentation-grape - version: 0.1.6 + version: 0.1.7 diff --git a/data/registry/instrumentation-ruby-graphql.yml b/data/registry/instrumentation-ruby-graphql.yml index 9c2809d8d37d..45fce75987fe 100644 --- a/data/registry/instrumentation-ruby-graphql.yml +++ b/data/registry/instrumentation-ruby-graphql.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-graphql - version: 0.28.1 + version: 0.28.2 diff --git a/data/registry/instrumentation-ruby-gruf.yml b/data/registry/instrumentation-ruby-gruf.yml index 9aae41a2a0a8..bccb626b6854 100644 --- a/data/registry/instrumentation-ruby-gruf.yml +++ b/data/registry/instrumentation-ruby-gruf.yml @@ -17,4 +17,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-gruf - version: 0.2.0 + version: 0.2.1 diff --git a/data/registry/instrumentation-ruby-http-client.yml b/data/registry/instrumentation-ruby-http-client.yml index 6515249ea443..dfde3fe72060 100644 --- a/data/registry/instrumentation-ruby-http-client.yml +++ b/data/registry/instrumentation-ruby-http-client.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-http_client - version: 0.22.3 + version: 0.22.5 diff --git a/data/registry/instrumentation-ruby-http.yml b/data/registry/instrumentation-ruby-http.yml index 22c957732cd5..fa67cca1ecb8 100644 --- a/data/registry/instrumentation-ruby-http.yml +++ b/data/registry/instrumentation-ruby-http.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-http - version: 0.23.2 + version: 0.23.3 diff --git a/data/registry/instrumentation-ruby-httpx.yml b/data/registry/instrumentation-ruby-httpx.yml index 1e9c34f1d1e3..01423c9841c5 100644 --- a/data/registry/instrumentation-ruby-httpx.yml +++ b/data/registry/instrumentation-ruby-httpx.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: gems name: opentelemetry-instrumentation-httpx - version: 0.1.1 + version: 0.1.2 diff --git a/data/registry/instrumentation-ruby-koala.yml b/data/registry/instrumentation-ruby-koala.yml index 227df765359b..578919aad09e 100644 --- a/data/registry/instrumentation-ruby-koala.yml +++ b/data/registry/instrumentation-ruby-koala.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-koala - version: 0.20.2 + version: 0.20.4 diff --git a/data/registry/instrumentation-ruby-lmdb.yml b/data/registry/instrumentation-ruby-lmdb.yml index bf2b274160c0..0f4582232d0e 100644 --- a/data/registry/instrumentation-ruby-lmdb.yml +++ b/data/registry/instrumentation-ruby-lmdb.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-lmdb - version: 0.22.1 + version: 0.22.2 diff --git a/data/registry/instrumentation-ruby-mongo.yml b/data/registry/instrumentation-ruby-mongo.yml index bd21b63a5c00..ad6018a8ba7b 100644 --- a/data/registry/instrumentation-ruby-mongo.yml +++ b/data/registry/instrumentation-ruby-mongo.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-mongo - version: 0.22.2 + version: 0.22.3 diff --git a/data/registry/instrumentation-ruby-mysql2.yml b/data/registry/instrumentation-ruby-mysql2.yml index 185a90d324f4..8145a08d0651 100644 --- a/data/registry/instrumentation-ruby-mysql2.yml +++ b/data/registry/instrumentation-ruby-mysql2.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-mysql2 - version: 0.27.0 + version: 0.27.1 diff --git a/data/registry/instrumentation-ruby-net-http.yml b/data/registry/instrumentation-ruby-net-http.yml index 7f90862aeeea..7ff7c3f06f4f 100644 --- a/data/registry/instrumentation-ruby-net-http.yml +++ b/data/registry/instrumentation-ruby-net-http.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-net_http - version: 0.22.4 + version: 0.22.5 diff --git a/data/registry/instrumentation-ruby-pg.yml b/data/registry/instrumentation-ruby-pg.yml index 15ab13e20fca..9fd5480be1f1 100644 --- a/data/registry/instrumentation-ruby-pg.yml +++ b/data/registry/instrumentation-ruby-pg.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-pg - version: 0.27.1 + version: 0.27.3 diff --git a/data/registry/instrumentation-ruby-que.yml b/data/registry/instrumentation-ruby-que.yml index 175765be3037..9f1d68fc0d0d 100644 --- a/data/registry/instrumentation-ruby-que.yml +++ b/data/registry/instrumentation-ruby-que.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-que - version: 0.8.0 + version: 0.8.1 diff --git a/data/registry/instrumentation-ruby-racecar.yml b/data/registry/instrumentation-ruby-racecar.yml index abcc19dc758c..c1245fdf463e 100644 --- a/data/registry/instrumentation-ruby-racecar.yml +++ b/data/registry/instrumentation-ruby-racecar.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: gems name: opentelemetry-instrumentation-racecar - version: 0.3.1 + version: 0.3.2 diff --git a/data/registry/instrumentation-ruby-rack.yml b/data/registry/instrumentation-ruby-rack.yml index a687ec77fab2..5c3abca5ce82 100644 --- a/data/registry/instrumentation-ruby-rack.yml +++ b/data/registry/instrumentation-ruby-rack.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-rack - version: 0.24.1 + version: 0.24.4 diff --git a/data/registry/instrumentation-ruby-rails.yml b/data/registry/instrumentation-ruby-rails.yml index 81321aa1e119..e6cbd3b5ac37 100644 --- a/data/registry/instrumentation-ruby-rails.yml +++ b/data/registry/instrumentation-ruby-rails.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-rails - version: 0.30.0 + version: 0.30.1 diff --git a/data/registry/instrumentation-ruby-rake.yml b/data/registry/instrumentation-ruby-rake.yml index 0ddc0c6c615a..3cb37d73cdaa 100644 --- a/data/registry/instrumentation-ruby-rake.yml +++ b/data/registry/instrumentation-ruby-rake.yml @@ -17,4 +17,4 @@ createdAt: 2022-10-27 package: registry: gems name: opentelemetry-instrumentation-rake - version: 0.2.1 + version: 0.2.2 diff --git a/data/registry/instrumentation-ruby-rdkafka.yml b/data/registry/instrumentation-ruby-rdkafka.yml index a9da22a69d1c..60646c7e014a 100644 --- a/data/registry/instrumentation-ruby-rdkafka.yml +++ b/data/registry/instrumentation-ruby-rdkafka.yml @@ -18,4 +18,4 @@ createdAt: 2022-10-27 package: registry: gems name: opentelemetry-instrumentation-rdkafka - version: 0.4.3 + version: 0.4.5 diff --git a/data/registry/instrumentation-ruby-redis.yml b/data/registry/instrumentation-ruby-redis.yml index 4224103e56ef..9f29cd96ffc6 100644 --- a/data/registry/instrumentation-ruby-redis.yml +++ b/data/registry/instrumentation-ruby-redis.yml @@ -11,7 +11,7 @@ authors: package: registry: gems name: opentelemetry-instrumentation-redis - version: 0.25.3 + version: 0.25.5 urls: repo: https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/main/instrumentation/redis createdAt: 2020-11-09 diff --git a/data/registry/instrumentation-ruby-resque.yml b/data/registry/instrumentation-ruby-resque.yml index edd8aa56a266..7231757682fd 100644 --- a/data/registry/instrumentation-ruby-resque.yml +++ b/data/registry/instrumentation-ruby-resque.yml @@ -16,4 +16,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-resque - version: 0.5.1 + version: 0.5.2 diff --git a/data/registry/instrumentation-ruby-restclient.yml b/data/registry/instrumentation-ruby-restclient.yml index 69b177fd2107..4440bb92fc8b 100644 --- a/data/registry/instrumentation-ruby-restclient.yml +++ b/data/registry/instrumentation-ruby-restclient.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-restclient - version: 0.22.3 + version: 0.22.5 diff --git a/data/registry/instrumentation-ruby-rspec.yml b/data/registry/instrumentation-ruby-rspec.yml index 3e0fcbb79030..f83fb20f7f65 100644 --- a/data/registry/instrumentation-ruby-rspec.yml +++ b/data/registry/instrumentation-ruby-rspec.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-rspec - version: 0.3.2 + version: 0.3.3 diff --git a/data/registry/instrumentation-ruby-ruby-kafka.yml b/data/registry/instrumentation-ruby-ruby-kafka.yml index ae048c6bf9f6..0980b5114728 100644 --- a/data/registry/instrumentation-ruby-ruby-kafka.yml +++ b/data/registry/instrumentation-ruby-ruby-kafka.yml @@ -14,4 +14,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-ruby_kafka - version: 0.21.0 + version: 0.21.1 diff --git a/data/registry/instrumentation-ruby-sidekiq.yml b/data/registry/instrumentation-ruby-sidekiq.yml index f437e268e733..79d564eab253 100644 --- a/data/registry/instrumentation-ruby-sidekiq.yml +++ b/data/registry/instrumentation-ruby-sidekiq.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-sidekiq - version: 0.25.2 + version: 0.25.4 diff --git a/data/registry/instrumentation-ruby-sinatra.yml b/data/registry/instrumentation-ruby-sinatra.yml index 62354b48d5dc..e272bf5c5ca1 100644 --- a/data/registry/instrumentation-ruby-sinatra.yml +++ b/data/registry/instrumentation-ruby-sinatra.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-sinatra - version: 0.23.2 + version: 0.23.4 diff --git a/data/registry/instrumentation-ruby-trilogy.yml b/data/registry/instrumentation-ruby-trilogy.yml index f123d2da6d3f..be3151dd80ad 100644 --- a/data/registry/instrumentation-ruby-trilogy.yml +++ b/data/registry/instrumentation-ruby-trilogy.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-trilogy - version: 0.59.2 + version: 0.59.3 diff --git a/data/registry/otel-rust-sdk.yml b/data/registry/otel-rust-sdk.yml new file mode 100644 index 000000000000..50f7beec71e6 --- /dev/null +++ b/data/registry/otel-rust-sdk.yml @@ -0,0 +1,16 @@ +title: Rust SDK +registryType: core +language: rust +tags: + - rust +license: Apache 2.0 +description: The OpenTelemetry SDK for Rust. +authors: + - name: OpenTelemetry Authors +urls: + repo: https://github.com/open-telemetry/opentelemetry-rust +createdAt: 2020-02-04 +package: + registry: crates + name: opentelemetry_sdk + version: 0.22.1 diff --git a/data/registry/otel-rust.yml b/data/registry/otel-rust.yml index e33e0624dac3..ae5d83e78f18 100644 --- a/data/registry/otel-rust.yml +++ b/data/registry/otel-rust.yml @@ -4,7 +4,7 @@ language: rust tags: - rust license: Apache 2.0 -description: The OpenTelemetry API and SDK for Rust. +description: The OpenTelemetry API for Rust. authors: - name: OpenTelemetry Authors urls: @@ -13,4 +13,4 @@ createdAt: 2020-02-04 package: registry: crates name: opentelemetry - version: 0.21.0 + version: 0.22.0 diff --git a/data/registry/resource-detector-js-alibabacloud.yml b/data/registry/resource-detector-js-alibabacloud.yml index b5915407cbb3..d942a7d38132 100644 --- a/data/registry/resource-detector-js-alibabacloud.yml +++ b/data/registry/resource-detector-js-alibabacloud.yml @@ -16,4 +16,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-alibaba-cloud' - version: 0.28.8 + version: 0.28.9 diff --git a/data/registry/resource-detector-js-aws.yml b/data/registry/resource-detector-js-aws.yml index 8628f28c45ee..c49560d096fc 100644 --- a/data/registry/resource-detector-js-aws.yml +++ b/data/registry/resource-detector-js-aws.yml @@ -15,4 +15,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-aws' - version: 1.4.1 + version: 1.4.2 diff --git a/data/registry/resource-detector-js-azure.yml b/data/registry/resource-detector-js-azure.yml index cd4bb2abba91..1130f68bba2c 100644 --- a/data/registry/resource-detector-js-azure.yml +++ b/data/registry/resource-detector-js-azure.yml @@ -15,4 +15,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-azure' - version: 0.2.6 + version: 0.2.7 diff --git a/data/registry/resource-detector-js-container.yml b/data/registry/resource-detector-js-container.yml index 10c5b4575a22..ee977b0f5d10 100644 --- a/data/registry/resource-detector-js-container.yml +++ b/data/registry/resource-detector-js-container.yml @@ -17,4 +17,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-container' - version: 0.3.8 + version: 0.3.9 diff --git a/data/registry/resource-detector-js-gcp.yml b/data/registry/resource-detector-js-gcp.yml index 6421c1451767..1deb9b6e4cc1 100644 --- a/data/registry/resource-detector-js-gcp.yml +++ b/data/registry/resource-detector-js-gcp.yml @@ -15,4 +15,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-gcp' - version: 0.29.8 + version: 0.29.9 diff --git a/data/registry/resource-detector-js-github.yml b/data/registry/resource-detector-js-github.yml index a56b9fdb7cf8..a272355fc910 100644 --- a/data/registry/resource-detector-js-github.yml +++ b/data/registry/resource-detector-js-github.yml @@ -17,4 +17,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-github' - version: 0.28.1 + version: 0.28.2 diff --git a/data/registry/resource-detector-js-instana.yml b/data/registry/resource-detector-js-instana.yml index b64fef57a356..0d07cbecac3f 100644 --- a/data/registry/resource-detector-js-instana.yml +++ b/data/registry/resource-detector-js-instana.yml @@ -17,4 +17,4 @@ createdAt: 2022-12-07 package: registry: npm name: '@opentelemetry/resource-detector-instana' - version: 0.8.0 + version: 0.9.0 diff --git a/data/registry/tools-dotnet-purview-telemetry-sourcegenerator.yml b/data/registry/tools-dotnet-purview-telemetry-sourcegenerator.yml new file mode 100644 index 000000000000..79eda76870b1 --- /dev/null +++ b/data/registry/tools-dotnet-purview-telemetry-sourcegenerator.yml @@ -0,0 +1,41 @@ +# cSpell:ignore Kieron Lanning +title: Purview Telemetry Source Generator +registryType: utilities +language: dotnet +tags: + - c# + - .net + - dotnet + - source-generator + - activities + - logging + - logs + - events + - metrics + - spans + - attributes + - tags + - baggage + - telemetry + - high-performance-logging + - tracing + - distributed-tracing + - dependency-injection + - purview + - nuget +license: MIT +description: + Generates ActivitySource, Activity, ActivityEvent, High-performance logging + (ILogger) and Metrics based on methods on an interface, enabling fast + iteration cycles and substitutes for testing through dependency injection. +authors: + - name: Kieron Lanning + url: https://github.com/kieronlanning +urls: + repo: https://github.com/purview-dev/purview-telemetry-sourcegenerator/ + docs: https://github.com/purview-dev/purview-telemetry-sourcegenerator/blob/main/README.md +createdAt: 2024-04-26 +package: + registry: nuget + name: Purview.Telemetry.SourceGenerator + version: 1.0.5 diff --git a/data/registry/tools-js-sentry.yml b/data/registry/tools-js-sentry.yml deleted file mode 100644 index 7235eae8c4ab..000000000000 --- a/data/registry/tools-js-sentry.yml +++ /dev/null @@ -1,23 +0,0 @@ -title: Node Integration for Sentry -registryType: utilities -language: js -tags: - - javascript - - node - - processor - - propagator - - utilities - - sentry - - error monitoring -license: MIT -description: - The Sentry OpenTelemetry Node integration provides a processor and propagator - to send data to Sentry and to associate traces/spans to Sentry errors. For - configuration details, see [OpenTelemetry - Support](https://docs.sentry.io/platforms/node/performance/instrumentation/opentelemetry/). -authors: - - name: Sentry authors - email: otel@sentry.io -urls: - repo: https://github.com/getsentry/sentry-javascript/tree/master/packages/opentelemetry-node -createdAt: 2023-01-31 diff --git a/data/registry/tools-ruby-sentry.yml b/data/registry/tools-ruby-sentry.yml index fbc4813549d0..2e96b7f3e983 100644 --- a/data/registry/tools-ruby-sentry.yml +++ b/data/registry/tools-ruby-sentry.yml @@ -23,4 +23,4 @@ createdAt: 2023-01-31 package: registry: gems name: sentry-opentelemetry - version: 5.17.2 + version: 5.17.3 diff --git a/hugo.yaml b/hugo.yaml index cac33d3e05de..12298c0e07aa 100644 --- a/hugo.yaml +++ b/hugo.yaml @@ -1,7 +1,6 @@ -# cSpell:ignore docsy goldmark netlify wordmark +# cSpell:ignore docsy goldmark linkify netlify wordmark baseURL: https://opentelemetry.io -title: &title OpenTelemetry -description: &desc The OpenTelemetry Project Site +title: OpenTelemetry disableKinds: [taxonomy] theme: [docsy] disableAliases: true # We do redirects via Netlify's _redirects file @@ -9,18 +8,26 @@ enableGitInfo: true # Language settings enableMissingTranslationPlaceholders: true +defaultContentLanguage: en + languages: en: languageName: English params: - title: *title - description: *desc + description: The OpenTelemetry Project Site + zh: + languageName: 中文 (Chinese) + params: + description: OpenTelemetry 项目网站 + imaging: resampleFilter: CatmullRom # cspell:disable-line quality: 75 anchor: smart markup: + tableOfContents: + endLevel: 5 goldmark: extensions: linkify: false @@ -31,8 +38,7 @@ markup: renderer: unsafe: true highlight: - # noClasses: false - style: tango + noClasses: false # Netlify _redirects file mediaTypes: @@ -45,7 +51,7 @@ outputFormats: notAlternative: true outputs: - home: [HTML, REDIRECTS] + home: [HTML] section: [HTML] params: @@ -79,6 +85,7 @@ params: ui: navbar_logo: true navbar_translucent_over_cover_disable: true + showLightDarkModeMenu: true sidebar_menu_compact: true sidebar_menu_foldable: true sidebar_search_disable: true @@ -206,6 +213,9 @@ module: mounts: - source: content/en target: content + - source: content/zh + target: content + lang: zh - source: tmp/otel/specification target: content/docs/specs/otel - source: tmp/opamp diff --git a/layouts/partials/banner.md b/layouts/partials/banner.md index 638780a0ff2f..8c913c87c6f4 100644 --- a/layouts/partials/banner.md +++ b/layouts/partials/banner.md @@ -6,14 +6,12 @@ Join us for [**OTel Community Day** on June 25th](https://sessionize.com/OTel-Community-Day/)! -{{/* -Template for a second post. +Help improve OTel and Prometheus interoperability: [complete our survey](https://forms.gle/bZAG9f7udoJsjZUG9) by May 31 {.pt-0} -*/ -}} {{ end -}} diff --git a/layouts/shortcodes/docs/languages/exporters/intro.md b/layouts/shortcodes/docs/languages/exporters/intro.md index 3e4f33af7f6d..9d2867a6dd6a 100644 --- a/layouts/shortcodes/docs/languages/exporters/intro.md +++ b/layouts/shortcodes/docs/languages/exporters/intro.md @@ -1,6 +1,7 @@ -Send telemetry to the [OpenTelemetry Collector](/docs/collector/) to make sure -it's exported correctly. Using the Collector in production environments is a -best practice. To visualize your telemetry, export it to a backend such as +{{/* cSpell:ignore cond */ -}} Send telemetry to the +[OpenTelemetry Collector](/docs/collector/) to make sure it's exported +correctly. Using the Collector in production environments is a best practice. To +visualize your telemetry, export it to a backend such as [Jaeger](https://jaegertracing.io/), [Zipkin](https://zipkin.io/), [Prometheus](https://prometheus.io/), or a [vendor-specific](/ecosystem/vendors/) backend. @@ -34,7 +35,6 @@ Specification][OTLP]. [OTLP]: /docs/specs/otlp/ [Prometheus]: https://prometheus.io/docs/prometheus/latest/feature_flags/#otlp-receiver -[signals]: /docs/concepts/signals/ [vendors]: /ecosystem/vendors/ [reg]: /ecosystem/registry/?component=exporter&language={{ $lang }} @@ -47,12 +47,13 @@ them up. {{ end -}} {{ with $.Page.GetPage "automatic/configuration" }} +{{ $l := cond (eq $lang "dotnet") "net" $lang }} @@ -62,7 +63,7 @@ Guide](/docs/languages/{{ $lang }}/automatic/configuration/). below list needs to grow until all languages are updated to a consistent structure. */ -}} -{{ if in (slice "python" "js" "java" "cpp") $lang -}} +{{ if in (slice "python" "js" "java" "cpp" "dotnet") $lang -}} ## OTLP diff --git a/layouts/shortcodes/docs/languages/exporters/jaeger.md b/layouts/shortcodes/docs/languages/exporters/jaeger.md index 151ab54851b9..bf8f4e2aa781 100644 --- a/layouts/shortcodes/docs/languages/exporters/jaeger.md +++ b/layouts/shortcodes/docs/languages/exporters/jaeger.md @@ -1,5 +1,7 @@ ## Jaeger +### Backend Setup {#jaeger-backend-setup} + [Jaeger](https://www.jaegertracing.io/) natively supports OTLP to receive trace data. You can run Jaeger in a docker container with the UI accessible on port 16686 and OTLP enabled on ports 4317 and 4318: @@ -14,4 +16,6 @@ docker run --rm \ jaegertracing/all-in-one:latest ``` +### Usage {#jaeger-usage} + Now following the instruction to setup the [OTLP exporters](#otlp-dependencies). diff --git a/layouts/shortcodes/docs/languages/exporters/outro.md b/layouts/shortcodes/docs/languages/exporters/outro.md index b4a0da7ffb55..a6ccb6adc578 100644 --- a/layouts/shortcodes/docs/languages/exporters/outro.md +++ b/layouts/shortcodes/docs/languages/exporters/outro.md @@ -1,9 +1,6 @@ {{ $lang := .Get 0 -}} {{ $spanExporterInterfaceUrl := .Get 1 }} -## Other available exporters - -There are many other exporters available. For a list of available exporters, see -the [registry](/ecosystem/registry/?component=exporter&language={{ $lang }}). +## Custom exporters Finally, you can also write your own exporter. For more information, see the [SpanExporter Interface in the API diff --git a/layouts/shortcodes/ecosystem/vendor-table.md b/layouts/shortcodes/ecosystem/vendor-table.md index 7e35a99353dc..3abd51d19c16 100644 --- a/layouts/shortcodes/ecosystem/vendor-table.md +++ b/layouts/shortcodes/ecosystem/vendor-table.md @@ -3,7 +3,7 @@ cSpell:ignore: bution cial cond distri */ -}} {{ $data := sort (sort (sort $.Site.Data.ecosystem.vendors "name") "oss" "desc") "commercial" -}} -| Organization[^org] | OSS | Com­mer­cial | Distri­bution | Native OTLP | Learn more | +| Organization[^org] | OSS | Com­mer­cial | Native OTLP | Learn more | | ----------- | ----------- | ---------- | ----------------- | ----------- | ----------- | {{- range $data }} {{- $shortUrl := .shortUrl -}} diff --git a/package.json b/package.json index 0084bdeff143..36bb792f499a 100644 --- a/package.json +++ b/package.json @@ -28,7 +28,7 @@ "_prettier:any": "npx prettier --ignore-path ''", "_rename-to-kebab-case": "find assets content static -name '*_*' ! -name '_*' -exec sh -c 'mv \"$1\" \"${1//_/-}\"' _ {} \\;", "_serve:hugo": "hugo server -DFE --minify", - "_serve:netlify": "netlify dev -c \"npm run _serve:hugo\"", + "_serve:netlify": "netlify dev -c \"npm run _serve:hugo -- --renderToMemory\"", "_sync": "./scripts/sync-submodules.pl", "all": "bash -c 'x=0; for c in \"$@\"; do npm run $c || x=$((x+1)); done; ((!x)) || (echo \"ERROR: some scripts failed!\" && exit 1)' -", "build:preview": "set -x && npm run _build -- --minify", @@ -77,9 +77,9 @@ "prefix:submodules": "npm run update:submodule", "schemas:update": "npm run update:submodule content-modules/opentelemetry-specification", "seq": "bash -c 'for cmd in \"$@\"; do npm run $cmd || exit 1; done' - ", - "serve:hugo": "npm run _serve:hugo", + "serve:hugo": "npm run _serve:hugo -- --renderToMemory", "serve:netlify": "npm run _serve:netlify", - "serve": "npm run serve:hugo", + "serve": "npm run serve:hugo --", "sync": "./scripts/sync-submodules.pl", "test-and-fix": "npm run seq -- check fix:dict fix:filenames", "test": "npm run check", @@ -95,7 +95,7 @@ "autoprefixer": "^10.4.19", "cspell": "^8.0.0", "gulp": "^4.0.2", - "hugo-extended": "0.124.1", + "hugo-extended": "github:chalin/hugo-extended#v0.125.7", "markdown-link-check": "^3.12.1", "markdownlint": "^0.34.0", "postcss-cli": "^11.0.0", @@ -104,17 +104,17 @@ "textlint": "^14.0.1", "textlint-filter-rule-allowlist": "^4.0.0", "textlint-filter-rule-comments": "^1.2.2", - "textlint-rule-terminology": "^4.0.1", + "textlint-rule-terminology": "^5.0.0", "through2": "^4.0.2", "yargs": "^17.7.2" }, "dependencies": { "@opentelemetry/api": "^1.3.0", - "@opentelemetry/auto-instrumentations-web": "^0.37.0", + "@opentelemetry/auto-instrumentations-web": "^0.39.0", "@opentelemetry/context-zone": "^1.8.0", "@opentelemetry/core": "^1.8.0", - "@opentelemetry/exporter-trace-otlp-http": "^0.49.1", - "@opentelemetry/instrumentation": "^0.49.1", + "@opentelemetry/exporter-trace-otlp-http": "^0.51.0", + "@opentelemetry/instrumentation": "^0.51.0", "@opentelemetry/resources": "^1.8.0", "@opentelemetry/sdk-trace-base": "^1.8.0", "@opentelemetry/sdk-trace-web": "^1.8.0", diff --git a/scripts/check-registry-urls b/scripts/check-registry-urls index bc34f2c90be6..a8620d7ded60 100755 --- a/scripts/check-registry-urls +++ b/scripts/check-registry-urls @@ -6,7 +6,7 @@ REGISTRY_FILES=$REPO_DIR/data/registry/* for FILE in ${REGISTRY_FILES} ; do REPO_URL=$(grep "repo: " ${FILE}) - REPO_URL=${REPO_URL#repo: } + REPO_URL=${REPO_URL# repo: } if [ -n "${REPO_URL}" ] ; then RESULT=$(curl -I -s "{$REPO_URL}" -o /dev/null -w "%{http_code}") if [ "${RESULT}" != "200" ] ; then diff --git a/scripts/content-modules/adjust-pages.pl b/scripts/content-modules/adjust-pages.pl index f493006d6b82..195655180354 100755 --- a/scripts/content-modules/adjust-pages.pl +++ b/scripts/content-modules/adjust-pages.pl @@ -18,8 +18,8 @@ my $semConvRef = "$otelSpecRepoUrl/blob/main/semantic_conventions/README.md"; my $specBasePath = '/docs/specs'; my %versions = qw( - spec: 1.31.0 - otlp: 1.2.0 + spec: 1.33.0 + otlp: 1.3.1 semconv: 1.25.0 ); my $otelSpecVers = $versions{'spec:'}; @@ -51,12 +51,6 @@ () # TODO: add to front matter of OTel spec file and drop next line: $linkTitle = 'Design Goals' if $title eq 'Design Goals for OpenTelemetry Wire Protocol'; - # TODO: remove once all submodules have been updated in the context of https://github.com/open-telemetry/opentelemetry.io/issues/3922 - $frontMatterFromFile =~ s|: content/en/docs/specs/opamp/|: tmp/opamp/|g; - $frontMatterFromFile =~ s|: content/en/docs/specs/semconv/|: tmp/semconv/docs/|g; - $frontMatterFromFile =~ s|path_base_for_github_subdir:\n from: content/en/docs/specs/otlp/_index.md\n to: specification.md\n||; - $frontMatterFromFile =~ s|github_subdir: docs\n path_base_for_github_subdir: content/en/docs/specs/otlp/|path_base_for_github_subdir: tmp/otlp/|g; - # printf STDOUT "> $title -> $linkTitle\n"; print "linkTitle: $linkTitle\n" if $linkTitle and $frontMatterFromFile !~ /linkTitle: /; print "$frontMatterFromFile" if $frontMatterFromFile; @@ -157,8 +151,13 @@ () s|\]\(([^:\)]*?\.md(#.*?)?)\)|]({{% relref "$1" %}})|g; } - # Rewrite link defs - s|^(\[[^\]]+\]:\s*)([^:\s]*)(\s*(\(.*\))?)$|$1\{{% relref "$2" %}}$3|g; + # Rewrite link defs to local pages such as the following: + # + # [specification]: overview.md + # [faas]: some-path/faas-spans.md (FaaS trace conventions) + # + # The subregex `[:\s]+` excludes external URLs (because they contain a colon after the protocol) + s|^(\[[^\]]+\]:\s*)([^:\s]+)(\s*(\(.*\))?)$|$1\{{% relref "$2" %}}$3|g; # Make website-local page references local: s|https://opentelemetry.io/|/|g; diff --git a/static/refcache.json b/static/refcache.json index ca2eaf35b85a..1a88dba190fc 100644 --- a/static/refcache.json +++ b/static/refcache.json @@ -47,6 +47,14 @@ "StatusCode": 200, "LastSeen": "2024-02-23T23:30:53.006527-05:00" }, + "https://adri-v.medium.com/81d63addbf92": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:01.348993-04:00" + }, + "https://adri-v.medium.com/prometheus-opentelemetry-better-together-41dc637f2292": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:03.277893-04:00" + }, "https://agilecoffee.com/leancoffee/": { "StatusCode": 200, "LastSeen": "2024-01-18T08:05:43.542109-05:00" @@ -155,6 +163,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T15:19:46.407077+01:00" }, + "https://axiom.co/docs/send-data/opentelemetry": { + "StatusCode": 206, + "LastSeen": "2024-04-23T09:25:52.097148675Z" + }, "https://azure.github.io/azure-sdk/releases/latest/index.html": { "StatusCode": 206, "LastSeen": "2024-01-30T15:24:54.938182-05:00" @@ -179,6 +191,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T08:05:49.179762-05:00" }, + "https://bento.me/adrianamvillela": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:12.426363-04:00" + }, "https://betterstack.com/docs/logs/open-telemetry/#2-setup": { "StatusCode": 200, "LastSeen": "2024-01-30T16:14:47.668996-05:00" @@ -351,6 +367,22 @@ "StatusCode": 200, "LastSeen": "2024-01-30T06:07:21.044023-05:00" }, + "https://cloud-native.slack.com/archives/C033BJ8BASU/p1709128862949249": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:12.168228-04:00" + }, + "https://cloud-native.slack.com/archives/C033BJ8BASU/p1709321896612279": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:04.608233-04:00" + }, + "https://cloud-native.slack.com/archives/C033BJ8BASU/p1709935402250859": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:09.586175-04:00" + }, + "https://cloud-native.slack.com/archives/C033BJ8BASU/p1713894678225579": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:06.117078-04:00" + }, "https://cloud-native.slack.com/archives/C03B4CWV4DA": { "StatusCode": 200, "LastSeen": "2024-01-18T08:53:40.157677-05:00" @@ -811,6 +843,10 @@ "StatusCode": 206, "LastSeen": "2024-01-30T16:07:39.690877-05:00" }, + "https://docs.ansible.com/ansible/latest/collections/grafana/grafana/": { + "StatusCode": 206, + "LastSeen": "2024-03-19T11:21:52.991213698Z" + }, "https://docs.appdynamics.com/latest/en/application-monitoring/appdynamics-for-opentelemetry": { "StatusCode": 200, "LastSeen": "2024-01-18T08:51:22.195056-05:00" @@ -1163,6 +1199,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T05:18:24.354598-05:00" }, + "https://docs.google.com/forms/d/e/1FAIpQLSfpxKvN3_5VN6FQ5dF5-XLfNdOhVYtjreetkxlRCF8qS7AW2w/viewform": { + "StatusCode": 200, + "LastSeen": "2024-04-16T16:28:02.021217686Z" + }, "https://docs.google.com/spreadsheets/d/1SYKfjYhZdm2Wh2Cl6KVQalKg_m4NhTPZqq-8SzEVO6s": { "StatusCode": 200, "LastSeen": "2024-01-30T06:05:57.197702-05:00" @@ -1211,6 +1251,14 @@ "StatusCode": 206, "LastSeen": "2024-01-30T15:25:59.36407-05:00" }, + "https://docs.konghq.com/mesh/latest/guides/otel-metrics/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T15:56:23.493141+02:00" + }, + "https://docs.lightstep.com/docs/about-sending-data": { + "StatusCode": 206, + "LastSeen": "2024-05-13T07:15:59.231698318Z" + }, "https://docs.linuxfoundation.org/lfx/easycla/contributors": { "StatusCode": 206, "LastSeen": "2024-01-30T16:15:11.937332-05:00" @@ -1359,6 +1407,10 @@ "StatusCode": 206, "LastSeen": "2024-01-18T08:52:59.602661-05:00" }, + "https://docs.openlit.io/": { + "StatusCode": 206, + "LastSeen": "2024-05-02T10:13:10.86573134Z" + }, "https://docs.openshift.com/container-platform/4.14/otel/otel-release-notes.html": { "StatusCode": 206, "LastSeen": "2024-02-02T12:42:05.756504535Z" @@ -1631,6 +1683,10 @@ "StatusCode": 206, "LastSeen": "2024-02-19T17:27:38.673604461+01:00" }, + "https://docs.spring.io/spring-boot/docs/current/reference/html/features.html#features.external-config.typesafe-configuration-properties.relaxed-binding.environment-variables": { + "StatusCode": 200, + "LastSeen": "2024-04-11T13:40:26.805402963+02:00" + }, "https://docs.spring.io/spring-boot/docs/current/reference/html/using.html#using.auto-configuration": { "StatusCode": 206, "LastSeen": "2024-01-30T16:15:14.908906-05:00" @@ -1639,6 +1695,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:14:53.797365-05:00" }, + "https://docs.spring.io/spring-framework/docs/3.2.x/spring-framework-reference/html/expressions.html": { + "StatusCode": 206, + "LastSeen": "2024-04-03T12:51:54.758528517+02:00" + }, "https://docs.spring.io/spring-security/reference/servlet/authorization/architecture.html#authz-authorities": { "StatusCode": 206, "LastSeen": "2024-02-12T22:02:33.483262-05:00" @@ -1715,6 +1775,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:14:47.246698-05:00" }, + "https://embrace.io/opentelemetry-for-mobile/": { + "StatusCode": 206, + "LastSeen": "2024-04-25T10:29:55.539338+02:00" + }, "https://en.cppreference.com/w/cpp/container/set": { "StatusCode": 200, "LastSeen": "2024-01-18T19:02:25.398061-05:00" @@ -2007,6 +2071,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:05:22.448487-05:00" }, + "https://forms.gle/bZAG9f7udoJsjZUG9": { + "StatusCode": 200, + "LastSeen": "2024-05-01T16:48:59.737619-04:00" + }, "https://forms.gle/mEDWyn6G7iCe4bvJ7": { "StatusCode": 200, "LastSeen": "2024-01-18T19:02:03.877372-05:00" @@ -2059,6 +2127,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T06:01:12.059909-05:00" }, + "https://github.cm/open-telemetry/open-telemetry-collector": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:07.022619-04:00" + }, "https://github.com": { "StatusCode": 200, "LastSeen": "2024-01-18T19:55:56.862973-05:00" @@ -2075,6 +2147,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T05:18:56.239248-05:00" }, + "https://github.com/Azure/azure-sdk-for-net": { + "StatusCode": 200, + "LastSeen": "2024-04-23T14:33:23.6880679Z" + }, "https://github.com/Causely/documentation": { "StatusCode": 200, "LastSeen": "2024-03-15T20:34:22.210208944Z" @@ -2127,6 +2203,10 @@ "StatusCode": 200, "LastSeen": "2024-01-25T12:26:11.985357104Z" }, + "https://github.com/MassTransit/MassTransit": { + "StatusCode": 200, + "LastSeen": "2024-04-23T14:33:25.288254308Z" + }, "https://github.com/MetinSeylan/Nestjs-OpenTelemetry": { "StatusCode": 200, "LastSeen": "2024-01-18T19:12:29.56313-05:00" @@ -2287,6 +2367,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T20:05:40.87763-05:00" }, + "https://github.com/avillela/otel-errors-talk": { + "StatusCode": 200, + "LastSeen": "2024-03-27T00:26:43.376792984Z" + }, "https://github.com/aws-observability/aws-otel-collector": { "StatusCode": 200, "LastSeen": "2024-01-24T14:54:51.229664+01:00" @@ -2583,6 +2667,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:15:04.170576-05:00" }, + "https://github.com/iamebonyhope": { + "StatusCode": 200, + "LastSeen": "2024-05-08T10:07:06.998803+02:00" + }, "https://github.com/imandra-ai/ocaml-opentelemetry/": { "StatusCode": 200, "LastSeen": "2024-01-18T19:13:40.755331-05:00" @@ -2595,6 +2683,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:14:36.112572-05:00" }, + "https://github.com/ishanjainn": { + "StatusCode": 200, + "LastSeen": "2024-03-19T11:21:47.871135724Z" + }, "https://github.com/jack-berg": { "StatusCode": 200, "LastSeen": "2024-01-18T20:04:54.949867-05:00" @@ -2671,6 +2763,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T06:01:35.269251-05:00" }, + "https://github.com/kieronlanning": { + "StatusCode": 200, + "LastSeen": "2024-04-26T09:57:50.019728503+01:00" + }, "https://github.com/knative/eventing/issues/3126": { "StatusCode": 200, "LastSeen": "2024-01-18T20:05:35.589179-05:00" @@ -2755,6 +2851,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T05:18:18.419715-05:00" }, + "https://github.com/microsoft/ApplicationInsights-Java": { + "StatusCode": 200, + "LastSeen": "2024-04-19T17:43:49.897716918Z" + }, "https://github.com/mkocher": { "StatusCode": 200, "LastSeen": "2024-01-30T16:04:58.425652-05:00" @@ -2891,6 +2991,10 @@ "StatusCode": 200, "LastSeen": "2024-03-19T10:16:37.692028682Z" }, + "https://github.com/open-telemetry/community/issues/1971": { + "StatusCode": 200, + "LastSeen": "2024-05-03T07:21:04.501478-07:00" + }, "https://github.com/open-telemetry/community/issues/828": { "StatusCode": 200, "LastSeen": "2024-01-18T19:37:16.771654-05:00" @@ -2935,6 +3039,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:36:40.22377-05:00" }, + "https://github.com/open-telemetry/opentelemetry-collector-builder": { + "StatusCode": 200, + "LastSeen": "2024-05-08T10:07:07.582195+02:00" + }, "https://github.com/open-telemetry/opentelemetry-collector-contrib": { "StatusCode": 200, "LastSeen": "2024-01-18T20:05:30.222833-05:00" @@ -3059,6 +3167,14 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:36:56.082576-05:00" }, + "https://github.com/open-telemetry/opentelemetry-collector/issues/7532": { + "StatusCode": 200, + "LastSeen": "2024-04-04T11:07:15.276911438-07:00" + }, + "https://github.com/open-telemetry/opentelemetry-collector/issues/9375": { + "StatusCode": 200, + "LastSeen": "2024-05-03T08:34:29.3339-07:00" + }, "https://github.com/open-telemetry/opentelemetry-collector/pull/6140": { "StatusCode": 200, "LastSeen": "2024-01-30T05:18:24.402543-05:00" @@ -3071,6 +3187,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:37:01.457649-05:00" }, + "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/cmd%2Fbuilder%2Fv0.100.0": { + "StatusCode": 200, + "LastSeen": "2024-05-07T08:06:40.723390912Z" + }, "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/cmd%2Fbuilder%2Fv0.95.0": { "StatusCode": 200, "LastSeen": "2024-03-01T16:49:42.006164+01:00" @@ -3087,6 +3207,10 @@ "StatusCode": 200, "LastSeen": "2024-04-11T06:50:03.774028053Z" }, + "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/cmd%2Fbuilder%2Fv0.99.0": { + "StatusCode": 200, + "LastSeen": "2024-04-23T07:21:32.424805627Z" + }, "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.63.0": { "StatusCode": 200, "LastSeen": "2024-01-30T16:04:58.261649-05:00" @@ -3655,10 +3779,22 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:37:11.461365-05:00" }, + "https://github.com/open-telemetry/opentelemetry-operator/issues/1906": { + "StatusCode": 200, + "LastSeen": "2024-05-13T07:25:18.846726619Z" + }, "https://github.com/open-telemetry/opentelemetry-operator/issues/902": { "StatusCode": 200, "LastSeen": "2024-01-18T20:05:35.482435-05:00" }, + "https://github.com/open-telemetry/opentelemetry-operator/pull/2430#discussion_r1420495631": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:09.014347-04:00" + }, + "https://github.com/open-telemetry/opentelemetry-operator/pull/2787": { + "StatusCode": 200, + "LastSeen": "2024-05-13T07:25:20.170057644Z" + }, "https://github.com/open-telemetry/opentelemetry-operator/pull/832": { "StatusCode": 200, "LastSeen": "2024-01-18T20:05:30.899318-05:00" @@ -3763,6 +3899,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:37:26.943394-05:00" }, + "https://github.com/open-telemetry/opentelemetry-python-contrib/": { + "StatusCode": 200, + "LastSeen": "2024-04-26T12:45:03.066448+02:00" + }, "https://github.com/open-telemetry/opentelemetry-python/": { "StatusCode": 200, "LastSeen": "2024-01-10T11:27:53.222542-08:00" @@ -3875,6 +4015,14 @@ "StatusCode": 200, "LastSeen": "2024-01-30T05:19:02.768932-05:00" }, + "https://github.com/open-telemetry/opentelemetry-specification/issues/3966": { + "StatusCode": 200, + "LastSeen": "2024-04-11T14:54:53.493845265Z" + }, + "https://github.com/open-telemetry/opentelemetry-specification/issues/3967": { + "StatusCode": 200, + "LastSeen": "2024-04-11T14:54:50.847233614Z" + }, "https://github.com/open-telemetry/opentelemetry-specification/issues/437": { "StatusCode": 200, "LastSeen": "2024-01-18T19:36:56.207791-05:00" @@ -4095,6 +4243,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T05:18:13.065627-05:00" }, + "https://github.com/orgs/open-telemetry/projects/83": { + "StatusCode": 200, + "LastSeen": "2024-05-03T07:21:05.157831-07:00" + }, "https://github.com/orgs/open-telemetry/teams/technical-committee": { "StatusCode": 200, "LastSeen": "2024-01-30T16:15:03.796394-05:00" @@ -4167,6 +4319,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:37:11.409183-05:00" }, + "https://github.com/purview-dev/purview-telemetry-sourcegenerator/": { + "StatusCode": 200, + "LastSeen": "2024-04-26T09:57:49.687508317+01:00" + }, "https://github.com/raito-io/neo4j-tracing": { "StatusCode": 200, "LastSeen": "2024-01-30T05:18:18.651911-05:00" @@ -4481,15 +4637,23 @@ }, "https://grafana.com/docs/alloy/latest/": { "StatusCode": 200, - "LastSeen": "2024-04-10T00:09:47.949842+02:00" + "LastSeen": "2024-04-12T20:40:28.798266582Z" }, "https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/setup/instrument/dotnet/": { "StatusCode": 200, - "LastSeen": "2024-04-10T00:09:50.125651+02:00" + "LastSeen": "2024-04-12T20:40:30.368448693Z" }, "https://grafana.com/docs/grafana-cloud/monitor-applications/application-observability/setup/instrument/java/": { "StatusCode": 200, - "LastSeen": "2024-04-10T00:09:55.400731+02:00" + "LastSeen": "2024-04-12T20:40:34.652514906Z" + }, + "https://grafana.com/docs/grafana/latest/#installing-grafana": { + "StatusCode": 200, + "LastSeen": "2024-04-12T20:40:33.435682362Z" + }, + "https://grafana.com/grafana/dashboards/15983-opentelemetry-collector/": { + "StatusCode": 200, + "LastSeen": "2024-04-10T15:11:30.311778613-07:00" }, "https://grafana.com/oss/opentelemetry/": { "StatusCode": 200, @@ -4579,6 +4743,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:02:09.59825-05:00" }, + "https://hex.pm/packages": { + "StatusCode": 200, + "LastSeen": "2024-04-26T15:24:12.437103+02:00" + }, "https://hex.pm/packages/opentelemetry": { "StatusCode": 200, "LastSeen": "2024-01-18T19:02:25.352177-05:00" @@ -4587,6 +4755,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:02:20.083952-05:00" }, + "https://hex.pm/packages/opentelemetry_bandit": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:50.383352+02:00" + }, "https://hex.pm/packages/opentelemetry_ecto": { "StatusCode": 200, "LastSeen": "2024-01-08T12:17:14.14905+01:00" @@ -4607,6 +4779,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:55:51.119525-05:00" }, + "https://hexdocs.pm/bandit/Bandit.Telemetry.html#content": { + "StatusCode": 206, + "LastSeen": "2024-04-18T10:52:50.022207+02:00" + }, "https://hexdocs.pm/ecto/Ecto.html": { "StatusCode": 206, "LastSeen": "2024-01-18T19:55:56.733898-05:00" @@ -4791,10 +4967,18 @@ "StatusCode": 200, "LastSeen": "2024-01-18T08:07:19.690634-05:00" }, + "https://konghq.com/products/kong-mesh": { + "StatusCode": 200, + "LastSeen": "2024-04-30T15:56:22.220894+02:00" + }, "https://kubernetes.github.io/ingress-nginx/examples/grpc/": { "StatusCode": 206, "LastSeen": "2024-01-18T19:02:39.056387-05:00" }, + "https://kubernetes.io": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:03.727092-04:00" + }, "https://kubernetes.io/": { "StatusCode": 206, "LastSeen": "2024-01-18T08:52:44.68263-05:00" @@ -4807,6 +4991,14 @@ "StatusCode": 206, "LastSeen": "2024-01-18T08:53:40.07228-05:00" }, + "https://kubernetes.io/docs/concepts/configuration/secret/#using-a-secret": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:05.630302-04:00" + }, + "https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:01.910218-04:00" + }, "https://kubernetes.io/docs/concepts/extend-kubernetes/operator/": { "StatusCode": 206, "LastSeen": "2024-01-18T19:02:12.432637-05:00" @@ -4867,14 +5059,42 @@ "StatusCode": 206, "LastSeen": "2024-01-30T16:14:53.147946-05:00" }, + "https://kubernetes.io/docs/reference/access-authn-authz/rbac/#role-and-clusterrole": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:11.20031-04:00" + }, + "https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:11.609121-04:00" + }, "https://kubernetes.io/docs/reference/kubectl/": { "StatusCode": 206, "LastSeen": "2024-01-30T06:02:57.628168-05:00" }, + "https://kubernetes.io/docs/tasks/configure-pod-container/configure-service-account/": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:10.691008-04:00" + }, + "https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:07.571021-04:00" + }, "https://kubernetes.io/docs/tasks/debug/debug-cluster/resource-usage-monitoring/": { "StatusCode": 206, "LastSeen": "2024-01-30T06:01:40.735077-05:00" }, + "https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definitions/": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:10.120654-04:00" + }, + "https://kuma.io/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T15:56:19.177281+02:00" + }, + "https://kuma.io/docs/2.7.x/guides/otel-metrics/": { + "StatusCode": 206, + "LastSeen": "2024-04-30T15:56:19.48504+02:00" + }, "https://kyverno.io/": { "StatusCode": 206, "LastSeen": "2024-01-30T16:06:10.681585-05:00" @@ -4899,6 +5119,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T15:25:14.866011-05:00" }, + "https://learn.microsoft.com/azure/azure-monitor/app/opentelemetry-enable": { + "StatusCode": 200, + "LastSeen": "2024-04-19T15:58:48.039807479Z" + }, "https://learn.microsoft.com/azure/event-hubs/event-hubs-about": { "StatusCode": 200, "LastSeen": "2024-04-04T20:00:42.394166-04:00" @@ -4927,6 +5151,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:14:18.196332-05:00" }, + "https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable": { + "StatusCode": 200, + "LastSeen": "2024-04-23T14:33:24.635286085Z" + }, "https://learn.microsoft.com/en-us/dotnet/api/system.reflection.assembly.getentryassembly": { "StatusCode": 200, "LastSeen": "2024-01-30T15:24:54.805878-05:00" @@ -5039,6 +5267,14 @@ "StatusCode": 206, "LastSeen": "2024-01-18T19:02:52.895666-05:00" }, + "https://masstransit.io/documentation/configuration/observability": { + "StatusCode": 200, + "LastSeen": "2024-04-23T14:33:28.363350589Z" + }, + "https://maven.apache.org/": { + "StatusCode": 206, + "LastSeen": "2024-02-15T17:43:36.624023547Z" + }, "https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms": { "StatusCode": 206, "LastSeen": "2024-01-30T16:15:00.07395-05:00" @@ -5155,6 +5391,10 @@ "StatusCode": 206, "LastSeen": "2024-01-18T19:10:28.513448-05:00" }, + "https://newrelic.com/blog/how-to-relic/dude-wheres-my-error": { + "StatusCode": 206, + "LastSeen": "2024-03-27T00:26:34.094985195Z" + }, "https://newrelic.com/solutions/opentelemetry": { "StatusCode": 206, "LastSeen": "2024-01-18T19:08:01.196826-05:00" @@ -5187,6 +5427,14 @@ "StatusCode": 200, "LastSeen": "2024-01-30T06:01:27.910674-05:00" }, + "https://nodejs.org/api/perf_hooks.html": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:50.937617+02:00" + }, + "https://nodejs.org/docs/latest/api/globals.html#fetch": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:53.71005+02:00" + }, "https://nodejs.org/en/": { "StatusCode": 206, "LastSeen": "2024-01-18T19:10:39.6518-05:00" @@ -5391,6 +5639,10 @@ "StatusCode": 200, "LastSeen": "2024-01-15T11:08:26.460933+01:00" }, + "https://npmjs.com/package/@opentelemetry/instrumentation-runtime-node": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:53.07175+02:00" + }, "https://npmjs.com/package/@opentelemetry/instrumentation-socket.io": { "StatusCode": 200, "LastSeen": "2024-01-15T11:08:28.151807+01:00" @@ -5399,6 +5651,10 @@ "StatusCode": 200, "LastSeen": "2024-01-15T11:08:29.855822+01:00" }, + "https://npmjs.com/package/@opentelemetry/instrumentation-undici": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:59:58.377585+02:00" + }, "https://npmjs.com/package/@opentelemetry/instrumentation-user-interaction": { "StatusCode": 200, "LastSeen": "2024-01-15T11:08:31.830172+01:00" @@ -5595,6 +5851,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:15:09.905013-05:00" }, + "https://opentelemetry-python.readthedocs.io/en/latest/_modules/opentelemetry/sdk/trace.html#Span.record_exception": { + "StatusCode": 200, + "LastSeen": "2024-03-27T00:26:39.534637612Z" + }, "https://opentelemetry-python.readthedocs.io/en/latest/api/metrics.html": { "StatusCode": 200, "LastSeen": "2024-01-18T19:07:50.251993-05:00" @@ -5651,6 +5911,14 @@ "StatusCode": 206, "LastSeen": "2024-03-19T10:16:59.755536357Z" }, + "https://opentelemetry.io/blog/2024/otel-collector-anti-patterns/": { + "StatusCode": 206, + "LastSeen": "2024-05-06T07:53:28.679391-07:00" + }, + "https://opentelemetry.io/blog/2024/scaling-collectors/": { + "StatusCode": 206, + "LastSeen": "2024-05-06T07:53:28.903161-07:00" + }, "https://opentelemetry.io/docs/collector": { "StatusCode": 206, "LastSeen": "2024-02-23T22:55:03.656226-05:00" @@ -5799,6 +6067,10 @@ "StatusCode": 200, "LastSeen": "2024-01-19T13:15:36.979713+01:00" }, + "https://packagist.org/packages/open-telemetry/opentelemetry-auto-psr16": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:54.145856+02:00" + }, "https://packagist.org/packages/open-telemetry/opentelemetry-auto-psr18": { "StatusCode": 200, "LastSeen": "2024-01-19T13:15:37.164154+01:00" @@ -6059,6 +6331,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:15:48.644086+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/exporter/rabbitmqexporter": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:41.513572+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter": { "StatusCode": 200, "LastSeen": "2024-01-08T12:15:48.96771+01:00" @@ -6099,6 +6375,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:15:53.29617+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/ackextension": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:42.492159+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/asapauthextension": { "StatusCode": 200, "LastSeen": "2024-01-08T12:15:53.592567+01:00" @@ -6115,6 +6395,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:15:54.593894+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/googleclientauthextension": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:59:50.120996+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/headerssetterextension": { "StatusCode": 200, "LastSeen": "2024-01-08T12:15:55.080979+01:00" @@ -6127,6 +6411,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:15:55.902358+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarderextension": { + "StatusCode": 200, + "LastSeen": "2024-04-20T15:42:40.997100599Z" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/jaegerremotesampling": { "StatusCode": 200, "LastSeen": "2024-01-08T12:15:56.204017+01:00" @@ -6159,6 +6447,10 @@ "StatusCode": 200, "LastSeen": "2024-02-05T17:24:24.214319+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/extension/sumologicextension": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:43.668863+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/processor/attributesprocessor": { "StatusCode": 200, "LastSeen": "2024-01-08T12:15:59.158+01:00" @@ -6307,6 +6599,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:16:13.469744+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awss3receiver": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:46.332437+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awsxrayreceiver": { "StatusCode": 200, "LastSeen": "2024-01-08T12:16:11.377253+01:00" @@ -6499,6 +6795,10 @@ "StatusCode": 200, "LastSeen": "2024-01-19T13:15:33.894429+01:00" }, + "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otelarrowreceiver": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:48.70354+02:00" + }, "https://pkg.go.dev/github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otlpjsonfilereceiver": { "StatusCode": 200, "LastSeen": "2024-01-08T12:16:35.726108+01:00" @@ -6671,14 +6971,26 @@ "StatusCode": 200, "LastSeen": "2024-03-01T16:49:31.744795+01:00" }, + "https://pkg.go.dev/go.opentelemetry.io/collector/exporter/nopexporter": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:41.016085+02:00" + }, "https://pkg.go.dev/go.opentelemetry.io/collector/exporter/otlpexporter": { "StatusCode": 200, "LastSeen": "2024-03-01T16:49:32.206669+01:00" }, + "https://pkg.go.dev/go.opentelemetry.io/collector/extension/memorylimiterextension": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:59:50.520596+02:00" + }, "https://pkg.go.dev/go.opentelemetry.io/collector/processor/batchprocessor": { "StatusCode": 200, "LastSeen": "2024-03-01T16:49:33.428723+01:00" }, + "https://pkg.go.dev/go.opentelemetry.io/collector/receiver/nopreceiver": { + "StatusCode": 200, + "LastSeen": "2024-04-18T10:52:48.17193+02:00" + }, "https://pkg.go.dev/go.opentelemetry.io/collector/receiver/otlpreceiver": { "StatusCode": 200, "LastSeen": "2024-03-01T16:49:37.76693+01:00" @@ -6699,6 +7011,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:10:29.862565-05:00" }, + "https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp": { + "StatusCode": 200, + "LastSeen": "2024-04-25T07:21:16.712986-07:00" + }, "https://pkg.go.dev/go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc": { "StatusCode": 200, "LastSeen": "2024-01-30T15:25:43.27652-05:00" @@ -6719,6 +7035,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:07:44.890589-05:00" }, + "https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutlog": { + "StatusCode": 200, + "LastSeen": "2024-04-24T13:46:14.851022-07:00" + }, "https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutmetric": { "StatusCode": 200, "LastSeen": "2024-01-30T15:25:21.196671-05:00" @@ -6851,6 +7171,22 @@ "StatusCode": 206, "LastSeen": "2024-01-18T19:55:30.198683-05:00" }, + "https://prometheus.io/docs/instrumenting/clientlibs/": { + "StatusCode": 206, + "LastSeen": "2024-04-11T14:54:50.705990785Z" + }, + "https://prometheus.io/docs/instrumenting/exposition_formats/#basic-info": { + "StatusCode": 206, + "LastSeen": "2024-04-11T14:54:57.142101041Z" + }, + "https://prometheus.io/docs/instrumenting/exposition_formats/#comments-help-text-and-type-information": { + "StatusCode": 206, + "LastSeen": "2024-04-11T14:54:55.03691741Z" + }, + "https://prometheus.io/docs/instrumenting/writing_clientlibs/#overall-structure": { + "StatusCode": 206, + "LastSeen": "2024-04-11T14:54:52.880727432Z" + }, "https://prometheus.io/docs/practices/naming/#metric-names": { "StatusCode": 206, "LastSeen": "2024-01-18T19:06:10.627254-05:00" @@ -6915,6 +7251,10 @@ "StatusCode": 206, "LastSeen": "2024-01-30T16:14:48.105173-05:00" }, + "https://pypi.org/project/opentelemetry-instrumentation-httpx/": { + "StatusCode": 206, + "LastSeen": "2024-04-28T16:14:45.577134727Z" + }, "https://qryn.metrico.in/#/support": { "StatusCode": 206, "LastSeen": "2024-01-30T16:03:54.589618-05:00" @@ -7483,6 +7823,10 @@ "StatusCode": 206, "LastSeen": "2024-02-26T10:53:38.643051+01:00" }, + "https://stackoverflow.com/a/56653384": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:04.058944-04:00" + }, "https://stackoverflow.com/questions/5626193/what-is-monkey-patching": { "StatusCode": 200, "LastSeen": "2024-01-18T19:07:28.672979-05:00" @@ -7659,6 +8003,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:07:34.497619-05:00" }, + "https://undici.nodejs.org/": { + "StatusCode": 206, + "LastSeen": "2024-04-18T10:52:53.442567+02:00" + }, "https://uplight.com": { "StatusCode": 206, "LastSeen": "2024-01-30T05:18:18.611588-05:00" @@ -7667,7 +8015,7 @@ "StatusCode": 206, "LastSeen": "2024-01-30T06:06:33.174666-05:00" }, - "https://uptrace.dev": { + "https://uptrace.dev/get/open-source-apm.html": { "StatusCode": 206, "LastSeen": "2024-01-18T19:08:12.676498-05:00" }, @@ -7787,6 +8135,10 @@ "StatusCode": 200, "LastSeen": "2024-01-19T09:04:05.862693+01:00" }, + "https://www.ansible.com/": { + "StatusCode": 200, + "LastSeen": "2024-03-19T11:21:48.883430689Z" + }, "https://www.apollographql.com/docs/federation/": { "StatusCode": 206, "LastSeen": "2024-01-18T19:55:56.349642-05:00" @@ -7811,6 +8163,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:56:02.154722-05:00" }, + "https://www.base64encode.org/": { + "StatusCode": 200, + "LastSeen": "2024-04-25T00:01:05.091534-04:00" + }, "https://www.bmc.com/blogs/opentracing-opencensus-openmetrics/": { "StatusCode": 200, "LastSeen": "2024-01-18T19:10:51.674944-05:00" @@ -7991,6 +8347,10 @@ "StatusCode": 206, "LastSeen": "2024-01-30T06:01:04.885071-05:00" }, + "https://www.honeycomb.io/blog/what-is-auto-instrumentation": { + "StatusCode": 206, + "LastSeen": "2024-04-25T00:01:02.263794-04:00" + }, "https://www.hyperdx.io/docs/install/opentelemetry": { "StatusCode": 206, "LastSeen": "2024-01-30T16:14:16.496047-05:00" @@ -8147,6 +8507,14 @@ "StatusCode": 200, "LastSeen": "2024-01-30T15:37:02.403477-05:00" }, + "https://www.krakend.io": { + "StatusCode": 206, + "LastSeen": "2024-04-19T07:13:40.975524094Z" + }, + "https://www.krakend.io/docs/telemetry/opentelemetry/": { + "StatusCode": 206, + "LastSeen": "2024-04-19T07:13:43.941227206Z" + }, "https://www.linuxfoundation.org/legal/privacy-policy": { "StatusCode": 200, "LastSeen": "2024-01-30T16:04:05.250977-05:00" @@ -8327,6 +8695,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:04:59.787702-05:00" }, + "https://www.nuget.org/packages/OpenTelemetry.Exporter.Console/": { + "StatusCode": 200, + "LastSeen": "2024-02-26T11:49:03.510469+01:00" + }, "https://www.nuget.org/packages/OpenTelemetry.Exporter.Geneva": { "StatusCode": 200, "LastSeen": "2024-01-08T12:16:52.640928+01:00" @@ -8351,6 +8723,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:16:55.911758+01:00" }, + "https://www.nuget.org/packages/OpenTelemetry.Exporter.OpenTelemetryProtocol/": { + "StatusCode": 200, + "LastSeen": "2024-02-26T11:21:32.246063+01:00" + }, "https://www.nuget.org/packages/OpenTelemetry.Exporter.Prometheus.AspNetCore": { "StatusCode": 200, "LastSeen": "2024-01-08T12:16:56.504932+01:00" @@ -8367,6 +8743,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:16:58.383719+01:00" }, + "https://www.nuget.org/packages/OpenTelemetry.Extensions.Hosting": { + "StatusCode": 200, + "LastSeen": "2024-02-26T11:49:01.977306+01:00" + }, "https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWS": { "StatusCode": 200, "LastSeen": "2024-01-08T12:17:03.97417+01:00" @@ -8455,6 +8835,10 @@ "StatusCode": 200, "LastSeen": "2024-01-08T12:17:13.880643+01:00" }, + "https://www.nuget.org/packages/Purview.Telemetry.SourceGenerator": { + "StatusCode": 200, + "LastSeen": "2024-04-26T09:57:50.691575342+01:00" + }, "https://www.nuget.org/packages/Quartz": { "StatusCode": 200, "LastSeen": "2024-01-30T15:26:32.105686-05:00" @@ -8811,6 +9195,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T16:34:02.591185-05:00" }, + "https://www.youtube.com/@otel-official": { + "StatusCode": 200, + "LastSeen": "2024-04-15T11:38:45.271323+02:00" + }, "https://www.youtube.com/embed/coPrhP_7lVU": { "StatusCode": 200, "LastSeen": "2024-01-30T16:15:42.688406-05:00" @@ -8827,6 +9215,10 @@ "StatusCode": 206, "LastSeen": "2024-01-11T06:07:16.115841487Z" }, + "https://yaml.org/spec/1.2.2/#103-core-schema": { + "StatusCode": 206, + "LastSeen": "2024-05-09T18:03:35.877818575Z" + }, "https://youtu.be/9iaGG-YZw5I": { "StatusCode": 200, "LastSeen": "2024-01-18T08:06:46.2047-05:00" diff --git a/themes/docsy b/themes/docsy index b077a74d38c8..6f7e81d34ca7 160000 --- a/themes/docsy +++ b/themes/docsy @@ -1 +1 @@ -Subproject commit b077a74d38c833586361e7d735672166818a64cf +Subproject commit 6f7e81d34ca7c75558c5bc969969c96202a059ea