Merge branch 'main' into michael2893-update-collector-docs-gateway

Author: michael2893

.htmltest.yml

@@ -8,6 +8,8 @@ CheckMailto: false
 TestFilesConcurrently: true
 IgnoreDirs:
   - ^blog/(\d+/)?page/\d+
+  # TODO drop after https://github.com/open-telemetry/opentelemetry.io/issues/5267 is fixed:
+  - zh/docs/contributing/pr-checks
 IgnoreInternalURLs: # list of paths
 IgnoreURLs: # list of regexs of paths or URLs to be ignored
   - ^((/..)?/docs/languages/\w+|\.\.)/(api|examples|registry)/$

content/en/blog/2023/otel-arrow/index.md

@@ -24,8 +24,8 @@ repository that supports this protocol. This protocol, designed to complement
 the OTLP protocol in situations with substantial telemetry data volumes, has
 been under discussion and development for two years. It represents a
 collaborative effort between [F5](https://f5.com),
-[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html)
-, and numerous technical leaders from the OpenTelemetry community (see
+[ServiceNow Cloud Observability](https://www.servicenow.com/products/observability.html),
+and numerous technical leaders from the OpenTelemetry community (see
 [donation](https://github.com/open-telemetry/community/issues/1332)). The
 compression benefits are significant, demonstrating a **40% improvement
 compression efficiency** for the majority of workloads and even greater

content/en/blog/2024/otel-arrow-production/index.md

@@ -2,10 +2,9 @@
 title: OpenTelemetry Protocol with Apache Arrow in Production
 linkTitle: OpenTelemetry Arrow in Production
 date: 2024-09-25
-author:
-  >- # If you have only one author, then add the single name on this line in quotes.
-  [Joshua MacDonald](https://github.com/jmacd) (ServiceNow, Inc), [Laurent
-  Querel](https://github.com/lquerel) (F5, Inc)
+author: >-
+  [Joshua MacDonald](https://github.com/jmacd) (ServiceNow), [Laurent
+  Querel](https://github.com/lquerel) (F5)
 cSpell:ignore: Querel Zstd
 issue: 5193
 sig: OpenTelemetry Arrow
@@ -54,8 +53,8 @@ OpenTelemetry Collectors.
 The compression bridge consists of two OpenTelemetry Collectors labeled exporter
 and receiver, or they could equally be two pools of load-balanced collectors.
 
-As described in this
-["OTEP" design document](https://github.com/open-telemetry/oteps/blob/main/text/0156-columnar-encoding.md#mapping-otel-entities-to-arrow-records),
+As described in the
+[OTEP 0156 design document](https://github.com/open-telemetry/oteps/blob/main/text/0156-columnar-encoding.md#mapping-otel-entities-to-arrow-records),
 the exporter converts arbitrary OpenTelemetry data into an Arrow record batch.
 The Arrow record batch is a block of memory, with a standardized layout, making
 it possible to exchange data across address spaces and virtual process
@@ -224,7 +223,7 @@ giving them an opportunity to retry on another connection, and it gives the
 service operator a chance to auto-scale the number of instances to handle the
 increase in load based on memory utilization.
 
-See the
+For details, see the
 [documentation on batching and back-pressure](https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/exporter/otelarrowexporter/README.md#batching-configuration)
 for the OTel-Arrow exporter.
 
@@ -246,7 +245,7 @@ the OpenTelemetry standard OTLP over gRPC, with round-robin load balancing. The
 gateway collectors apply a variety of processors, including the concurrent batch
 processor described above, followed by the OTel-Arrow exporter.
 
-![A pool of gateway collectors sends to a load balancer, then to a backend service.](./setup.png)
+![A pool of gateway collectors sends to a load balancer, then to a backend service.](setup.png)
 
 On the other side of the bridge, a pool of Envoy load balancers distributes the
 streams across a pool of collectors running the OTel-Arrow receiver, after

content/en/docs/collector/custom-collector.md

@@ -120,8 +120,6 @@ the development and testing of components.
 Go ahead and create a manifest file named `builder-config.yaml` with the
 following content:
 
-> builder-config.yaml
-
 ```yaml
 dist:
   name: otelcol-dev
@@ -144,8 +142,6 @@ collector distribution:
 The `builder-config.yaml` manifest file will look like this after adding the
 components:
 
-> builder-config.yaml
-
 <!-- prettier-ignore -->
 ```yaml
 dist:
@@ -170,6 +166,15 @@ receivers:
       go.opentelemetry.io/collector/receiver/otlpreceiver {{% version-from-registry collector-receiver-otlp %}}
 ```
 
+{{% alert color="primary" title="Tip" %}}
+
+For a list of components that you can add to your custom collector, see the
+[OpenTelemetry Registry](/ecosystem/registry/?language=collector). Note that
+registry entries provide the full name and version you need to add to your
+`builder-config.yaml`.
+
+{{% /alert %}}
+
 ## Step 3 - Generating the Code and Building your Collector's distribution
 
 All you need now is to let the `ocb` do it's job, so go to your terminal and

content/en/docs/contributing/_index.md

@@ -1,29 +1,52 @@
 ---
 title: Contributing
-description: Learn how to contribute to OpenTelemetry documentation.
 aliases: [/docs/contribution-guidelines]
 weight: 980
 ---
 
+Thanks for your interest in contributing to the OpenTelemetry docs and website.
+
+## Jump right in!
+
+What do you want to do?
+
+- Correct a **typo or other quick fixes**, see
+  [Submitting content using GitHub](pull-requests/#changes-using-github)
+- For more significant contributions, read the pages in this section starting
+  with:
+  - [Prerequisites]
+  - [Issues]
+  - [Submitting content]
+
+[Prerequisites]: prerequisites/
+[Issues]: issues/
+[Submitting content]: pull-requests/
+
+{{% alert title="<i class='far fa-exclamation-triangle'></i> First time contributing? " %}}
+
+Eager first-time contributors, see
+[Fixing an existing issue](issues/#fixing-an-existing-issue) for important
+guidance.
+
+{{% /alert %}}
+
+## What can I contribute to?
+
 OpenTelemetry documentation contributors:
 
-- Improve existing content.
-- Create new content.
-- Update the OpenTelemetry Registry.
-- Improve the code that builds the site.
+- Improve existing or create new content
+- [Submit a blog post](blog/) or case study
+- Add to or update the [OpenTelemetry Registry](/ecosystem/registry/)
+- Improve the code that builds the site
 
-The following guides describe how to contribute to OpenTelemetry documentation.
+The pages in this section describe 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/guides/contributor/README.md)
-, which provides details on the Contributor License Agreement and the Code of
-Conduct. Every language implementation, Collector, and conventions
-[repository](https://github.com/open-telemetry/) has its own specific
+the community [OpenTelemetry New Contributor Guide]. Every [OTel repository][org]
+for language implementations, the Collector, and conventions have their own project-specific
 contributing guides.
 
-## Other ways to contribute
-
-- Visit the [OpenTelemetry community site](/community/).
-- Add your application to the [Registry](/ecosystem).
-- Submit a [blog post or case study](/docs/contributing/blog/).
+[OpenTelemetry New Contributor Guide]:
+  https://github.com/open-telemetry/community/blob/main/guides/contributor
+[org]: https://github.com/open-telemetry

content/en/docs/contributing/development.md

@@ -1,5 +1,6 @@
 ---
-title: Development
+title: Development setup and commands to build, serve, and more
+linkTitle: Dev setup and more
 description:
   Learn how to set up a development environment for the opentelemetry.io site.
 weight: 60

content/en/docs/contributing/issues.md

@@ -1,10 +1,54 @@
 ---
-title: Reporting an issue
-description: How to report a bug, a security issue, or a potential improvement.
-weight: 50
+title: Issues
+description:
+  How to fix an existing issue, or report a bug, security risk, or potential
+  improvement.
+weight: 10
 cSpell:ignore: prepopulated
+_issues: https://github.com/open-telemetry/opentelemetry.io/issues
+_issue: https://github.com/open-telemetry/opentelemetry.io/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc+label%3A
 ---
 
+## Fixing an existing issue
+
+One of the best ways to help make OTel docs better is to fix an existing issue.
+
+1. Browse through the list of [issues]({{% param _issues %}}).
+2. Select an issue that you would like to work on, ideally one that you can fix
+   in a short amount of time.
+
+   <!-- prettier-ignore -->
+   <a name="first-issue"></a>
+   {{% alert title="First time contributing? " %}}
+
+   Select an issue with the following labels:
+
+   - [Good first issue]
+   - [Help wanted]
+
+   <!-- prettier-ignore -->
+   > **NOTE**: we **_do not_ assign issues** to those who
+   > have not already made contributions to the [OpenTelemetry
+   > organization][org].
+   {.mt-3}
+
+   <!-- prettier-ignore -->
+   [good first issue]: {{% param _issue %}}%22good+first+issue%22
+   [help wanted]: {{% param _issue %}}%3A%22help+wanted%22
+   [org]: https://github.com/open-telemetry
+
+   {{% /alert %}}
+
+3. Read through the issue comments, if any.
+4. Ask maintainers if this issue is still relevant, and ask any questions you
+   need for clarification by posting comments over the issue.
+5. Share your intention to work on the issue by adding add a comment to this
+   effect.
+6. Work on fixing the issue. Let maintainers know if you run into any problems.
+7. When ready, [submit your work through a pull request](../pull-requests) (PR).
+
+## Reporting an issue
+
 If you notice an error or want to suggest improvements to existing content, open
 an issue.
 

content/en/docs/contributing/pr-checks.md

@@ -18,8 +18,8 @@ a set of checks are executed. The PR checks verify that...
 
 {{% alert title="Note" color="primary" %}}
 
-If any of the PR checks fails, please try to
-[fix content issues automatically](/docs/contributing/new-content/#fix-content-issues-automatically)
+If any of the PR checks fails, try to
+[fix content issues automatically](../pull-requests/#fix-content-issues-automatically)
 first by running `npm run fix:all` on your machine.
 
 Additionally, you can comment `/fix:all` on your Pull Request. This will make
@@ -33,8 +33,7 @@ can recover from a failed state.
 
 ## Easy CLA
 
-This check fails if you haven't
-[signed the CLA](/docs/contributing/requirements/#sign-the-cla).
+This check fails if you haven't [signed the CLA](../prerequisites/#cla).
 
 ## Netlify deployment
 
@@ -43,17 +42,17 @@ more information.
 
 ## Style checks
 
-To make sure that contributions follow our
-[style guide](/docs/contributing/style-guide) we have implemented a set of
-checks that verify style guide rules and fail l if they find any issues.
+To make sure that contributions follow our [style guide](../style-guide/) we
+have implemented a set of checks that verify style guide rules and fail l if
+they find any issues.
 
 The following list describes current checks and what you can do to fix related
 errors:
 
 ### TEXT linter
 
 This check verifies that
-[OpenTelemetry-specific terms and words are used consistently across the site](/docs/contributing/style-guide#opentelemetryio-word-list).
+[OpenTelemetry-specific terms and words are used consistently across the site](../style-guide/#opentelemetryio-word-list).
 
 If any issues are found, annotations are added to your files in the
 `files changed` view of your PR. Fix those to turn the check green. As an
@@ -63,15 +62,15 @@ issues. Run `npm run check:text` again and manually fix the remaining issues.
 ### MARKDOWN linter
 
 This check verifies that
-[standards and consistency for Markdown files are enforced](/docs/contributing/style-guide#markdown-standards).
+[standards and consistency for Markdown files are enforced](../style-guide/#markdown-standards).
 
 If any issues are found, run `npm:run format` to fix most issues. For more
 complex issues, run `npm run check:markdown` and apply the suggested changes.
 
 ### SPELLING check
 
 This check verifies that
-[all words are spelled correctly](/docs/contributing/style-guide#spell-checking).
+[all words are spelled correctly](../style-guide/#spell-checking).
 
 ### CSPELL:IGNORE check
 
@@ -83,15 +82,15 @@ new commit.
 ### FILENAME check
 
 This check verifies that all
-[files are formatted by prettier](/docs/contributing/style-guide#file-format).
+[files are formatted by prettier](../style-guide/#file-format).
 
 If this check fails, run `npm fix:format` locally and push the changes in a new
 commit.
 
 ### FILE FORMAT
 
 This check verifies that all
-[file names are in kebab-case](/docs/contributing/style-guide#file-names).
+[file names are in kebab-case](../style-guide/#file-names).
 
 If this check fails, run `npm fix:filenames` locally and push the changes in a
 new commit.

content/en/docs/contributing/prerequisites.md

@@ -0,0 +1,43 @@
+---
+title: Prerequisites
+description:
+  To contribute, you need to be familiar with the following techs and tools.
+aliases: [requirements]
+weight: 1
+---
+
+To contribute to this repository, you need to be familiar with the following
+techs and tools:
+
+- [git](https://git-scm.com/)
+- [GitHub](https://github.com/)
+- Markdown ([CommonMark](https://commonmark.org/))
+- YAML
+
+For technical details concerning how the documentation is built and tested
+locally, see [Development](../development).
+
+## Sign the CNCF CLA {#cla}
+
+All OpenTelemetry contributors must sign the Linux Foundation [Contributor
+License Agreement (CLA)][CLA].
+
+Pull requests from contributors who haven't signed the CLA fail the automated
+tests. The name and email you provide must match those found in your
+`git config`, and your git name and email must match those used for the CNCF
+CLA.
+
+## Code of conduct
+
+All OpenTelemetry contributors are bound by the [CNCF Community Code of
+Conduct][CoC].
+
+## Community guidelines
+
+For general OpenTelemetry community guidelines, including roles and
+expectations, see [OpenTelemetry New Contributor Guide][NCG]
+
+[CLA]: https://docs.linuxfoundation.org/lfx/easycla/contributors
+[CoC]: https://github.com/cncf/foundation/blob/main/code-of-conduct.md
+[NCG]:
+  https://github.com/open-telemetry/community/blob/main/guides/contributor/README.md

content/en/docs/contributing/new-content.md content/en/docs/contributing/pull-requests.md

@@ -1,22 +1,26 @@
 ---
-title: Add new content
-description: Learn how to add new content using GitHub UI or a local fork.
-weight: 2
+title: Submitting content
+description:
+  Learn how to submit new or changed content using the GitHub UI or a local
+  fork.
+aliases: [new-content]
+weight: 15
 ---
 
-To contribute new content pages or improve existing content pages, open a pull
-request (PR):
+To contribute new or improve existing documentation content, submit a [pull
+request][PR] (PR):
 
-- If your change is small, or you're unfamiliar with Git, read
+- If your change is small, or you're unfamiliar with Git, see
   [Changes using GitHub](#changes-using-github) to learn how to edit a page.
-- If your changes are large, read [Work from a local fork](#fork-the-repo) to
+- If your changes are large, see [Work from a local fork](#fork-the-repo) to
   learn how to make changes locally on your computer.
 
-{{% alert title="Tip" %}}
+{{% alert title="Tip: Draft status" %}}
 
-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.
+Set the status of your pull request to **Draft** to let maintainers know that
+the content isn't ready for review yet. 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 %}}
 
@@ -46,7 +50,17 @@ _Figure 1. Contributing new content._
 ## Changes using GitHub {#changes-using-github}
 
 If you're less experienced with Git workflows, here's an easier method of
-opening a pull request. Figure 2 outlines the steps and the details follow.
+creating and submitting a pull request. Figure 2 outlines the steps and the
+details follow.
+
+{{% alert title="Contributor License Agreement (CLA)" color=warning %}}
+
+All contributors are required to [sign a Contributor License Agreement
+(CLA)][CLA] before changes can be approved and merged.
+
+[CLA]: ../prerequisites/#cla
+
+{{% /alert %}}
 
 ```mermaid
 flowchart LR
@@ -330,8 +344,7 @@ using [Netlify](https://www.netlify.com/).
   the OpenTelemetry website with your changes applied. This is how reviewers
   check your changes.
 
-Other checks might also fail. See the
-[list of all PR checks](/docs/contributing/pr-checks).
+Other checks might also fail. See the [list of all PR checks](../pr-checks).
 
 ### Fix content issues automatically
 
@@ -349,9 +362,8 @@ npm run test    # Checks but does not update any files
 npm run fix:all # May update files
 ```
 
-To list available NPM scripts, run `npm run`. See
-[PR checks](/docs/contributing/pr-checks) for more information on pull request
-checks and how to fix errors automatically.
+To list available NPM scripts, run `npm run`. See [PR checks](../pr-checks) for
+more information on pull request checks and how to fix errors automatically.
 
 ### Preview your changes locally {#preview-locally}
 
@@ -501,3 +513,4 @@ Pull requests are merged when they comply with the following criteria:
 [dashboard]: https://app.netlify.com/sites/opentelemetry/overview
 [deploy preview]:
   https://www.netlify.com/blog/2016/07/20/introducing-deploy-previews-in-netlify/
+[PR]: https://docs.github.com/en/pull-requests

content/en/docs/contributing/requirements.md

@@ -22,8 +22,8 @@ before submitting a
 [pull request](https://docs.github.com/en/get-started/learning-about-github/github-glossary#pull-request)
 (PR), run `npm run fix:all` on your local machine and commit the changes.
 
-If you run into errors or [failed PR checks](/docs/contributing/pr-checks), read
-about our style guide and learn what you can do to fix certain common issues.
+If you run into errors or [failed PR checks](../pr-checks), read about our style
+guide and learn what you can do to fix certain common issues.
 
 {{% /alert %}}
 

content/en/docs/contributing/style-guide.md

@@ -1,8 +1,6 @@
 ---
 title: Manage Telemetry with SDK
-linkTitle: Manage Telemetry with SDK
 weight: 11
-aliases: [sdk-concepts]
 cSpell:ignore: autoconfigured FQCNs Interceptable Logback okhttp
 ---
 

content/en/docs/languages/java/sdk.md

@@ -36,7 +36,7 @@ First, on the sending service, inject the current `context`:
 ```python
 from flask import Flask
 import requests
-from opentelemetry import trace, propagators, baggage
+from opentelemetry import trace, baggage
 from opentelemetry.trace.propagation.tracecontext import TraceContextTextMapPropagator
 from opentelemetry.baggage.propagation import W3CBaggagePropagator
 from opentelemetry.sdk.trace import TracerProvider

content/en/docs/languages/python/propagation.md

@@ -147,11 +147,11 @@ probability, a number in the [0..1] range, e.g. "0.25". Default is 1.0.
 
 Exporters output the telemetry.
 
-| Environment variable    | Description                                                                                      | Default value | Status                                              |
-| ----------------------- | ------------------------------------------------------------------------------------------------ | ------------- | --------------------------------------------------- |
-| `OTEL_TRACES_EXPORTER`  | Comma-separated list of propagators. Supported options: `otlp`, `zipkin`, `console`, `none`.     | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
-| `OTEL_METRICS_EXPORTER` | Comma-separated list of propagators. Supported options: `otlp`, `prometheus`, `console`, `none`. | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
-| `OTEL_LOGS_EXPORTER`    | Comma-separated list of propagators. Supported options: `otlp`, `console`, `none`.               | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
+| Environment variable    | Description                                                                                    | Default value | Status                                              |
+| ----------------------- | ---------------------------------------------------------------------------------------------- | ------------- | --------------------------------------------------- |
+| `OTEL_TRACES_EXPORTER`  | Comma-separated list of exporters. Supported options: `otlp`, `zipkin`, `console`, `none`.     | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
+| `OTEL_METRICS_EXPORTER` | Comma-separated list of exporters. Supported options: `otlp`, `prometheus`, `console`, `none`. | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
+| `OTEL_LOGS_EXPORTER`    | Comma-separated list of exporters. Supported options: `otlp`, `console`, `none`.               | `otlp`        | [Stable](/docs/specs/otel/versioning-and-stability) |
 
 ### Traces exporter
 

content/en/docs/zero-code/net/configuration.md

@@ -1,4 +1,4 @@
-# cSpell:ignore apiclarity
+# cSpell:ignore apiclarity apiclarityexporter openclarity
 title: APIClarity HTTP Exporter
 registryType: exporter
 language: collector
@@ -15,3 +15,7 @@ authors:
 urls:
   repo: https://github.com/openclarity/apiclarity/tree/master/plugins/otel-collector
 createdAt: 2022-11-28
+package:
+  name: github.com/openclarity/apiclarity/plugins/otel-collector/apiclarityexporter
+  registry: go-collector
+  version: v0.0.0

data/registry/collector-exporter-apiclarity.yml

@@ -23,4 +23,4 @@ createdAt: 2023-01-31
 package:
   registry: gems
   name: sentry-opentelemetry
-  version: 5.19.0
+  version: 5.20.1

data/registry/tools-ruby-sentry.yml

@@ -15,5 +15,13 @@
 {{ end -}}
 
 {{ range $pages }}
-* [{{ .lang.name }} — {{ .page.Title }}]({{ .page.Permalink }})
-{{ end -}}
+{{ $title := replaceRE `API reference` "" .page.Title -}}
+
+- [
+    {{- .lang.name -}}
+    {{ with $title }} — {{ . }} {{- end -}}
+  ](
+    {{- .page.Permalink -}}
+  )
+
+{{- end -}}

layouts/shortcodes/apidocs.md

@@ -117,7 +117,7 @@
     "ajv-errors": "^3.0.0",
     "ajv-formats": "^3.0.1",
     "autoprefixer": "^10.4.20",
-    "cspell": "^8.14.2",
+    "cspell": "^8.14.4",
     "gulp": "^5.0.0",
     "hugo-extended": "0.133.0",
     "js-yaml": "^4.1.0",
@@ -129,26 +129,26 @@
     "textlint": "^14.2.0",
     "textlint-filter-rule-allowlist": "^4.0.0",
     "textlint-filter-rule-comments": "^1.2.2",
-    "textlint-rule-terminology": "^5.2.6",
+    "textlint-rule-terminology": "^5.2.9",
     "through2": "^4.0.2",
     "yargs": "^17.7.2"
   },
   "dependencies": {
     "@opentelemetry/api": "^1.9.0",
     "@opentelemetry/auto-instrumentations-web": "^0.41.0",
-    "@opentelemetry/context-zone": "^1.25.1",
-    "@opentelemetry/core": "^1.25.1",
+    "@opentelemetry/context-zone": "^1.26.0",
+    "@opentelemetry/core": "^1.26.0",
     "@opentelemetry/exporter-trace-otlp-http": "^0.53.0",
     "@opentelemetry/instrumentation": "^0.53.0",
-    "@opentelemetry/resources": "^1.25.1",
-    "@opentelemetry/sdk-trace-base": "^1.25.1",
-    "@opentelemetry/sdk-trace-web": "^1.25.1",
-    "@opentelemetry/semantic-conventions": "^1.26.0",
+    "@opentelemetry/resources": "^1.26.0",
+    "@opentelemetry/sdk-trace-base": "^1.26.0",
+    "@opentelemetry/sdk-trace-web": "^1.26.0",
+    "@opentelemetry/semantic-conventions": "^1.27.0",
     "path": "^0.12.7"
   },
   "optionalDependencies": {
-    "netlify-cli": "^17.34.3",
-    "npm-check-updates": "^17.1.0"
+    "netlify-cli": "^17.36.2",
+    "npm-check-updates": "^17.1.3"
   },
   "enginesComment": "Ensure that engines.node value stays consistent with the project's .nvmrc",
   "engines": {

package.json

@@ -2591,6 +2591,10 @@
     "StatusCode": 206,
     "LastSeen": "2024-06-12T11:21:07.765039+02:00"
   },
+  "https://docs.github.com/en/pull-requests": {
+    "StatusCode": 206,
+    "LastSeen": "2024-09-28T12:02:48.071874-04:00"
+  },
   "https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests": {
     "StatusCode": 206,
     "LastSeen": "2024-01-30T15:25:17.633498-05:00"
@@ -10795,6 +10799,10 @@
     "StatusCode": 200,
     "LastSeen": "2024-08-09T11:01:13.220618-04:00"
   },
+  "https://pkg.go.dev/github.com/openclarity/apiclarity/plugins/otel-collector/apiclarityexporter": {
+    "StatusCode": 200,
+    "LastSeen": "2024-08-12T17:56:07.964057+02:00"
+  },
   "https://pkg.go.dev/go.opentelemetry.io/collector/cmd/builder": {
     "StatusCode": 200,
     "LastSeen": "2024-03-01T16:49:30.684687+01:00"