diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 6b090dbe7bc3..f61d9e7aba30 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -14,40 +14,3 @@ # Global owners, will be the owners for everything in the repo. * @open-telemetry/docs-approvers - -# content owners -content-modules/ @open-telemetry/docs-maintainers -content-modules/opamp-spec @open-telemetry/docs-maintainers @open-telemetry/opamp-spec-approvers -content-modules/opentelemetry-proto @open-telemetry/docs-maintainers @open-telemetry/specs-approvers -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/sig-end-user-approvers -content/en/docs/collector @open-telemetry/docs-approvers @open-telemetry/collector-approvers -content/en/docs/contributing/ @open-telemetry/docs-approvers @open-telemetry/docs-maintainers -content/en/docs/demo @open-telemetry/docs-approvers @open-telemetry/demo-approvers -content/en/docs/kubernetes/helm/ @open-telemetry/docs-approvers @open-telemetry/helm-approvers -content/en/docs/kubernetes/operator/ @open-telemetry/docs-approvers @open-telemetry/operator-approvers -content/en/docs/languages/cpp/ @open-telemetry/docs-approvers @open-telemetry/cpp-approvers -content/en/docs/languages/erlang/ @open-telemetry/docs-approvers @open-telemetry/erlang-approvers -content/en/docs/languages/go/ @open-telemetry/docs-approvers @open-telemetry/go-approvers @open-telemetry/go-instrumentation-approvers -content/en/docs/languages/java/ @open-telemetry/docs-approvers @open-telemetry/java-approvers @open-telemetry/java-instrumentation-approvers -content/en/docs/languages/js/ @open-telemetry/docs-approvers @open-telemetry/javascript-approvers -content/en/docs/languages/net/ @open-telemetry/docs-approvers @open-telemetry/dotnet-approvers @open-telemetry/dotnet-instrumentation-approvers -content/en/docs/languages/php/ @open-telemetry/docs-approvers @open-telemetry/php-approvers -content/en/docs/languages/python/ @open-telemetry/docs-approvers @open-telemetry/python-approvers -content/en/docs/languages/ruby/ @open-telemetry/docs-approvers @open-telemetry/ruby-approvers @open-telemetry/ruby-contrib-approvers -content/en/docs/languages/rust/ @open-telemetry/docs-approvers @open-telemetry/rust-approvers -content/en/docs/languages/swift/ @open-telemetry/docs-approvers @open-telemetry/swift-approvers -content/en/docs/security/ @open-telemetry/docs-approvers @open-telemetry/sig-security-maintainers -content/en/docs/specs/ @open-telemetry/docs-approvers @open-telemetry/specs-approvers -content/en/docs/zero-code/go @open-telemetry/docs-approvers @open-telemetry/go-approvers @open-telemetry/go-instrumentation-approvers -content/en/docs/zero-code/java/ @open-telemetry/docs-approvers @open-telemetry/java-approvers @open-telemetry/java-instrumentation-approvers -content/en/docs/zero-code/js/ @open-telemetry/docs-approvers @open-telemetry/javascript-approvers -content/en/docs/zero-code/net/ @open-telemetry/docs-approvers @open-telemetry/dotnet-approvers @open-telemetry/dotnet-instrumentation-approvers -content/en/docs/zero-code/python/ @open-telemetry/docs-approvers @open-telemetry/python-approvers -content/en/docs/zero-code/php/ @open-telemetry/docs-approvers @open-telemetry/php-approvers -content/en/ecosystem/demo/ @open-telemetry/demo-approvers @open-telemetry/demo-approvers -content/zh/ @open-telemetry/docs-maintainers @open-telemetry/docs-zh-approvers -content/ja/ @open-telemetry/docs-maintainers @open-telemetry/docs-ja-approvers - diff --git a/.github/component-label-map.yml b/.github/component-label-map.yml index 1b1a7cae663c..a27e9017581a 100644 --- a/.github/component-label-map.yml +++ b/.github/component-label-map.yml @@ -14,6 +14,10 @@ lang:ja: - changed-files: - any-glob-to-any-file: - content/ja/** +lang:pt: + - changed-files: + - any-glob-to-any-file: + - content/pt/** sig:cpp: - changed-files: - any-glob-to-any-file: diff --git a/.github/component-owners.yml b/.github/component-owners.yml new file mode 100644 index 000000000000..f92ed31dbe18 --- /dev/null +++ b/.github/component-owners.yml @@ -0,0 +1,79 @@ +# This file is used to define the owners of the content modules in the OpenTelemetry repository. +components: + content-modules: + - open-telemetry/docs-maintainers + content-modules/opamp-spec: + - open-telemetry/docs-maintainers + - open-telemetry/opamp-spec-approvers + content-modules/opentelemetry-proto: + - open-telemetry/docs-maintainers + - open-telemetry/specs-approvers + 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/sig-end-user-approvers + content/en/docs/collector: + - open-telemetry/collector-approvers + content/en/docs/contributing: + - open-telemetry/docs-maintainers + content/en/docs/demo: + - open-telemetry/demo-approvers + content/en/docs/kubernetes/helm: + - open-telemetry/helm-approvers + content/en/docs/kubernetes/operator: + - open-telemetry/operator-approvers + content/en/docs/languages/cpp: + - open-telemetry/cpp-approvers + content/en/docs/languages/erlang: + - open-telemetry/erlang-approvers + content/en/docs/languages/go: + - open-telemetry/go-approvers + - open-telemetry/go-instrumentation-approvers + content/en/docs/languages/java: + - open-telemetry/java-approvers + - open-telemetry/java-instrumentation-approvers + content/en/docs/languages/js: + - open-telemetry/javascript-approvers + content/en/docs/languages/net: + - open-telemetry/dotnet-approvers + - open-telemetry/dotnet-instrumentation-approvers + content/en/docs/languages/php: + - open-telemetry/php-approvers + content/en/docs/languages/python: + - open-telemetry/python-approvers + content/en/docs/languages/ruby: + - open-telemetry/ruby-approvers + - open-telemetry/ruby-contrib-approvers + content/en/docs/languages/rust: + - open-telemetry/rust-approvers + content/en/docs/languages/swift: + - open-telemetry/swift-approvers + content/en/docs/security: + - open-telemetry/sig-security-maintainers + content/en/docs/specs: + - open-telemetry/specs-approvers + content/en/docs/zero-code/java: + - open-telemetry/java-approvers + - open-telemetry/java-instrumentation-approvers + content/en/docs/zero-code/js: + - open-telemetry/javascript-approvers + content/en/docs/zero-code/net: + - open-telemetry/dotnet-approvers + - open-telemetry/dotnet-instrumentation-approvers + content/en/ecosystem/demo: + - open-telemetry/demo-approvers + content/zh: + - open-telemetry/docs-maintainers + - open-telemetry/docs-zh-approvers + content/ja: + - open-telemetry/docs-maintainers + - open-telemetry/docs-ja-approvers + content/pt: + - open-telemetry/docs-maintainers + - open-telemetry/docs-pt-approvers diff --git a/.github/workflows/component-owners.yml b/.github/workflows/component-owners.yml new file mode 100644 index 000000000000..7615888440d9 --- /dev/null +++ b/.github/workflows/component-owners.yml @@ -0,0 +1,15 @@ +name: Component owners +on: + pull_request_target: + +jobs: + run_self: + runs-on: ubuntu-latest + name: Assign component owners + permissions: + contents: read + pull-requests: write + steps: + - uses: dyladan/component-owners@v0.1.0 + with: + config-file: .github/component-owners.yml diff --git a/content/en/blog/2022/debug-otel-with-otel/index.md b/content/en/blog/2022/debug-otel-with-otel/index.md index 622f09478107..fa89614193d5 100644 --- a/content/en/blog/2022/debug-otel-with-otel/index.md +++ b/content/en/blog/2022/debug-otel-with-otel/index.md @@ -260,5 +260,5 @@ COPY opentelemetry_module.conf /etc/nginx/conf.d [v1.0.1 release of the otel-webserver-module]: https://github.com/open-telemetry/opentelemetry-cpp-contrib/releases/tag/webserver%2Fv1.0.1 [java]: - /docs/zero-code/java/agent/configuration/#capturing-http-request-and-response-headers + /docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers [python]: /docs/zero-code/python/ diff --git a/content/en/blog/2024/otel-errors/index.md b/content/en/blog/2024/otel-errors/index.md index e7043078b654..c102787383ff 100644 --- a/content/en/blog/2024/otel-errors/index.md +++ b/content/en/blog/2024/otel-errors/index.md @@ -138,10 +138,6 @@ 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 diff --git a/content/en/blog/2024/security-audit-results.md b/content/en/blog/2024/security-audit-results.md new file mode 100644 index 000000000000..92710035f1af --- /dev/null +++ b/content/en/blog/2024/security-audit-results.md @@ -0,0 +1,43 @@ +--- +title: OpenTelemetry Security Audit Published +linkTitle: Security Audit Results +date: 2024-07-22 +author: '[Austin Parker](https://github.com/austinlparker)' +issue: +sig: GC +--- + +Thousands of organizations and millions of users around the world rely on +[OpenTelemetry](/) as part of their observability toolkit. To this end, it is +our responsibility as a project to ensure our code is safe, secure, and +performant. In conjunction with [OSTIF](https://ostif.org/) and +[7ASecurity](https://7asecurity.com/), and the support of the +[Cloud Native Computing Foundation](https://www.cncf.io/), we recently engaged +upon a security audit of the OpenTelemetry Collector and four SDKs – Go, Java, +C#, and Python. + +We are pleased to announce the publication of this audit, as well as its +results. One CVE was identified and remediated prior to the publication of this +audit (see [CVE-2024-36129](https://nvd.nist.gov/vuln/detail/CVE-2024-36129) for +information) in the OpenTelemetry Collector, and five hardening recommendations +were made. Overall, the results of the audit are very positive, with the +auditors noting the high quality of source code and the security best practices +that the project is following. + +The conclusion of this audit marks an important milestone on our journey towards +the next stage of maturity in the CNCF, graduation. We’ll have more to share on +that in the coming months. The OpenTelemetry Governance Committee and Security +SIG would also like to personally commend the contributors and maintainers of +OpenTelemetry for their high-quality work over the years. + +Finally, we would like to thank the following individuals and groups: + +- SIG Security +- SIG Collector +- 7ASecurity +- OSTIF + +You can read more about the audit on the +[OSTIF](https://www.ostif.org/otel-audit-complete/) and 7A Security blogs, or +read the +[full report](https://7asecurity.com/reports/pentest-report-opentelemetry.pdf). diff --git a/content/en/docs/collector/_index.md b/content/en/docs/collector/_index.md index c6613dda5666..87ccbf9e0328 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.104.0 + vers: 0.105.0 weight: 270 --- diff --git a/content/en/docs/collector/internal-telemetry.md b/content/en/docs/collector/internal-telemetry.md index 2c4190b4a205..b86e113405f2 100644 --- a/content/en/docs/collector/internal-telemetry.md +++ b/content/en/docs/collector/internal-telemetry.md @@ -193,7 +193,7 @@ categorized by instrumentation type. | Metric name | Description | Type | | ------------------------------------------------------ | --------------------------------------------------------------------------------------- | --------- | -| `otelcol_exporter_enqueue_failed_`
`log_records` | Number of spans that exporter(s) failed to enqueue. | Counter | +| `otelcol_exporter_enqueue_failed_`
`log_records` | Number of logs that exporter(s) failed to enqueue. | Counter | | `otelcol_exporter_enqueue_failed_`
`metric_points` | Number of metric points that exporter(s) failed to enqueue. | Counter | | `otelcol_exporter_enqueue_failed_`
`spans` | Number of spans that exporter(s) failed to enqueue. | Counter | | `otelcol_exporter_queue_capacity` | Fixed capacity of the retry queue, in batches. | Gauge | diff --git a/content/en/docs/faas/lambda-auto-instrument.md b/content/en/docs/faas/lambda-auto-instrument.md index b297e2b16b5b..732d26243da7 100644 --- a/content/en/docs/faas/lambda-auto-instrument.md +++ b/content/en/docs/faas/lambda-auto-instrument.md @@ -56,7 +56,7 @@ variables: instrumentations, see [Suppressing specific agent instrumentation][1]. [1]: - /docs/zero-code/java/agent/configuration/#suppressing-specific-agent-instrumentation + /docs/zero-code/java/agent/disable/#suppressing-specific-agent-instrumentation For example, to only enable auto-instrumentation for Lambda and the AWS SDK, you would set the following environment variables: diff --git a/content/en/docs/kubernetes/operator/automatic.md b/content/en/docs/kubernetes/operator/automatic.md index 5eca24528a68..d86d03000f5d 100644 --- a/content/en/docs/kubernetes/operator/automatic.md +++ b/content/en/docs/kubernetes/operator/automatic.md @@ -212,7 +212,7 @@ Therefore, the example uses `http://demo-collector:4318`, which connects to the #### Excluding auto-instrumentation {#java-excluding-auto-instrumentation} By default, the Java auto-instrumentation ships with -[many instrumentation libraries](/docs/zero-code/java/agent/#supported-libraries-frameworks-application-services-and-jvms). +[many instrumentation libraries](/docs/zero-code/java/agent/getting-started/#supported-libraries-frameworks-application-services-and-jvms). This makes instrumentation easy, but could result in too much or unwanted data. If there are any libraries you do not want to use you can set the `OTEL_INSTRUMENTATION_[NAME]_ENABLED=false` where `[NAME]` is the name of the @@ -221,7 +221,7 @@ the default libraries by setting `OTEL_INSTRUMENTATION_COMMON_DEFAULT_ENABLED=false` and then use `OTEL_INSTRUMENTATION_[NAME]_ENABLED=true` where `[NAME]` is the name of the library. For more details, see -[Suppressing specific instrumentation](/docs/zero-code/java/agent/configuration/#suppressing-specific-instrumentation). +[Suppressing specific instrumentation](/docs/zero-code/java/agent/disable/). ```yaml apiVersion: opentelemetry.io/v1alpha1 diff --git a/content/en/docs/languages/go/instrumentation.md b/content/en/docs/languages/go/instrumentation.md index 634e83b6fd66..41ca2e98046f 100644 --- a/content/en/docs/languages/go/instrumentation.md +++ b/content/en/docs/languages/go/instrumentation.md @@ -1063,13 +1063,12 @@ Now that a `LoggerProvider` is configured, you can use it to set up a A log bridge is a component that bridges logs from an existing log package into the OpenTelemetry [Log SDK](#logs-sdk) using the [Logs Bridge -API][logs bridge API]. Log bridges are available for various popular Go log -packages: +API][logs bridge API]. -- [logrus bridge][otellogrus] -- [slog bridge][otelslog] +A full list of log bridges available can be found in the +[OpenTelemetry registry](/ecosystem/registry/?language=go&component=log-bridge). -The links above contain full usage and installation documentation. +Each log bridge package documentation should have a usage example. ### Via file or stdout @@ -1097,8 +1096,6 @@ telemetry backends. https://github.com/open-telemetry/opentelemetry-collector [logs bridge API]: /docs/specs/otel/logs/bridge-api [log data model]: /docs/specs/otel/logs/data-model -[otellogrus]: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otellogrus -[otelslog]: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelslog [`go.opentelemetry.io/otel`]: https://pkg.go.dev/go.opentelemetry.io/otel [`go.opentelemetry.io/otel/exporters/stdout/stdoutmetric`]: https://pkg.go.dev/go.opentelemetry.io/otel/exporters/stdout/stdoutmetric diff --git a/content/en/docs/languages/java/_index.md b/content/en/docs/languages/java/_index.md index 00959f5e2080..679aefd04f01 100644 --- a/content/en/docs/languages/java/_index.md +++ b/content/en/docs/languages/java/_index.md @@ -6,7 +6,7 @@ description: >- aliases: [/java, /java/metrics, /java/tracing] cascade: vers: - instrumentation: 2.5.0 + instrumentation: 2.6.0 otel: 1.40.0 semconv: 1.26.0 weight: 18 diff --git a/content/en/docs/languages/java/getting-started.md b/content/en/docs/languages/java/getting-started.md index 68de7ef50d5e..7405286cb343 100644 --- a/content/en/docs/languages/java/getting-started.md +++ b/content/en/docs/languages/java/getting-started.md @@ -248,7 +248,7 @@ For more: [metrics]: /docs/concepts/signals/metrics/ [logs]: /docs/concepts/signals/logs/ [annotations]: /docs/zero-code/java/agent/annotations/ -[configure the java agent]: /docs/zero-code/java/agent/#configuring-the-agent +[configure the java agent]: /docs/zero-code/java/agent/configuration/ [console exporter]: https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#logging-exporter [exporter]: diff --git a/content/en/docs/languages/java/libraries.md b/content/en/docs/languages/java/libraries.md index 72429f1a0e63..2c2179ba542e 100644 --- a/content/en/docs/languages/java/libraries.md +++ b/content/en/docs/languages/java/libraries.md @@ -16,7 +16,7 @@ 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 turn off certain instrumentation libraries, you can -[suppress them](/docs/zero-code/java/agent/configuration/#suppressing-specific-instrumentation). +[suppress them](/docs/zero-code/java/agent/disable/). If you use [code-based instrumentation](../instrumentation), you can leverage some instrumentation libraries for your dependencies standalone. To find out diff --git a/content/en/docs/languages/java/performance.md b/content/en/docs/languages/java/performance.md new file mode 100644 index 000000000000..d47dae31e231 --- /dev/null +++ b/content/en/docs/languages/java/performance.md @@ -0,0 +1,194 @@ +--- +title: Performance +description: Performance reference for the OpenTelemetry Java agent +weight: 75 +--- + +The OpenTelemetry Java agent instruments your application by running inside the +same Java Virtual Machine (JVM). Like any other software agent, the Java agent +requires system resources like CPU, memory, and network bandwidth. The use of +resources by the agent is called agent overhead or performance overhead. The +OpenTelemetry Java agent has minimal impact on system performance when +instrumenting JVM applications, although the final agent overhead depends on +multiple factors. + +Some factors that might increase agent overhead are environmental, such as the +physical machine architecture, CPU frequency, amount and speed of memory, system +temperature, and resource contention. Other factors include virtualization and +containerization, the operating system and its libraries, the JVM version and +vendor, JVM settings, the algorithmic design of the software being monitored, +and software dependencies. + +Due to the complexity of modern software and the broad diversity in deployment +scenarios, it is impossible to come up with a single agent overhead estimate. To +find the overhead of any instrumentation agent in a given deployment, you have +to conduct experiments and collect measurements directly. Therefore, treat all +statements about performance as general information and guidelines that are +subject to evaluation in a specific system. + +The following sections describe the minimum requirements of the OpenTelemetry +Java agent, as well as potential constraints impacting performance, and +guidelines to optimize and troubleshoot the performance of the agent. + +## Guidelines to reduce agent overhead + +The following best practices and techniques might help reduce overhead caused by +the Java agent. + +### Configure trace sampling + +The volume of spans processed by the instrumentation might impact agent +overhead. You can configure trace sampling to adjust the span volume and reduce +resource usage. See [Sampling](/docs/languages/java/sampling). + +### Turn off specific instrumentations + +You can further reduce agent overhead by turning off instrumentations that +aren't needed or are producing too many spans. To turn off an instrumentation, +use `-Dotel.instrumentation..enabled=false` or the +`OTEL_INSTRUMENTATION__ENABLED` environment variable, where `` is +the name of the instrumentation. + +For example, the following option turns off the JDBC instrumentation: +`-Dotel.instrumentation.jdbc.enabled=false` + +### Allocate more memory for the application + +Increasing the maximum heap size of the JVM using the `-Xmx` option might +help in alleviating agent overhead issues, as instrumentations can generate a +large number of short-lived objects in memory. + +### Reduce manual instrumentation to what you need + +Too much manual instrumentation might introduce inefficiencies that increase +agent overhead. For example, using `@WithSpan` on every method results in a high +span volume, which in turn increases noise in the data and consumes more system +resources. + +### Provision adequate resources + +Make sure to provision enough resources for your instrumentation and for the +Collector. The amount of resources such as memory or disk depend on your +application architecture and needs. For example, a common setup is to run the +instrumented application on the same host as the OpenTelemetry Collector. In +that case, consider rightsizing the resources for the Collector and optimize its +settings. See [Scaling](/docs/collector/scaling/). + +## Constraints impacting the performance of the Java agent + +In general, the more telemetry you collect from your application, the greater +the the impact on agent overhead. For example, tracing methods that aren't +relevant to your application can still produce considerable agent overhead +because tracing such methods is computationally more expensive than running the +method itself. Similarly, high cardinality tags in metrics might increase memory +usage. Debug logging, if turned on, also increases write operations to disk and +memory usage. + +Some instrumentations, for example JDBC or Redis, produce high span volumes that +increase agent overhead. For more information on how to turn off unnecessary +instrumentations, see +[Turn off specific instrumentations](#turn-off-specific-instrumentations). + +> [!NOTE] Experimental features of the Java agent might increase agent overhead +> due to the experimental focus on functionality over performance. Stable +> features are safer in terms of agent overhead. + +## Troubleshooting agent overhead issues + +When troubleshooting agent overhead issues, do the following: + +- Check minimum requirements. See + [Prerequisites](/docs/languages/java/getting-started/#prerequisites). +- Use the latest compatible version of the Java agent. +- Use the latest compatible version of your JVM. + +Consider taking the following actions to decrease agent overhead: + +- If your application is approaching memory limits, consider giving it more + memory. +- If your application is using all the CPU, you might want to scale it + horizontally. +- Try turning off or tuning metrics. +- Tune trace sampling settings to reduce span volume. +- Turn off specific instrumentations. +- Review manual instrumentation for unnecessary span generation. + +## Guidelines for measuring agent overhead + +Measuring agent overhead in your own environment and deployments provides +accurate data about the impact of instrumentation on the performance of your +application or service. The following guidelines describe the general steps for +collecting and comparing reliable agent overhead measurements. + +### Decide what you want to measure + +Different users of your application or service might notice different aspects of +agent overhead. For example, while end users might notice degradation in service +latency, power users with heavy workloads pay more attention to CPU overhead. On +the other hand, users who deploy frequently, for example due to elastic +workloads, care more about startup time. + +Reduce your measurements to factors that are sure to impact user experience, so +your datasets don't contain irrelevant information. Some examples of +measurements include the following: + +- User average, user peak, and machine average CPU usage +- Total memory allocated and maximum heap used +- Garbage collection pause time +- Startup time in milliseconds +- Average and percentile 95 (p95) service latency +- Network read and write average throughput + +### Prepare a suitable test environment + +By measuring agent overhead in a controlled test environment you can better +identify the factors affecting performance. When preparing a test environment, +complete the following: + +1. Make sure that the configuration of the test environment resembles + production. +2. Isolate the application under test from other services that might interfere. +3. Turn off or remove all unnecessary system services on the application host. +4. Ensure that the application has enough system resources to handle the test + workload. + +### Create a battery of realistic tests + +Design the tests that you run against the test environment to resemble typical +workloads as much as possible. For example, if some REST API endpoints of your +service are susceptible to high request volumes, create a test that simulates +heavy network traffic. + +For Java applications, use a warm-up phase prior to starting measurements. The +JVM is a highly dynamic machine that performs a large number of optimizations +through just-in-time compilation (JIT). The warm-up phase helps the application +to finish most of its class loading and gives the JIT compiler time to run the +majority of optimizations. + +Make sure to run a large number of requests and to repeat the test pass many +times. This repetition helps to ensure a representative data sample. Include +error scenarios in your test data. Simulate an error rate similar to that of a +normal workload, typically between 2% and 10%. + +{{% alert title="Note" color="info" %}} + +Tests might increase costs when targeting observability backends and other +commercial services. Plan your tests accordingly or consider using alternative +solutions, such as self-hosted or locally run backends. + +{{% /alert %}} + +### Collect comparable measurements + +To identify which factors might be affecting performance and causing agent +overhead, collect measurements in the same environment after modifying a single +factor or condition. + +### Analyze the agent overhead data + +After collecting data from multiple passes, you can plot results in a chart or +compare averages using statistical tests to check for significant differences. + +Consider that different stacks, applications, and environments might result in +different operational characteristics and different agent overhead measurement +results. diff --git a/content/en/docs/languages/php/sdk.md b/content/en/docs/languages/php/sdk.md index 0dd2485bf8f7..fcc89f0dca92 100644 --- a/content/en/docs/languages/php/sdk.md +++ b/content/en/docs/languages/php/sdk.md @@ -130,6 +130,7 @@ There are also a number of PHP-specific configurations: | `OTEL_PHP_INTERNAL_METRICS_ENABLED` | `false` | `true`, `false` | `true` | Whether the SDK should emit metrics about its internal state (for example, batch processors) | | `OTEL_PHP_DISABLED_INSTRUMENTATIONS` | `[]` | Instrumentation names, or `all` | `psr15,psr18` | Disable one or more installed auto-instrumentations | | `OTEL_PHP_EXCLUDED_URLS` | `` | Comma-delimited regular expression patterns | `client/.*/info,healthcheck` | Do not load the SDK if request URL matches one of the supplied regular expressions | +| `OTEL_PHP_DEBUG_SCOPES_DISABLED` | `false` | `true`, `false` | `true` | Turn on or off scope detachment debugging. | Configurations can be provided as environment variables, or via `php.ini` (or a file included by `php.ini`) diff --git a/content/en/docs/languages/python/_index.md b/content/en/docs/languages/python/_index.md index d6aedadda30d..395cdf4dd0e8 100644 --- a/content/en/docs/languages/python/_index.md +++ b/content/en/docs/languages/python/_index.md @@ -55,8 +55,7 @@ This can be done by cloning the repository and doing an ```sh git clone https://github.com/open-telemetry/opentelemetry-python.git cd opentelemetry-python -pip install -e ./opentelemetry-api -pip install -e ./opentelemetry-sdk +pip install -e ./opentelemetry-api -e ./opentelemetry-sdk -e ./opentelemetry-semantic-conventions ``` ## Repositories and benchmarks diff --git a/content/en/docs/zero-code/java/_index.md b/content/en/docs/zero-code/java/_index.md index 2005b37188c9..f6723a6ef0ca 100644 --- a/content/en/docs/zero-code/java/_index.md +++ b/content/en/docs/zero-code/java/_index.md @@ -6,8 +6,8 @@ aliases: - /docs/languages/java/automatic_instrumentation cascade: vers: - instrumentation: 2.5.0 - otel: 1.39.0 + instrumentation: 2.6.0 + otel: 1.40.0 --- Zero-code instrumentation with Java uses a Java agent JAR or Spring Boot diff --git a/content/en/docs/zero-code/java/agent/_index.md b/content/en/docs/zero-code/java/agent/_index.md index d5ae700e89a1..d9780a49dcdc 100644 --- a/content/en/docs/zero-code/java/agent/_index.md +++ b/content/en/docs/zero-code/java/agent/_index.md @@ -5,7 +5,6 @@ aliases: - /docs/java/automatic_instrumentation - /docs/languages/java/automatic_instrumentation redirects: [{ from: /docs/languages/java/automatic/*, to: ':splat' }] -cSpell:ignore: Dotel myapp --- Zero-code instrumentation with Java uses a Java agent JAR attached to any Java @@ -14,97 +13,3 @@ popular libraries and frameworks. It can be used to capture telemetry data at the "edges" of an app or service, such as inbound requests, outbound HTTP calls, database calls, and so on. To learn how to manually instrument your service or app code, see [Manual instrumentation](/docs/languages/java/instrumentation/). - -## Setup - -1. Download [opentelemetry-javaagent.jar][] from [Releases][] of the - `opentelemetry-java-instrumentation` repository and place the JAR in your - preferred directory. The JAR file contains the agent and instrumentation - libraries. -2. Add `-javaagent:path/to/opentelemetry-javaagent.jar` and other config to - your JVM startup arguments and launch your app: - - - Directly on the startup command: - - ```shell - java -javaagent:path/to/opentelemetry-javaagent.jar -Dotel.service.name=your-service-name -jar myapp.jar - ``` - - - Via the `JAVA_TOOL_OPTIONS` and other environment variables: - - ```shell - export JAVA_TOOL_OPTIONS="-javaagent:path/to/opentelemetry-javaagent.jar" - export OTEL_SERVICE_NAME="your-service-name" - java -jar myapp.jar - ``` - -## Configuring the agent - -The agent is highly configurable. - -One option is to pass configuration properties via the `-D` flag. In this -example, a service name and Zipkin exporter for traces are configured: - -```sh -java -javaagent:path/to/opentelemetry-javaagent.jar \ - -Dotel.service.name=your-service-name \ - -Dotel.traces.exporter=zipkin \ - -jar myapp.jar -``` - -You can also use environment variables to configure the agent: - -```sh -OTEL_SERVICE_NAME=your-service-name \ -OTEL_TRACES_EXPORTER=zipkin \ -java -javaagent:path/to/opentelemetry-javaagent.jar \ - -jar myapp.jar -``` - -You can also supply a Java properties file and load configuration values from -there: - -```sh -java -javaagent:path/to/opentelemetry-javaagent.jar \ - -Dotel.javaagent.configuration-file=path/to/properties/file.properties \ - -jar myapp.jar -``` - -or - -```sh -OTEL_JAVAAGENT_CONFIGURATION_FILE=path/to/properties/file.properties \ -java -javaagent:path/to/opentelemetry-javaagent.jar \ - -jar myapp.jar -``` - -To see the full range of configuration options, see -[Agent Configuration](configuration). - -## Supported libraries, frameworks, application services, and JVMs - -The Java agent ships with instrumentation libraries for many popular components. -For the full list, see [Supported libraries, frameworks, application services, -and JVMs][support]. - -## Troubleshooting - -{{% config_option name="otel.javaagent.debug" %}} - -Set to `true` to see debug logs. Note that these are quite verbose. - -{{% /config_option %}} - -## Next steps - -After you have automatic instrumentation configured for your app or service, you -might want to [annotate](annotations) selected methods or add -[manual instrumentation](/docs/languages/java/instrumentation/) to collect -custom telemetry data. - -[opentelemetry-javaagent.jar]: - https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar -[releases]: - https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases -[support]: - https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md diff --git a/content/en/docs/zero-code/java/agent/configuration.md b/content/en/docs/zero-code/java/agent/configuration.md index 83682b41f79d..3bfe107acd08 100644 --- a/content/en/docs/zero-code/java/agent/configuration.md +++ b/content/en/docs/zero-code/java/agent/configuration.md @@ -1,60 +1,24 @@ --- -title: Agent Configuration -linkTitle: Configuration +title: Configuration weight: 10 aliases: [agent-config] -# prettier-ignore -cSpell:ignore: akka armeria classloaders couchbase Customizer datasource dbcp Dotel dropwizard dubbo enduser finatra hikari hikaricp HSET httpasyncclient httpclient hystrix jaxrs jaxws jedis jodd kotlinx logback logmanager mojarra myfaces okhttp oshi pekko rabbitmq ratpack rediscala redisson restlet rocketmq serverlessapis spymemcached twilio vaadin vertx vibur webflux webmvc --- -## SDK Autoconfiguration - -The SDK's autoconfiguration module is used for basic configuration of the agent. -Read the [docs](/docs/languages/java/configuration) to find settings such as -configuring export or sampling. - -{{% 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 -can enable additional resource providers that are disabled by default: - -{{% config_option -name="otel.resource.providers.aws.enabled" -default=false -%}} Enables the -[AWS Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/aws-resources). -{{% /config_option %}} - -{{% config_option -name="otel.resource.providers.gcp.enabled" -default=false -%}} Enables the -[GCP Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources). -{{% /config_option %}} - -## Configuring the agent +## Agent Configuration The agent can consume configuration from one or more of the following sources (ordered from highest to lowest priority): -- system properties -- [environment variables](#configuring-with-environment-variables) -- the [configuration file](#configuration-file) -- properties provided by the +- System properties +- [Environment variables](#configuring-with-environment-variables) +- [Configuration file](#configuration-file) +- Properties provided by the [`AutoConfigurationCustomizer#addPropertiesSupplier()`](https://github.com/open-telemetry/opentelemetry-java/blob/f92e02e4caffab0d964c02a32fe305d6d6ba372e/sdk-extensions/autoconfigure-spi/src/main/java/io/opentelemetry/sdk/autoconfigure/spi/AutoConfigurationCustomizer.java#L73) function; using the [`AutoConfigurationCustomizerProvider`](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure-spi/src/main/java/io/opentelemetry/sdk/autoconfigure/spi/AutoConfigurationCustomizerProvider.java) SPI -### Configuring with Environment Variables +## Configuring with Environment Variables In some environments, configuring via Environment Variables is more preferred. Any setting configurable with a System Property can also be configured with an @@ -68,7 +32,7 @@ desired System Property: For example `otel.instrumentation.common.default-enabled` would convert to `OTEL_INSTRUMENTATION_COMMON_DEFAULT_ENABLED`. -### Configuration file +## Configuration file You can provide a path to agent configuration file by setting the following property: @@ -77,7 +41,7 @@ property: Java properties file which contains the agent configuration. {{% /config_option %}} -### Extensions +## Extensions You can enable [extensions][] by setting the following property: @@ -89,7 +53,7 @@ extension. {{% /config_option %}} -### Java agent logging output +## Java agent logging output The agent's logging output can be configured by setting the following property: @@ -111,484 +75,38 @@ The Java agent logging mode. The following 3 modes are supported: {{% /config_option %}} -## Common instrumentation configuration - -Common settings that apply to multiple instrumentations at once. - -### Peer service name - -The -[peer service name](/docs/specs/semconv/general/attributes/#general-remote-service-attributes) -is the name of a remote service to which a connection is made. It corresponds to -`service.name` in the [resource](/docs/specs/semconv/resource/#service) for the -local service. - -{{% config_option name="otel.instrumentation.common.peer-service-mapping" %}} - -Used to specify a mapping from host names or IP addresses to peer services, as a -comma-separated list of `=` pairs. The peer -service is added as an attribute to a span whose host or IP address match the -mapping. - -For example, if set to the following: - - 1.2.3.4=cats-service,dogs-abcdef123.serverlessapis.com=dogs-api - -Then, requests to `1.2.3.4` will have a `peer.service` attribute of -`cats-service` and requests to `dogs-abcdef123.serverlessapis.com` will have an -attribute of `dogs-api`. - -Since Java agent version `1.31.0`, it is possible to provide a port and a path -to define a `peer.service`. - -For example, if set to the following: - - 1.2.3.4:443=cats-service,dogs-abcdef123.serverlessapis.com:80/api=dogs-api - -Then, requests to `1.2.3.4` will have no override for `peer.service` attribute, -while `1.2.3.4:443` will have have `peer.service` of `cats-service` and requests -to `dogs-abcdef123.serverlessapis.com:80/api/v1` will have an attribute of -`dogs-api`. - -{{% /config_option %}} - -### DB statement sanitization - -The agent sanitizes all database queries/statements before setting the -`db.statement` semantic attribute. All values (strings, numbers) in the query -string are replaced with a question mark (`?`). - -Note: JDBC bind parameters are not captured in `db.statement`. See -[the corresponding issue](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7413) -if you are looking to capture bind parameters. - -Examples: - -- SQL query `SELECT a from b where password="secret"` will appear as - `SELECT a from b where password=?` in the exported span; -- Redis command `HSET map password "secret"` will appear as - `HSET map password ?` in the exported span. - -This behavior is turned on by default for all database instrumentations. Use the -following property to disable it: - -{{% config_option -name="otel.instrumentation.common.db-statement-sanitizer.enabled" -default=true -%}} Enables the DB statement sanitization. {{% /config_option %}} - -### HTTP instrumentation configuration - -#### Capturing HTTP request and response headers - -You can configure the agent to capture predefined HTTP headers as span -attributes, according to the -[semantic convention](/docs/specs/semconv/http/http-spans/). Use the following -properties to define which HTTP headers you want to capture: - -{{% config_option name="otel.instrumentation.http.client.capture-request-headers" %}} -A comma-separated list of HTTP header names. HTTP client instrumentations will -capture HTTP request header values for all configured header names. -{{% /config_option %}} - -{{% config_option name="otel.instrumentation.http.client.capture-response-headers" %}} -A comma-separated list of HTTP header names. HTTP client instrumentations will -capture HTTP response header values for all configured header names. -{{% /config_option %}} - -{{% config_option name="otel.instrumentation.http.server.capture-request-headers" %}} -A comma-separated list of HTTP header names. HTTP server instrumentations will -capture HTTP request header values for all configured header names. -{{% /config_option %}} - -{{% config_option name="otel.instrumentation.http.server.capture-response-headers" %}} -A comma-separated list of HTTP header names. HTTP server instrumentations will -capture HTTP response header values for all configured header names. -{{% /config_option %}} - -These configuration options are supported by all HTTP client and server -instrumentations. - -> **Note**: The property/environment variable names listed in the table are -> still experimental, and thus are subject to change. - -#### Capturing servlet request parameters - -You can configure the agent to capture predefined HTTP request parameter as span -attributes for requests that are handled by Servlet API. Use the following -property to define which servlet request parameters you want to capture: - -{{% config_option name="otel.instrumentation.servlet.experimental.capture-request-parameters" %}} -A comma-separated list of request parameter names. {{% /config_option %}} - -> **Note**: The property/environment variable names listed in the table are -> still experimental, and thus are subject to change. - -#### Configuring known HTTP methods - -Configures the instrumentation to recognize an alternative set of HTTP request -methods. All other methods will be treated as `_OTHER`. - -{{% config_option -name="otel.instrumentation.http.known-methods" -default="CONNECT,DELETE,GET,HEAD,OPTIONS,PATCH,POST,PUT,TRACE" -%}} A comma-separated list of known HTTP methods. {{% /config_option %}} - -#### Enabling experimental HTTP telemetry - -You can configure the agent to capture additional experimental HTTP telemetry -data. - -{{% config_option -name="otel.instrumentation.http.client.emit-experimental-telemetry" -default=false -%}} Enables the experimental HTTP client telemetry. {{% /config_option %}} - -{{% config_option name="otel.instrumentation.http.server.emit-experimental-telemetry" -default=false -%}} -Enables the experimental HTTP server telemetry. {{% /config_option %}} +## SDK Configuration -For client and server spans, the following attributes are added: - -- `http.request.body.size` and `http.response.body.size`: The size of the - request and response bodies, respectively. - -For client metrics, the following metrics are created: - -- [http.client.request.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpclientrequestbodysize) -- [http.client.response.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpclientresponsebodysize) - -For server metrics, the following metrics are created: - -- [http.server.active_requests](/docs/specs/semconv/http/http-metrics/#metric-httpserveractive_requests) -- [http.server.request.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestbodysize) -- [http.server.response.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpserverresponsebodysize) - -### Capturing consumer message receive telemetry in messaging instrumentations - -You can configure the agent to capture the consumer message receive telemetry in -messaging instrumentation. Use the following property to enable it: - -{{% config_option -name="otel.instrumentation.messaging.experimental.receive-telemetry.enabled" -default=false -%}} Enables the consumer message receive telemetry. {{% /config_option %}} - -Note that this will cause the consumer side to start a new trace, with only a -span link connecting it to the producer trace. - -> **Note**: The property/environment variable names listed in the table are -> still experimental, and thus are subject to change. +The SDK's autoconfiguration module is used for basic configuration of the agent. +Read the [docs](/docs/languages/java/configuration) to find settings such as +configuring export or sampling. -### Capturing enduser attributes +{{% alert title="Important" color="warning" %}} -You can configure the agent to capture -[general identity attributes](/docs/specs/semconv/general/attributes/#general-identity-attributes) -(`enduser.id`, `enduser.role`, `enduser.scope`) from instrumentation libraries -like -[JavaEE/JakartaEE Servlet](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/servlet) -and -[Spring Security](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-security-config-6.0). +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`. -> **Note**: Given the sensitive nature of the data involved, this feature is -> turned off by default while allowing selective activation for particular -> attributes. You must carefully evaluate each attribute's privacy implications -> before enabling the collection of the data. +{{% /alert %}} -{{% config_option -name="otel.instrumentation.common.enduser.id.enabled" -default=false -%}} Determines whether to capture `enduser.id` semantic attribute. -{{% /config_option %}} +## Enable Resource Providers that are disabled by default -{{% config_option -name="otel.instrumentation.common.enduser.role.enabled" -default=false -%}} Determines whether to capture `enduser.role` semantic attribute. -{{% /config_option %}} +In addition to the resource configuration from the SDK autoconfiguration, you +can enable additional resource providers that are disabled by default: {{% config_option -name="otel.instrumentation.common.enduser.scope.enabled" +name="otel.resource.providers.aws.enabled" default=false -%}} Determines whether to capture `enduser.scope` semantic attribute. -{{% /config_option %}} - -#### Spring Security - -For users of Spring Security who use custom -[granted authority prefixes](https://docs.spring.io/spring-security/reference/servlet/authorization/architecture.html#authz-authorities), -you can use the following properties to strip those prefixes from the -`enduser.*` attribute values to better represent the actual role and scope -names: - -{{% config_option -name="otel.instrumentation.spring-security.enduser.role.granted-authority-prefix" -default=ROLE_ -%}} Prefix of granted authorities identifying roles to capture in the -`enduser.role` semantic attribute. {{% /config_option %}} - -{{% config_option -name="otel.instrumentation.spring-security.enduser.scope.granted-authority-prefix" -default=SCOPE_ -%}} Prefix of granted authorities identifying scopes to capture in the -`enduser.scopes` semantic attribute. {{% /config_option %}} - -## Suppressing specific instrumentation - -### Disabling the agent entirely - -{{% config_option name="otel.javaagent.enabled" %}} - -Set the value to `false` to disable the agent entirely. - +%}} Enables the +[AWS Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/aws-resources). {{% /config_option %}} -### Enable only specific instrumentation - -You can disable all default auto instrumentation and selectively re-enable -individual instrumentation. This may be desirable to reduce startup overhead or -to have more control of which instrumentation is applied. - -{{% config_option name="otel.instrumentation.common.default-enabled" %}} Set to -`false` to disable all instrumentation in the agent. {{% /config_option %}} - -{{% config_option name="otel.instrumentation.[name].enabled" %}} Set to `true` -to enable each desired instrumentation individually. {{% /config_option %}} - -> **Note**: Some instrumentation relies on other instrumentation to function -> properly. When selectively enabling instrumentation, be sure to enable the -> transitive dependencies too. Determining this dependency relationship is left -> as an exercise to the user. - -### Enable manual instrumentation only - -You can suppress all auto instrumentations but have support for manual -instrumentation with `@WithSpan` and normal API interactions by using -`-Dotel.instrumentation.common.default-enabled=false -Dotel.instrumentation.opentelemetry-api.enabled=true -Dotel.instrumentation.opentelemetry-instrumentation-annotations.enabled=true` - -### Suppressing specific agent instrumentation - -You can suppress agent instrumentation of specific libraries. - -{{% config_option name="otel.instrumentation.[name].enabled" %}} Set to `false` -to suppress agent instrumentation of specific libraries, where [name] is the -corresponding instrumentation name: {{% /config_option %}} - -| Library/Framework | Instrumentation name | -| ------------------------------------------------ | ------------------------------------------- | -| Additional methods tracing | `methods` | -| Additional tracing annotations | `external-annotations` | -| Akka Actor | `akka-actor` | -| Akka HTTP | `akka-http` | -| Apache Axis2 | `axis2` | -| Apache Camel | `camel` | -| Apache Cassandra | `cassandra` | -| Apache CXF | `cxf` | -| Apache DBCP | `apache-dbcp` | -| Apache Dubbo | `apache-dubbo` | -| Apache Geode | `geode` | -| Apache HttpAsyncClient | `apache-httpasyncclient` | -| Apache HttpClient | `apache-httpclient` | -| Apache Kafka | `kafka` | -| Apache MyFaces | `jsf-myfaces` | -| Apache Pekko Actor | `pekko-actor` | -| Apache Pekko HTTP | `pekko-http` | -| Apache Pulsar | `pulsar` | -| Apache RocketMQ | `rocketmq-client` | -| Apache Struts 2 | `struts` | -| Apache Tapestry | `tapestry` | -| Apache Tomcat | `tomcat` | -| Apache Wicket | `wicket` | -| Armeria | `armeria` | -| AsyncHttpClient (AHC) | `async-http-client` | -| AWS Lambda | `aws-lambda` | -| AWS SDK | `aws-sdk` | -| Azure SDK | `azure-core` | -| Couchbase | `couchbase` | -| C3P0 | `c3p0` | -| Dropwizard Views | `dropwizard-views` | -| Dropwizard Metrics | `dropwizard-metrics` | -| Eclipse Grizzly | `grizzly` | -| Eclipse Jersey | `jersey` | -| Eclipse Jetty | `jetty` | -| Eclipse Jetty HTTP Client | `jetty-httpclient` | -| Eclipse Metro | `metro` | -| Eclipse Mojarra | `jsf-mojarra` | -| Eclipse Vert.x HttpClient | `vertx-http-client` | -| Eclipse Vert.x Kafka Client | `vertx-kafka-client` | -| Eclipse Vert.x RxJava | `vertx-rx-java` | -| Eclipse Vert.x Web | `vertx-web` | -| Elasticsearch client | `elasticsearch-transport` | -| Elasticsearch REST client | `elasticsearch-rest` | -| Google Guava | `guava` | -| Google HTTP client | `google-http-client` | -| Google Web Toolkit | `gwt` | -| Grails | `grails` | -| GraphQL Java | `graphql-java` | -| GRPC | `grpc` | -| Hibernate | `hibernate` | -| HikariCP | `hikaricp` | -| Java HTTP Client | `java-http-client` | -| Java `HttpURLConnection` | `http-url-connection` | -| Java JDBC | `jdbc` | -| Java JDBC `DataSource` | `jdbc-datasource` | -| Java RMI | `rmi` | -| Java Runtime | `runtime-telemetry` | -| Java Servlet | `servlet` | -| java.util.concurrent | `executors` | -| java.util.logging | `java-util-logging` | -| JAX-RS (Client) | `jaxrs-client` | -| JAX-RS (Server) | `jaxrs` | -| JAX-WS | `jaxws` | -| JBoss Logging Appender | `jboss-logmanager-appender` | -| JBoss Logging MDC | `jboss-logmanager-mdc` | -| JMS | `jms` | -| Jodd HTTP | `jodd-http` | -| JSP | `jsp` | -| K8s Client | `kubernetes-client` | -| kotlinx.coroutines | `kotlinx-coroutines` | -| Log4j Appender | `log4j-appender` | -| Log4j MDC (1.x) | `log4j-mdc` | -| Log4j Context Data (2.x) | `log4j-context-data` | -| Logback Appender | `logback-appender` | -| Logback MDC | `logback-mdc` | -| Micrometer | `micrometer` | -| MongoDB | `mongo` | -| Netflix Hystrix | `hystrix` | -| Netty | `netty` | -| OkHttp | `okhttp` | -| OpenLiberty | `liberty` | -| OpenTelemetry Extension Annotations | `opentelemetry-extension-annotations` | -| OpenTelemetry Instrumentation Annotations | `opentelemetry-instrumentation-annotations` | -| OpenTelemetry API | `opentelemetry-api` | -| Oracle UCP | `oracle-ucp` | -| OSHI (Operating System and Hardware Information) | `oshi` | -| Play Framework | `play` | -| Play WS HTTP Client | `play-ws` | -| Quartz | `quartz` | -| R2DBC | `r2dbc` | -| RabbitMQ Client | `rabbitmq` | -| Ratpack | `ratpack` | -| ReactiveX RxJava | `rxjava` | -| Reactor | `reactor` | -| Reactor Netty | `reactor-netty` | -| Redis Jedis | `jedis` | -| Redis Lettuce | `lettuce` | -| Rediscala | `rediscala` | -| Redisson | `redisson` | -| Restlet | `restlet` | -| Scala ForkJoinPool | `scala-fork-join` | -| Spark Web Framework | `spark` | -| Spring Batch | `spring-batch` | -| Spring Core | `spring-core` | -| Spring Data | `spring-data` | -| Spring JMS | `spring-jms` | -| Spring Integration | `spring-integration` | -| Spring Kafka | `spring-kafka` | -| Spring RabbitMQ | `spring-rabbit` | -| Spring RMI | `spring-rmi` | -| Spring Scheduling | `spring-scheduling` | -| Spring Web | `spring-web` | -| Spring WebFlux | `spring-webflux` | -| Spring Web MVC | `spring-webmvc` | -| Spring Web Services | `spring-ws` | -| Spymemcached | `spymemcached` | -| Tomcat JDBC | `tomcat-jdbc` | -| Twilio SDK | `twilio` | -| Twitter Finatra | `finatra` | -| Undertow | `undertow` | -| Vaadin | `vaadin` | -| Vibur DBCP | `vibur-dbcp` | -| ZIO | `zio` | - -**Note:** When using environment variables, dashes (`-`) should be converted to -underscores (`_`). For example, to suppress traces from `akka-actor` library, -set `OTEL_INSTRUMENTATION_AKKA_ACTOR_ENABLED` to `false`. - -### Suppressing controller and/or view spans - -Some instrumentations (e.g. Spring Web MVC instrumentation) produce -[SpanKind.Internal](/docs/specs/otel/trace/api/#spankind) spans to capture the -controller and/or view execution. These spans can be suppressed using the -configuration settings below, without suppressing the entire instrumentation -which would also disable the instrumentation's capturing of `http.route` and -associated span name on the parent -[SpanKind.Server](/docs/specs/otel/trace/api/#spankind) span. - -{{% config_option -name="otel.instrumentation.common.experimental.controller-telemetry.enabled" -default=false -%}} Set to `true` to enable controller telemetry. {{% /config_option %}} - {{% config_option -name="otel.instrumentation.common.experimental.view-telemetry.enabled" +name="otel.resource.providers.gcp.enabled" default=false -%}} Set to `true` to enable view telemetry. {{% /config_option %}} - -### Instrumentation span suppression behavior - -Some libraries that this agent instruments in turn use lower-level libraries, -that are also instrumented. This would normally result in nested spans -containing duplicate telemetry data. For example: - -- Spans produced by the Reactor Netty HTTP client instrumentation would have - duplicate HTTP client spans produced by the Netty instrumentation; -- Dynamo DB spans produced by the AWS SDK instrumentation would have children - HTTP client spans produced by its internal HTTP client library (which is also - instrumented); -- Spans produced by the Tomcat instrumentation would have duplicate HTTP server - spans produced by the generic Servlet API instrumentation. - -The Java agent prevents these situations by detecting and suppressing nested -spans that duplicate telemetry data. The suppression behavior can be configured -using the following configuration option: - -{{% config_option name="otel.instrumentation.experimental.span-suppression-strategy" %}} - -The Java agent span suppression strategy. The following 3 strategies are -supported: - -- `semconv`: The agent will suppress duplicate semantic conventions. This is the - default behavior of the Java agent. -- `span-kind`: The agent will suppress spans with the same kind (except - `INTERNAL`). -- `none`: The agent will not suppress anything at all. **We do not recommend - using this option for anything other than debug purposes, as it generates lots - of duplicate telemetry data**. - +%}} Enables the +[GCP Resource Provider](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources). {{% /config_option %}} -For example, suppose we instrument a database client which internally uses the -Reactor Netty HTTP client; which in turn uses Netty. - -Using the default `semconv` suppression strategy would result in 2 nested -`CLIENT` spans: - -- `CLIENT` span with database client semantic attributes emitted by the database - client instrumentation; -- `CLIENT` span with HTTP client semantic attributes emitted by the Reactor - Netty instrumentation. - -The Netty instrumentation would be suppressed, as it duplicates the Reactor -Netty HTTP client instrumentation. - -Using the suppression strategy `span-kind` would result in just one span: - -- `CLIENT` span with database client semantic attributes emitted by the database - client instrumentation. - -Both Reactor Netty and Netty instrumentations would be suppressed, as they also -emit `CLIENT` spans. - -Finally, using the suppression strategy `none` would result in 3 spans: - -- `CLIENT` span with database client semantic attributes emitted by the database - client instrumentation; -- `CLIENT` span with HTTP client semantic attributes emitted by the Reactor - Netty instrumentation; -- `CLIENT` span with HTTP client semantic attributes emitted by the Netty - instrumentation. - [extensions]: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/examples/extension#readme diff --git a/content/en/docs/zero-code/java/agent/disable.md b/content/en/docs/zero-code/java/agent/disable.md new file mode 100644 index 000000000000..942a6e754193 --- /dev/null +++ b/content/en/docs/zero-code/java/agent/disable.md @@ -0,0 +1,261 @@ +--- +title: Suppressing specific instrumentation +linkTitle: Suppressing instrumentation +weight: 11 +# prettier-ignore +cSpell:ignore: akka armeria classloaders couchbase Customizer datasource dbcp Dotel dropwizard dubbo enduser finatra hikari hikaricp HSET httpasyncclient httpclient hystrix jaxrs jaxws jedis jodd kotlinx logback logmanager mojarra myfaces okhttp oshi pekko rabbitmq ratpack rediscala redisson restlet rocketmq serverlessapis spymemcached twilio vaadin vertx vibur webflux webmvc +--- + +## Disabling the agent entirely + +{{% config_option name="otel.javaagent.enabled" %}} + +Set the value to `false` to disable the agent entirely. + +{{% /config_option %}} + +## Enable only specific instrumentation + +You can disable all default auto instrumentation and selectively re-enable +individual instrumentation. This may be desirable to reduce startup overhead or +to have more control of which instrumentation is applied. + +{{% config_option name="otel.instrumentation.common.default-enabled" %}} Set to +`false` to disable all instrumentation in the agent. {{% /config_option %}} + +{{% config_option name="otel.instrumentation.[name].enabled" %}} Set to `true` +to enable each desired instrumentation individually. {{% /config_option %}} + +> **Note**: Some instrumentation relies on other instrumentation to function +> properly. When selectively enabling instrumentation, be sure to enable the +> transitive dependencies too. Determining this dependency relationship is left +> as an exercise to the user. + +## Enable manual instrumentation only + +You can suppress all auto instrumentations but have support for manual +instrumentation with `@WithSpan` and normal API interactions by using +`-Dotel.instrumentation.common.default-enabled=false -Dotel.instrumentation.opentelemetry-api.enabled=true -Dotel.instrumentation.opentelemetry-instrumentation-annotations.enabled=true` + +## Suppressing specific agent instrumentation + +You can suppress agent instrumentation of specific libraries. + +{{% config_option name="otel.instrumentation.[name].enabled" %}} Set to `false` +to suppress agent instrumentation of specific libraries, where [name] is the +corresponding instrumentation name: {{% /config_option %}} + +| Library/Framework | Instrumentation name | +| ------------------------------------------------ | ------------------------------------------- | +| Additional methods tracing | `methods` | +| Additional tracing annotations | `external-annotations` | +| Akka Actor | `akka-actor` | +| Akka HTTP | `akka-http` | +| Apache Axis2 | `axis2` | +| Apache Camel | `camel` | +| Apache Cassandra | `cassandra` | +| Apache CXF | `cxf` | +| Apache DBCP | `apache-dbcp` | +| Apache Dubbo | `apache-dubbo` | +| Apache Geode | `geode` | +| Apache HttpAsyncClient | `apache-httpasyncclient` | +| Apache HttpClient | `apache-httpclient` | +| Apache Kafka | `kafka` | +| Apache MyFaces | `jsf-myfaces` | +| Apache Pekko Actor | `pekko-actor` | +| Apache Pekko HTTP | `pekko-http` | +| Apache Pulsar | `pulsar` | +| Apache RocketMQ | `rocketmq-client` | +| Apache Struts 2 | `struts` | +| Apache Tapestry | `tapestry` | +| Apache Tomcat | `tomcat` | +| Apache Wicket | `wicket` | +| Armeria | `armeria` | +| AsyncHttpClient (AHC) | `async-http-client` | +| AWS Lambda | `aws-lambda` | +| AWS SDK | `aws-sdk` | +| Azure SDK | `azure-core` | +| Couchbase | `couchbase` | +| C3P0 | `c3p0` | +| Dropwizard Views | `dropwizard-views` | +| Dropwizard Metrics | `dropwizard-metrics` | +| Eclipse Grizzly | `grizzly` | +| Eclipse Jersey | `jersey` | +| Eclipse Jetty | `jetty` | +| Eclipse Jetty HTTP Client | `jetty-httpclient` | +| Eclipse Metro | `metro` | +| Eclipse Mojarra | `jsf-mojarra` | +| Eclipse Vert.x HttpClient | `vertx-http-client` | +| Eclipse Vert.x Kafka Client | `vertx-kafka-client` | +| Eclipse Vert.x RxJava | `vertx-rx-java` | +| Eclipse Vert.x Web | `vertx-web` | +| Elasticsearch client | `elasticsearch-transport` | +| Elasticsearch REST client | `elasticsearch-rest` | +| Google Guava | `guava` | +| Google HTTP client | `google-http-client` | +| Google Web Toolkit | `gwt` | +| Grails | `grails` | +| GraphQL Java | `graphql-java` | +| GRPC | `grpc` | +| Hibernate | `hibernate` | +| HikariCP | `hikaricp` | +| Java HTTP Client | `java-http-client` | +| Java `HttpURLConnection` | `http-url-connection` | +| Java JDBC | `jdbc` | +| Java JDBC `DataSource` | `jdbc-datasource` | +| Java RMI | `rmi` | +| Java Runtime | `runtime-telemetry` | +| Java Servlet | `servlet` | +| java.util.concurrent | `executors` | +| java.util.logging | `java-util-logging` | +| JAX-RS (Client) | `jaxrs-client` | +| JAX-RS (Server) | `jaxrs` | +| JAX-WS | `jaxws` | +| JBoss Logging Appender | `jboss-logmanager-appender` | +| JBoss Logging MDC | `jboss-logmanager-mdc` | +| JMS | `jms` | +| Jodd HTTP | `jodd-http` | +| JSP | `jsp` | +| K8s Client | `kubernetes-client` | +| kotlinx.coroutines | `kotlinx-coroutines` | +| Log4j Appender | `log4j-appender` | +| Log4j MDC (1.x) | `log4j-mdc` | +| Log4j Context Data (2.x) | `log4j-context-data` | +| Logback Appender | `logback-appender` | +| Logback MDC | `logback-mdc` | +| Micrometer | `micrometer` | +| MongoDB | `mongo` | +| Netflix Hystrix | `hystrix` | +| Netty | `netty` | +| OkHttp | `okhttp` | +| OpenLiberty | `liberty` | +| OpenTelemetry Extension Annotations | `opentelemetry-extension-annotations` | +| OpenTelemetry Instrumentation Annotations | `opentelemetry-instrumentation-annotations` | +| OpenTelemetry API | `opentelemetry-api` | +| Oracle UCP | `oracle-ucp` | +| OSHI (Operating System and Hardware Information) | `oshi` | +| Play Framework | `play` | +| Play WS HTTP Client | `play-ws` | +| Quartz | `quartz` | +| R2DBC | `r2dbc` | +| RabbitMQ Client | `rabbitmq` | +| Ratpack | `ratpack` | +| ReactiveX RxJava | `rxjava` | +| Reactor | `reactor` | +| Reactor Netty | `reactor-netty` | +| Redis Jedis | `jedis` | +| Redis Lettuce | `lettuce` | +| Rediscala | `rediscala` | +| Redisson | `redisson` | +| Restlet | `restlet` | +| Scala ForkJoinPool | `scala-fork-join` | +| Spark Web Framework | `spark` | +| Spring Batch | `spring-batch` | +| Spring Core | `spring-core` | +| Spring Data | `spring-data` | +| Spring JMS | `spring-jms` | +| Spring Integration | `spring-integration` | +| Spring Kafka | `spring-kafka` | +| Spring RabbitMQ | `spring-rabbit` | +| Spring RMI | `spring-rmi` | +| Spring Scheduling | `spring-scheduling` | +| Spring Web | `spring-web` | +| Spring WebFlux | `spring-webflux` | +| Spring Web MVC | `spring-webmvc` | +| Spring Web Services | `spring-ws` | +| Spymemcached | `spymemcached` | +| Tomcat JDBC | `tomcat-jdbc` | +| Twilio SDK | `twilio` | +| Twitter Finatra | `finatra` | +| Undertow | `undertow` | +| Vaadin | `vaadin` | +| Vibur DBCP | `vibur-dbcp` | +| ZIO | `zio` | + +**Note:** When using environment variables, dashes (`-`) should be converted to +underscores (`_`). For example, to suppress traces from `akka-actor` library, +set `OTEL_INSTRUMENTATION_AKKA_ACTOR_ENABLED` to `false`. + +## Suppressing controller and/or view spans + +Some instrumentations (e.g. Spring Web MVC instrumentation) produce +[SpanKind.Internal](/docs/specs/otel/trace/api/#spankind) spans to capture the +controller and/or view execution. These spans can be suppressed using the +configuration settings below, without suppressing the entire instrumentation +which would also disable the instrumentation's capturing of `http.route` and +associated span name on the parent +[SpanKind.Server](/docs/specs/otel/trace/api/#spankind) span. + +{{% config_option +name="otel.instrumentation.common.experimental.controller-telemetry.enabled" +default=false +%}} Set to `true` to enable controller telemetry. {{% /config_option %}} + +{{% config_option +name="otel.instrumentation.common.experimental.view-telemetry.enabled" +default=false +%}} Set to `true` to enable view telemetry. {{% /config_option %}} + +## Instrumentation span suppression behavior + +Some libraries that this agent instruments in turn use lower-level libraries, +that are also instrumented. This would normally result in nested spans +containing duplicate telemetry data. For example: + +- Spans produced by the Reactor Netty HTTP client instrumentation would have + duplicate HTTP client spans produced by the Netty instrumentation; +- Dynamo DB spans produced by the AWS SDK instrumentation would have children + HTTP client spans produced by its internal HTTP client library (which is also + instrumented); +- Spans produced by the Tomcat instrumentation would have duplicate HTTP server + spans produced by the generic Servlet API instrumentation. + +The Java agent prevents these situations by detecting and suppressing nested +spans that duplicate telemetry data. The suppression behavior can be configured +using the following configuration option: + +{{% config_option name="otel.instrumentation.experimental.span-suppression-strategy" %}} + +The Java agent span suppression strategy. The following 3 strategies are +supported: + +- `semconv`: The agent will suppress duplicate semantic conventions. This is the + default behavior of the Java agent. +- `span-kind`: The agent will suppress spans with the same kind (except + `INTERNAL`). +- `none`: The agent will not suppress anything at all. **We do not recommend + using this option for anything other than debug purposes, as it generates lots + of duplicate telemetry data**. + +{{% /config_option %}} + +For example, suppose we instrument a database client which internally uses the +Reactor Netty HTTP client; which in turn uses Netty. + +Using the default `semconv` suppression strategy would result in 2 nested +`CLIENT` spans: + +- `CLIENT` span with database client semantic attributes emitted by the database + client instrumentation; +- `CLIENT` span with HTTP client semantic attributes emitted by the Reactor + Netty instrumentation. + +The Netty instrumentation would be suppressed, as it duplicates the Reactor +Netty HTTP client instrumentation. + +Using the suppression strategy `span-kind` would result in just one span: + +- `CLIENT` span with database client semantic attributes emitted by the database + client instrumentation. + +Both Reactor Netty and Netty instrumentations would be suppressed, as they also +emit `CLIENT` spans. + +Finally, using the suppression strategy `none` would result in 3 spans: + +- `CLIENT` span with database client semantic attributes emitted by the database + client instrumentation; +- `CLIENT` span with HTTP client semantic attributes emitted by the Reactor + Netty instrumentation; +- `CLIENT` span with HTTP client semantic attributes emitted by the Netty + instrumentation. diff --git a/content/en/docs/zero-code/java/agent/extensions.md b/content/en/docs/zero-code/java/agent/extensions.md index 5f452550ffe9..036c96034941 100644 --- a/content/en/docs/zero-code/java/agent/extensions.md +++ b/content/en/docs/zero-code/java/agent/extensions.md @@ -4,7 +4,7 @@ aliases: [/docs/instrumentation/java/extensions] description: Extensions add capabilities to the agent without having to create a separate distribution. -weight: 30 +weight: 300 --- ## Introduction diff --git a/content/en/docs/zero-code/java/agent/getting-started.md b/content/en/docs/zero-code/java/agent/getting-started.md new file mode 100644 index 000000000000..9dbcc22b68bd --- /dev/null +++ b/content/en/docs/zero-code/java/agent/getting-started.md @@ -0,0 +1,99 @@ +--- +title: Getting started +weight: 1 +cSpell:ignore: Dotel myapp +--- + +## Setup + +1. Download [opentelemetry-javaagent.jar][] from [Releases][] of the + `opentelemetry-java-instrumentation` repository and place the JAR in your + preferred directory. The JAR file contains the agent and instrumentation + libraries. +2. Add `-javaagent:path/to/opentelemetry-javaagent.jar` and other config to + your JVM startup arguments and launch your app: + + - Directly on the startup command: + + ```shell + java -javaagent:path/to/opentelemetry-javaagent.jar -Dotel.service.name=your-service-name -jar myapp.jar + ``` + + - Via the `JAVA_TOOL_OPTIONS` and other environment variables: + + ```shell + export JAVA_TOOL_OPTIONS="-javaagent:path/to/opentelemetry-javaagent.jar" + export OTEL_SERVICE_NAME="your-service-name" + java -jar myapp.jar + ``` + +## Configuring the agent + +The agent is highly configurable. + +One option is to pass configuration properties via the `-D` flag. In this +example, a service name and Zipkin exporter for traces are configured: + +```sh +java -javaagent:path/to/opentelemetry-javaagent.jar \ + -Dotel.service.name=your-service-name \ + -Dotel.traces.exporter=zipkin \ + -jar myapp.jar +``` + +You can also use environment variables to configure the agent: + +```sh +OTEL_SERVICE_NAME=your-service-name \ +OTEL_TRACES_EXPORTER=zipkin \ +java -javaagent:path/to/opentelemetry-javaagent.jar \ + -jar myapp.jar +``` + +You can also supply a Java properties file and load configuration values from +there: + +```sh +java -javaagent:path/to/opentelemetry-javaagent.jar \ + -Dotel.javaagent.configuration-file=path/to/properties/file.properties \ + -jar myapp.jar +``` + +or + +```sh +OTEL_JAVAAGENT_CONFIGURATION_FILE=path/to/properties/file.properties \ +java -javaagent:path/to/opentelemetry-javaagent.jar \ + -jar myapp.jar +``` + +To see the full range of configuration options, see +[Agent Configuration](../configuration). + +## Supported libraries, frameworks, application services, and JVMs + +The Java agent ships with instrumentation libraries for many popular components. +For the full list, see [Supported libraries, frameworks, application services, +and JVMs][support]. + +## Troubleshooting + +{{% config_option name="otel.javaagent.debug" %}} + +Set to `true` to see debug logs. Note that these are quite verbose. + +{{% /config_option %}} + +## Next steps + +After you have automatic instrumentation configured for your app or service, you +might want to [annotate](../annotations) selected methods or add +[manual instrumentation](/docs/languages/java/instrumentation/) to collect +custom telemetry data. + +[opentelemetry-javaagent.jar]: + https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases/latest/download/opentelemetry-javaagent.jar +[releases]: + https://github.com/open-telemetry/opentelemetry-java-instrumentation/releases +[support]: + https://github.com/open-telemetry/opentelemetry-java-instrumentation/blob/main/docs/supported-libraries.md diff --git a/content/en/docs/zero-code/java/agent/instrumentation/_index.md b/content/en/docs/zero-code/java/agent/instrumentation/_index.md new file mode 100644 index 000000000000..d0fde2bb94a7 --- /dev/null +++ b/content/en/docs/zero-code/java/agent/instrumentation/_index.md @@ -0,0 +1,144 @@ +--- +title: Instrumentation configuration +linkTitle: Instrumentation config +weight: 100 +cSpell:ignore: enduser hset serverlessapis +--- + +This page describes common settings that apply to multiple instrumentations at +once. + +## Peer service name + +The +[peer service name](/docs/specs/semconv/general/attributes/#general-remote-service-attributes) +is the name of a remote service to which a connection is made. It corresponds to +`service.name` in the [resource](/docs/specs/semconv/resource/#service) for the +local service. + +{{% config_option name="otel.instrumentation.common.peer-service-mapping" %}} + +Used to specify a mapping from host names or IP addresses to peer services, as a +comma-separated list of `=` pairs. The peer +service is added as an attribute to a span whose host or IP address match the +mapping. + +For example, if set to the following: + +```text +1.2.3.4=cats-service,dogs-abcdef123.serverlessapis.com=dogs-api +``` + +Then, requests to `1.2.3.4` will have a `peer.service` attribute of +`cats-service` and requests to `dogs-abcdef123.serverlessapis.com` will have an +attribute of `dogs-api`. + +Since Java agent version `1.31.0`, it is possible to provide a port and a path +to define a `peer.service`. + +For example, if set to the following: + +```text +1.2.3.4:443=cats-service,dogs-abcdef123.serverlessapis.com:80/api=dogs-api +``` + +Then, requests to `1.2.3.4` will have no override for `peer.service` attribute, +while `1.2.3.4:443` will have have `peer.service` of `cats-service` and requests +to `dogs-abcdef123.serverlessapis.com:80/api/v1` will have an attribute of +`dogs-api`. + +{{% /config_option %}} + +## DB statement sanitization + +The agent sanitizes all database queries/statements before setting the +`db.statement` semantic attribute. All values (strings, numbers) in the query +string are replaced with a question mark (`?`). + +Note: JDBC bind parameters are not captured in `db.statement`. See +[the corresponding issue](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7413) +if you are looking to capture bind parameters. + +Examples: + +- SQL query `SELECT a from b where password="secret"` will appear as + `SELECT a from b where password=?` in the exported span; +- Redis command `HSET map password "secret"` will appear as + `HSET map password ?` in the exported span. + +This behavior is turned on by default for all database instrumentations. Use the +following property to disable it: + +{{% config_option +name="otel.instrumentation.common.db-statement-sanitizer.enabled" +default=true +%}} Enables the DB statement sanitization. {{% /config_option %}} + +## Capturing consumer message receive telemetry in messaging instrumentations + +You can configure the agent to capture the consumer message receive telemetry in +messaging instrumentation. Use the following property to enable it: + +{{% config_option +name="otel.instrumentation.messaging.experimental.receive-telemetry.enabled" +default=false +%}} Enables the consumer message receive telemetry. {{% /config_option %}} + +Note that this will cause the consumer side to start a new trace, with only a +span link connecting it to the producer trace. + +> **Note**: The property/environment variable names listed in the table are +> still experimental, and thus are subject to change. + +## Capturing enduser attributes + +You can configure the agent to capture +[general identity attributes](/docs/specs/semconv/general/attributes/#general-identity-attributes) +(`enduser.id`, `enduser.role`, `enduser.scope`) from instrumentation libraries +like +[JavaEE/JakartaEE Servlet](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/servlet) +and +[Spring Security](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-security-config-6.0). + +> **Note**: Given the sensitive nature of the data involved, this feature is +> turned off by default while allowing selective activation for particular +> attributes. You must carefully evaluate each attribute's privacy implications +> before enabling the collection of the data. + +{{% config_option +name="otel.instrumentation.common.enduser.id.enabled" +default=false +%}} Determines whether to capture `enduser.id` semantic attribute. +{{% /config_option %}} + +{{% config_option +name="otel.instrumentation.common.enduser.role.enabled" +default=false +%}} Determines whether to capture `enduser.role` semantic attribute. +{{% /config_option %}} + +{{% config_option +name="otel.instrumentation.common.enduser.scope.enabled" +default=false +%}} Determines whether to capture `enduser.scope` semantic attribute. +{{% /config_option %}} + +### Spring Security + +For users of Spring Security who use custom +[granted authority prefixes](https://docs.spring.io/spring-security/reference/servlet/authorization/architecture.html#authz-authorities), +you can use the following properties to strip those prefixes from the +`enduser.*` attribute values to better represent the actual role and scope +names: + +{{% config_option +name="otel.instrumentation.spring-security.enduser.role.granted-authority-prefix" +default=ROLE_ +%}} Prefix of granted authorities identifying roles to capture in the +`enduser.role` semantic attribute. {{% /config_option %}} + +{{% config_option +name="otel.instrumentation.spring-security.enduser.scope.granted-authority-prefix" +default=SCOPE_ +%}} Prefix of granted authorities identifying scopes to capture in the +`enduser.scopes` semantic attribute. {{% /config_option %}} diff --git a/content/en/docs/zero-code/java/agent/instrumentation/http.md b/content/en/docs/zero-code/java/agent/instrumentation/http.md new file mode 100644 index 000000000000..d8442a4f21bf --- /dev/null +++ b/content/en/docs/zero-code/java/agent/instrumentation/http.md @@ -0,0 +1,91 @@ +--- +title: HTTP instrumentation configuration +linkTitle: HTTP +weight: 110 +--- + +## Capturing HTTP request and response headers + +You can configure the agent to capture predefined HTTP headers as span +attributes, according to the +[semantic convention](/docs/specs/semconv/http/http-spans/). Use the following +properties to define which HTTP headers you want to capture: + +{{% config_option name="otel.instrumentation.http.client.capture-request-headers" %}} +A comma-separated list of HTTP header names. HTTP client instrumentations will +capture HTTP request header values for all configured header names. +{{% /config_option %}} + +{{% config_option name="otel.instrumentation.http.client.capture-response-headers" %}} +A comma-separated list of HTTP header names. HTTP client instrumentations will +capture HTTP response header values for all configured header names. +{{% /config_option %}} + +{{% config_option name="otel.instrumentation.http.server.capture-request-headers" %}} +A comma-separated list of HTTP header names. HTTP server instrumentations will +capture HTTP request header values for all configured header names. +{{% /config_option %}} + +{{% config_option name="otel.instrumentation.http.server.capture-response-headers" %}} +A comma-separated list of HTTP header names. HTTP server instrumentations will +capture HTTP response header values for all configured header names. +{{% /config_option %}} + +These configuration options are supported by all HTTP client and server +instrumentations. + +> **Note**: The property/environment variable names listed in the table are +> still experimental, and thus are subject to change. + +## Capturing servlet request parameters + +You can configure the agent to capture predefined HTTP request parameter as span +attributes for requests that are handled by Servlet API. Use the following +property to define which servlet request parameters you want to capture: + +{{% config_option name="otel.instrumentation.servlet.experimental.capture-request-parameters" %}} +A comma-separated list of request parameter names. {{% /config_option %}} + +> **Note**: The property/environment variable names listed in the table are +> still experimental, and thus are subject to change. + +## Configuring known HTTP methods + +Configures the instrumentation to recognize an alternative set of HTTP request +methods. All other methods will be treated as `_OTHER`. + +{{% config_option +name="otel.instrumentation.http.known-methods" +default="CONNECT,DELETE,GET,HEAD,OPTIONS,PATCH,POST,PUT,TRACE" +%}} A comma-separated list of known HTTP methods. {{% /config_option %}} + +## Enabling experimental HTTP telemetry + +You can configure the agent to capture additional experimental HTTP telemetry +data. + +{{% config_option +name="otel.instrumentation.http.client.emit-experimental-telemetry" +default=false +%}} Enables the experimental HTTP client telemetry. {{% /config_option %}} + +{{% config_option name="otel.instrumentation.http.server.emit-experimental-telemetry" +default=false +%}} +Enables the experimental HTTP server telemetry. {{% /config_option %}} + +For client and server spans, the following attributes are added: + +- `http.request.body.size` and `http.response.body.size`: The size of the + request and response bodies, respectively. + +For client metrics, the following metrics are created: + +- [http.client.request.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpclientrequestbodysize) +- [http.client.response.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpclientresponsebodysize) + +For server metrics, the following metrics are created: + +- [http.server.active_requests](/docs/specs/semconv/http/http-metrics/#metric-httpserveractive_requests) +- [http.server.request.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpserverrequestbodysize) +- [http.server.response.body.size](/docs/specs/semconv/http/http-metrics/#metric-httpserverresponsebodysize) diff --git a/content/en/docs/zero-code/java/agent/server-config.md b/content/en/docs/zero-code/java/agent/server-config.md index 5f207f8f5638..2e3a698f0937 100644 --- a/content/en/docs/zero-code/java/agent/server-config.md +++ b/content/en/docs/zero-code/java/agent/server-config.md @@ -2,7 +2,7 @@ title: Application server configuration linkTitle: App server config description: Learn how to define agent paths for Java application servers -weight: 15 +weight: 215 cSpell:ignore: asadmin binsetenv binstart Glassfish Payara setenv --- diff --git a/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md b/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md index 18520fb770f4..19aec24686e0 100644 --- a/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md +++ b/content/en/docs/zero-code/java/spring-boot-starter/getting-started.md @@ -25,14 +25,19 @@ A Bill of Material ([BOM](https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms)) ensures that versions of dependencies (including transitive ones) are aligned. -Importing the `opentelemetry-bom` and `opentelemetry-instrumentation-bom-alpha` -BOMs when using the OpenTelemetry starter is important to ensure version -alignment across all OpenTelemetry dependencies. +To ensure version alignment across all OpenTelemetry dependencies, you must +import the `opentelemetry-instrumentation-bom` BOM when using the OpenTelemetry +starter. {{% alert title="Note" color="info" %}} -If you import the `spring-boot-dependencies` BOM, you have to declare it after -the OpenTelemetry BOMs. +When using Maven, import the OpenTelemetry BOMs before any other BOMs in your +project. For example, if you import the `spring-boot-dependencies` BOM, you have +to declare it after the OpenTelemetry BOMs. + +Gradle selects the +[latest version](https://docs.gradle.org/current/userguide/dependency_resolution.html#sec:version-conflict) +of a dependency when multiple BOMs, so the order of BOMs is not important. {{% /alert %}} @@ -41,17 +46,10 @@ The following example shows how to import the OpenTelemetry BOMs using Maven: ```xml - - io.opentelemetry - opentelemetry-bom - {{% param vers.otel %}} - pom - import - io.opentelemetry.instrumentation - opentelemetry-instrumentation-bom-alpha - {{% param vers.instrumentation %}}-alpha + opentelemetry-instrumentation-bom + {{% param vers.instrumentation %}} pom import @@ -73,8 +71,7 @@ plugins { dependencies { implementation(platform(SpringBootPlugin.BOM_COORDINATES)) - implementation(platform("io.opentelemetry:opentelemetry-bom:{{% param vers.otel %}}")) - implementation(platform("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:{{% param vers.instrumentation %}}-alpha")) + implementation(platform("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom:{{% param vers.instrumentation %}}")) } ``` @@ -90,8 +87,7 @@ plugins { dependencyManagement { imports { - mavenBom("io.opentelemetry:opentelemetry-bom:{{% param vers.otel %}}") - mavenBom("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom-alpha:{{% param vers.instrumentation %}}-alpha") + mavenBom("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom:{{% param vers.instrumentation %}}") } } ``` @@ -100,7 +96,7 @@ dependencyManagement { Be careful not to mix up the different ways of configuring things with Gradle. For example, don't use -`implementation(platform("io.opentelemetry:opentelemetry-bom:{{% param vers.otel %}}"))` +`implementation(platform("io.opentelemetry.instrumentation:opentelemetry-instrumentation-bom:{{% param vers.instrumentation %}}"))` with the `io.spring.dependency-management` plugin. {{% /alert %}} diff --git a/content/en/docs/zero-code/java/spring-boot-starter/other-spring-autoconfig.md b/content/en/docs/zero-code/java/spring-boot-starter/other-spring-autoconfig.md index ed2676c4b95b..012e9c060fb6 100644 --- a/content/en/docs/zero-code/java/spring-boot-starter/other-spring-autoconfig.md +++ b/content/en/docs/zero-code/java/spring-boot-starter/other-spring-autoconfig.md @@ -5,22 +5,7 @@ weight: 70 --- Instead of using the OpenTelemetry Spring starter, you can use the OpenTelemetry -autoconfiguration features with an annotation or the Zipkin starter. - -## Spring support - -Autoconfiguration is natively supported by Spring Boot applications. To enable -these features in "vanilla" use `@EnableOpenTelemetry` to complete a component -scan of this package. - -```java -import io.opentelemetry.instrumentation.spring.autoconfigure.EnableOpenTelemetry; -import org.springframework.context.annotation.Configuration; - -@Configuration -@EnableOpenTelemetry -public class OpenTelemetryConfig {} -``` +Zipkin starter. ## Zipkin starter diff --git a/content/en/docs/zero-code/java/spring-boot-starter/out-of-the-box-instrumentation.md b/content/en/docs/zero-code/java/spring-boot-starter/out-of-the-box-instrumentation.md index 1c560731ba60..e0aa2330fe81 100644 --- a/content/en/docs/zero-code/java/spring-boot-starter/out-of-the-box-instrumentation.md +++ b/content/en/docs/zero-code/java/spring-boot-starter/out-of-the-box-instrumentation.md @@ -18,6 +18,15 @@ Out of the box instrumentation is available for several frameworks: | Micrometer | `otel.instrumentation.micrometer.enabled` | false | | R2DBC (reactive JDBC) | `otel.instrumentation.r2dbc.enabled` | true | +## Turn on instrumentations selectively + +To use only specific instrumentations, turn off all the instrumentations first +by setting the `otel.instrumentation.common.default-enabled` property to +`false`. Then, turn on instrumentations one by one. + +For example, if you want to only enable the JDBC instrumentation, set +`otel.instrumentation.jdbc.enabled` to `true`. + ## Common instrumentation configuration Common properties for all database instrumentations: @@ -118,6 +127,13 @@ public MyService(RestClient.Builder restClientBuilder) { } ``` +As it's possible with the Java agent, you can configure the capture of the +following entities: + +- [HTTP request and response headers](/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers) +- [Known HTTP methods](/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods) +- [Experimental HTTP telemetry](/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry) + ## Spring Web MVC Autoconfiguration This feature autoconfigures instrumentation for Spring WebMVC controllers by @@ -129,6 +145,13 @@ request. To learn more about the OpenTelemetry Spring WebMVC instrumentation, see the [opentelemetry-spring-webmvc-5.3 instrumentation library](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/spring/spring-webmvc/spring-webmvc-5.3/library). +As it's possible with the Java agent, you can configure the capture of the +following entities: + +- [HTTP request and response headers](/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers) +- [Known HTTP methods](/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods) +- [Experimental HTTP telemetry](/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry) + ## Spring WebFlux Autoconfiguration Provides autoconfigurations for the OpenTelemetry WebClient ExchangeFilter diff --git a/content/en/docs/zero-code/java/spring-boot-starter/sdk-configuration.md b/content/en/docs/zero-code/java/spring-boot-starter/sdk-configuration.md index d9be4f4a5a73..c226c55dd0c3 100644 --- a/content/en/docs/zero-code/java/spring-boot-starter/sdk-configuration.md +++ b/content/en/docs/zero-code/java/spring-boot-starter/sdk-configuration.md @@ -12,7 +12,7 @@ IDE. ## General configuration The OpenTelemetry Starter supports all the -[SDK Autoconfiguration](/docs/zero-code/java/agent/configuration/#sdk-autoconfiguration) +[SDK Autoconfiguration](/docs/zero-code/java/agent/configuration/#sdk-configuration) (since 2.2.0). You can update the configuration with properties in the `application.properties` diff --git a/content/ja/docs/collector/_index.md b/content/ja/docs/collector/_index.md new file mode 100644 index 000000000000..30ad57b1193a --- /dev/null +++ b/content/ja/docs/collector/_index.md @@ -0,0 +1,54 @@ +--- +title: コレクター +description: テレメトリーデータを受信、処理、エクスポートするためのベンダー非依存な方法 +cascade: + vers: 0.104.0 +weight: 270 +default_lang_commit: 0879929 +--- + +![Jaeger、OTLP、Prometheusを統合したOpenTelemetryコレクターのダイアグラム](img/otel-collector.svg) + +## はじめに + +OpenTelemetryコレクターは、テレメトリーデータの受信、処理、エクスポート方法について、ベンダーにとらわれない実装を提供します。 +複数のエージェント／コレクターの実行、操作、メンテナンスの必要性を取り除きます。 +これはスケーラビリティを向上させ、1つ以上のオープンソースまたは商用バックエンドに送信するオープンソースのオブザーバビリティデータフォーマット（Jaeger、Prometheus、Fluent Bitなど）をサポートします。 +ローカルのコレクターエージェントは、計装ライブラリがテレメトリーデータをエクスポートするデフォルトの場所です。 + +## 目的 + +- _利便性_: 合理的なデフォルト設定、一般的なプロトコルのサポート、ダウンロードしてすぐの実行と収集が可能 +- _パフォーマンス_: さまざまな負荷や構成の下でも高い安定性とパフォーマンスを発揮 +- _オブザーバビリティ_: オブザーバビリティがあるサービスの模範例 +- _拡張性_: コアコードに触れることなくカスタマイズ可能 +- _統一性_: 単一のコードベース、エージェントまたはコレクターとしてデプロイ可能、トレース、メトリクス、ログをサポート + +## コレクターを使う場面 + +ほとんどの言語固有の計装ライブラリには、一般的なバックエンドやOTLP用のエクスポーターがあります。 +ですので、あなたは次のように不思議に思うかもしれません。 + +> 各サービスがバックエンドに直接データを送信するのではなく、どのような状況でコレクターを使ってデータを送信するのだろう + +OpenTelemetryを試したり始めたりするには、バックエンドに直接データを送ることは、素早く価値を得るための素晴らしい方法です。 +また、開発環境や小規模な環境では、コレクターなしでも十分な結果を得られます。 + +しかし、一般的には、サービスとともにコレクターを使用することをおすすめします。理由は、サービスが素早くコレクターにデータをオフロードして、コレクターが再試行、バッチ処理、暗号化、機密データのフィルタリングなどの追加処理を行えるからです。 + +[コレクターのセットアップ](quick-start)も、思っているより簡単です。 +各言語のデフォルトのOTLPエクスポーターは、ローカルコレクターのエンドポイントを想定しているので、コレクターを起動すると、自動的にテレメトリーの受信を開始します。 + +## ステータスとリリース + +**コレクター**のステータスは、コレクターのコアコンポーネントが現在、[安定性レベル][stability levels]がまちまちであるため、 [混合状態（mixed）][mixed] となっています。 + +**コレクターコンポーネント** は成熟度が異なります。 +各コンポーネントの安定性は `README.md` で明記されています。 +利用可能なコレクターコンポーネントの一覧は、[レジストリ][registry] にあります。 + +{{% docs/latest-release collector-releases /%}} + +[registry]: /ecosystem/registry/?language=collector +[mixed]: /docs/specs/otel/document-status/#mixed +[stability levels]: https://github.com/open-telemetry/opentelemetry-collector#stability-levels diff --git a/content/ja/docs/concepts/instrumentation/_index.md b/content/ja/docs/concepts/instrumentation/_index.md new file mode 100644 index 000000000000..996fda38b25c --- /dev/null +++ b/content/ja/docs/concepts/instrumentation/_index.md @@ -0,0 +1,35 @@ +--- +title: 計装 +description: OpenTelemetryはどのように計装を促進するか +weight: 15 +default_lang_commit: d8c5612 +--- + +システムを観測可能にするためには、システムが **計装** されなければなりません。 +つまり、システムコンポーネントのコードが[トレース](/docs/concepts/signals/traces/)、[メトリクス](/docs/concepts/signals/metrics/)、[ログ](/docs/concepts/signals/logs/)といったテレメトリーシグナルを送出しなければなりません。 + +OpenTelemetry を使えば、主に2つの方法でコードを計装できます。 + +1. 公式の[各言語向けのAPIとSDK](/docs/languages/)を使った[コードベースソリューション](/docs/concepts/instrumentation/code-based) +2. [ゼロコードソリューション](/docs/concepts/instrumentation/zero-code/) + +**コードベース** ソリューションは、より深い洞察とリッチなテレメトリーをアプリケーション自身から得ることを可能にします。 +OpenTelemetry APIを使ってアプリケーションからテレメトリーを生成でき、ゼロコードソリューションによって生成されたテレメトリーを補完する重要な役割を果たします。 + +**ゼロコード** ソリューションは、テレメトリーの取得を初めて行うときや、テレメトリーを取得する必要のあるアプリケーションを修正できない時に最適です。 +それらは、あなたが使用しているライブラリや、アプリケーションが動作している環境から、豊富なテレメトリーを提供します。 +別の考え方をすれば、アプリケーションの _エッジで_ 何が起こっているかについての情報を提供する、ということです。 + +両方のソリューションを同時に使うこともできます。 + +## OpenTelemetryのその他の利点 {#additional-opentelemetry-benefits} + +OpenTelemetryが提供するのは、ゼロコードやコードベースのテレメトリーソリューションだけではありません。 +以下のものもOpenTelemetryの一部です。 + +- ライブラリは依存関係として OpenTelemetry API を活用することができ、OpenTelemetry SDK がインポートされない限り、そのライブラリを使用するアプリケーションに影響はありません。 +- それぞれの[シグナル](/docs/concepts/signals)(トレース、メトリクス、ログ)に対して、それらを作成、処理、エクスポートするためのいくつかの方法が用意されています。 +- [コンテキスト伝播](/docs/concepts/context-propagation)が実装に組み込まれているので、シグナルがどこで生成されたかに関係なく、シグナルを相関させられます。 +- [リソース](/docs/concepts/resources)と[計装スコープ](/docs/concepts/instrumentation-scope)は、[ホスト](/docs/specs/semconv/resource/host/)、[オペレーティングシステム](/docs/specs/semconv/resource/os/)、[Kubernetesクラスター](/docs/specs/semconv/resource/k8s/#cluster)のように、異なるエンティティごとにシグナルをグループ化できます。 +- APIとSDKの各言語固有の実装は、[OpenTelemetry仕様](/docs/specs/otel/)の要件と期待に従います。 +- [セマンティック規約](/docs/concepts/semantic-conventions)は、コードベースやプラットフォーム間で標準化のために使用できる共通の命名スキーマを提供します。 diff --git a/content/ja/docs/concepts/instrumentation/code-based.md b/content/ja/docs/concepts/instrumentation/code-based.md new file mode 100644 index 000000000000..a79ffdbb3485 --- /dev/null +++ b/content/ja/docs/concepts/instrumentation/code-based.md @@ -0,0 +1,49 @@ +--- +title: コードベース +description: コードベース計装のセットアップに不可欠なステップを学ぶ +weight: 20 +cSpell:ignore: proxying +default_lang_commit: d8c5612 +--- + +## OpenTelemetry APIとSDKをインポートする {#import-the-opentelemetry-api-and-sdk} + +まず、あなたのサービスコードに OpenTelemetry をインポートする必要があります。 +もし、実行可能なバイナリによって消費されることを意図したライブラリやその他のコンポーネントを開発しているのであれば、APIにだけ依存することになるでしょう。 +アーティファクトがスタンドアロンのプロセスやサービスであれば、APIとSDKに依存することになります。 +OpenTelemetry APIとSDKの詳細については、[仕様](/docs/specs/otel/)を参照してください。 + +## OpenTelemetry API を設定する {#configure-the-opentelemetry-api} + +トレースやメトリクスを作成するには、まずトレーサーやメーターのプロバイダーを作成する必要があります。 +一般的に、SDKはこれらのオブジェクトに対して単一のデフォルトプロバイダーを提供することを推奨します。 +次に、そのプロバイダーからトレーサーまたはメーターのインスタンスを取得し、名前とバージョンを与えます。 +たとえばライブラリを書いているのであれば、ライブラリの名前（たとえば `com.example.myLibrary`）を付けるべきです。 +また、ライブラリやサービスの現在のバージョンに対応するバージョン文字列（例：`semver:1.0.0`）を指定することを推奨します。 + +## OpenTelemetry SDK を設定する {#configure-the-opentelemetry-sdk} + +サービスプロセスを構築している場合、テレメトリーデータを解析バックエンドにエクスポートするための適切なオプションをSDKに設定する必要もあります。 +この設定は、設定ファイルまたはその他のメカニズムを通じてプログラムで処理することを推奨します。 +また、場合によっては使いたくなるであろう、言語ごとのチューニングオプションもあります。 + +## テレメトリーデータの作成 {#create-telemetry-data} + +APIとSDKを設定したら、プロバイダーから取得したトレーサーオブジェクトとメーターオブジェクトを通して、トレースとメトリックイベントを自由に作成できるようになります。 +依存関係のために計装ライブラリを利用しましょう。これらの詳細については、[レジストリ](/ecosystem/registry/) やあなたの言語のレポジトリをチェックしてください。 + +## データのエクスポート {#export-data} + +テレメトリーデータを作成したら、それをどこかに送信したいでしょう。 +OpenTelemetryは、プロセスから分析バックエンドにデータをエクスポートする2つの主要な方法をサポートしています。 +プロセスから直接エクスポートするか、[OpenTelemetryコレクター](/docs/collector)を通してプロキシする方法です。 + +プロセス内からのエクスポートでは、1つ以上の _エクスポーター_ をインポートして依存する必要があります。 +エクスポーターとは、OpenTelemetry のメモリ内のスパンやメトリクスオブジェクトを、JaegerやPrometheusのようなテレメトリー分析ツールに適したフォーマットに変換するライブラリです。 +さらに、OpenTelemetry は `OTLP` として知られるワイヤプロトコルをサポートしていて、これはすべての OpenTelemetry SDK でサポートされています。 +このプロトコルは、OpenTelemetryコレクターにデータを送るために使用できます。 +OpenTelemetryコレクターはスタンドアローンのバイナリプロセスで、サービスインスタンスのプロキシやサイドカーとして実行したり、別のホストで実行したりできます。 +コレクターは、このデータを転送し、好きな分析ツールにエクスポートするように設定できます。 + +JaegerやPrometheusのようなオープンソースツールに加えて、OpenTelemetryからのテレメトリデータの取り込みをサポートする企業のリストが増えています。 +詳細は、[ベンダー](/ecosystem/vendors/)のページを参照してください。 diff --git a/content/ja/docs/concepts/instrumentation/libraries.md b/content/ja/docs/concepts/instrumentation/libraries.md new file mode 100644 index 000000000000..e7c89111f324 --- /dev/null +++ b/content/ja/docs/concepts/instrumentation/libraries.md @@ -0,0 +1,354 @@ +--- +title: ライブラリ +description: ライブラリにネイティブ計装を追加する方法を紹介します。 +weight: 40 +default_lang_commit: d8c5612 +--- + +OpenTelemetryは、多くのライブラリに[計装ライブラリ][instrumentation libraries]を提供していて、これは通常、ライブラリフックやモンキーパッチライブラリコードを通して行われます。 + +OpenTelemetry を使ったネイティブのライブラリ計装は、ユーザにより良いオブザーバビリティと開発者体験を提供し、ライブラリがフックを公開して、ドキュメントを書く必要性を取り除きます。 + +- カスタムロギングフックは、一般的で使いやすいOpenTelemetry APIに置き換えられ、ユーザーはOpenTelemetryとだけやり取りすることになります。 +- ライブラリとアプリケーションコードからのトレース、ログ、メトリクスを相関させ、一貫性を持たせられます。 +- 共通規約により、ユーザーは同じ技術内、ライブラリや言語間で類似した一貫性のあるテレメトリーを得られます。 +- テレメトリーシグナルは、さまざまな消費シナリオのために、十分にドキュメントが用意された多種多様なOpenTelemetry拡張ポイントを使用して、微調整（フィルター、処理、集約）できます。 + +## セマンティック規約 {#semantic-conventions} + +ウェブフレームワーク、RPCクライアント、データベース、メッセージングクライアント、インフラなどをカバーする利用可能な[セマンティック規約](/docs/specs/semconv/general/trace/)をチェックしてください！ + +もしあなたのライブラリがそのようなものであるなら、規約にしたがってください。 +規約は主要な情報源であり、どの情報がスパンに含まれるべきかを教えてくれます。 +規約は、計装に一貫性を持たせます。テレメトリーに携わるユーザーは、ライブラリの仕様を学ぶ必要がありませんし、オブザーバビリティベンダーは、さまざまなテクノロジー（たとえば、データベースやメッセージングシステム）に対応した体験を構築できます。 +ライブラリが規約にしたがえば、ユーザーの入力や設定なしで、多くのシナリオがそのまま有効になります。 + +セマンティック規約は常に進化しており、常に新しいものが追加されています。 +もしあなたのライブラリにないものがあれば、[追加する](https://github.com/open-telemetry/semantic-conventions/issues)ことを検討してください。 +スパン名には特に注意してください。 +意味のある名前を使うように努め、定義する際にはカーディナリティを考慮してください。 + +[`schema_url`]（/docs/specs/otel/schemas/#schema-url）属性があり、どのバージョンのセマンティック規約が使用されているかを記録できます。 +可能であれば、この属性を設定してください。 + +何かフィードバックがあったり、新しい規約を追加したい場合は、ぜひ貢献してください！ +CNCFのOpenTelemetryに関する[計装チャンネル（ `#otel-instrumentation` ）](https://cloud-native.slack.com/archives/C01QZFGMLQ7)や[仕様のレポジトリ](https://github.com/open-telemetry/opentelemetry-specification)から始めるとよいでしょう！ + +### スパンの定義 {#defining-spans} + +ライブラリの利用者の視点からライブラリのことを考え、利用者がライブラリの動作やアクティビティについて何を知りたいと思うかを考えてみてください。 +ライブラリのメンテナーであるあなたは内部構造を知っていますが、ユーザーはライブラリの内部構造にはあまり興味を持たず、自分のアプリケーションの機能に興味を持つでしょう。 +ライブラリの使用状況を分析する上でどのような情報が役に立つかを考え、そのデータをモデル化する適切な方法を考えましょう。 +考慮すべき点は以下の通りです。 + +- スパンとスパンの階層 +- スパンの数値属性（集約されたメトリクスの代替として） +- スパンイベント +- 集約された指標 + +たとえば、ライブラリがデータベースへのリクエストを行っている場合、データベースへの論理的なリクエストに対してのみスパンを作成します。 +ネットワークを介した物理的なリクエストは、その機能を実装するライブラリ内で計装する必要があります。 +また、オブジェクトやデータのシリアライズのような他のアクティビティは、追加スパンとしてではなく、スパンイベントとして捕捉することをおすすめします。 + +スパン属性を設定するときは、セマンティック規約にしたがってください。 + +## 計装すべき**でない**とき {#when-not-to-instrument} + +いくつかのライブラリは、ネットワーク呼び出しをラップするシンクライアントです。 +OpenTelemetryに、RPCクライアント用の計装ライブラリがある可能性があります（[レジストリ](/ecosystem/registry/)をチェックしてください）。 +この場合、ラッパーライブラリの計装は必要ないかもしれません。 +一般的なガイドラインとして、ライブラリの計装は、そのライブラリ自身のレベルでのみ行ってください。 + +次のような場合は計装しないでください。 + +- あなたのライブラリは、ドキュメント化された、あるいは自明なAPIの上にある薄いプロキシです +- _そして_ OpenTelemetryのエコシステムに、土台となるネットワーク呼び出しの計装があります +- _そして_ テレメトリーを充実させるために、ライブラリがしたがうべき規約がありません + +迷ったら、計装はやめましょう。後で必要性を感じたときにいつでもできます。 + +もし、計装しないことを選択した場合でも、内部のRPCクライアントインスタンスに OpenTelemetryハンドラーを設定する方法を提供することは有用でしょう。 +これは、完全な自動計装をサポートしていない言語では必須ですが、その他の言語でも有用です。 + +この文書の残りの部分では、計装を行うことを決定した場合、何をどのように計装するのかについて手引きを示します。 + +## OpenTelemetry API {#opentelemetry-api} + +最初のステップは、OpenTelemetry APIパッケージへ依存することです。 + +OpenTelemetryには[2つの主要なモジュール](/docs/specs/otel/overview/)であるAPIとSDKがあります。 +OpenTelemetry API は、抽象化と動作しない実装のセットです。 +アプリケーションが OpenTelemetry SDKをインポートしない限り、あなたの計装は何もせず、アプリケーションのパフォーマンスに影響を与えません。 + +**ライブラリはOpenTelemetry APIのみを使用すべきです。** + +新しい依存関係を追加することを心配するのは当然かもしれませんが、依存地獄を最小限に抑える方法を決めるのに役立ついくつかの考慮事項を紹介しましょう。 + +- OpenTelemetry Trace APIは2021年初めに安定版に達しました。このAPIは[Semantic Versioning 2.0](/docs/specs/otel/versioning-and-stability/)にしがたっていて、開発チームはAPIの安定性を真剣に受け止めています。 +- 依存する場合は、もっとも早い安定版の OpenTelemetry API (1.0.\*)を使用し、新機能を使用する必要がない限り、アップデートは避けてください。 +- あなたの計装が安定するまでの間、それを別のパッケージとしてリリースすることを検討してください。 + あなたのレポジトリに置いておくこともできますし、[OpenTelemetryに追加](https://github.com/open-telemetry/oteps/blob/main/text/0155-external-modules.md#contrib-components) して、他の計装パッケージと一緒にリリースすることもできます。 +- セマンティック規約は[安定していますが、徐々に発展しています][stable, but subject to evolution]。 + 機能的な問題は発生しませんが、ときどき、計装をアップデートする必要があるかもしれません。 + プレビュープラグインか、OpenTelemetry contrib リポジトリにそれを置くことで、ユーザの変更を壊すことなく、規約を最新に保つことができるかもしれません。 + + [stable, but subject to evolution]: /docs/specs/otel/versioning-and-stability/#semantic-conventions-stability + +### トレーサーを取得する {#getting-a-tracer} + +すべてのアプリケーションの設定は、Tracer API を通してライブラリから隠蔽されます。 +ライブラリは、アプリケーションに `TracerProvider` のインスタンスを渡して依存性注入とテストの容易さを促進したり、[グローバルの `TracerProvider`](/docs/specs/otel/trace/api/#get-a-tracer) から取得したりできます。 +OpenTelemetry 言語の実装は、インスタンスの受け渡しやグローバルへのアクセスについて、慣用的なものに基づいて好みが異なるかもしれません。 + +トレーサーを入手する際、ライブラリ（またはトレーシングプラグイン）の名前とバージョンを指定してください。 +これらはテレメトリーに表示され、ユーザーがテレメトリーを処理してフィルタリングし、それがどこから来たのかを理解し、計装の問題をデバッグ／報告するのに役立ちます。 + +## 何を計装すべきか {#what-to-instrument} + +### パブリックAPI {#public-apis} + +パブリックAPI呼び出し用に作成されたスパンによって、ユーザーはテレメトリーをアプリケーションコードにマッピングし、ライブラリ呼び出しの期間と結果を理解できます。 +トレースすべき呼び出しは次のとおりです。 + +- 内部でネットワークコールを行うパブリックメソッドや、時間がかかり失敗する可能性のあるローカル操作（IOなど） +- リクエストやメッセージを処理するハンドラー + +**計装の例：** + +```java +private static Tracer tracer = getTracer(TracerProvider.noop()); + +public static void setTracerProvider(TracerProvider tracerProvider) { + tracer = getTracer(tracerProvider); +} + +private static Tracer getTracer(TracerProvider tracerProvider) { + return tracerProvider.getTracer("demo-db-client", "0.1.0-beta1"); +} + +private Response selectWithTracing(Query query) { + // スパンの名前と属性に関する手引きについては、規約をチェックすること + Span span = tracer.spanBuilder(String.format("SELECT %s.%s", dbName, collectionName)) + .setSpanKind(SpanKind.CLIENT) + .setAttribute("db.name", dbName) + ... + .startSpan(); + + // スパンをアクティブにし、ログとネストスパンの関連付けを可能にする + try (Scope unused = span.makeCurrent()) { + Response response = query.runWithRetries(); + if (response.isSuccessful()) { + span.setStatus(StatusCode.OK); + } + + if (span.isRecording()) { + // レスポンスコードやその他の情報をレスポンス属性に入力する + } + } catch (Exception e) { + span.recordException(e); + span.setStatus(StatusCode.ERROR, e.getClass().getSimpleName()); + throw e; + } finally { + span.end(); + } +} +``` + +属性を入力するための規約に従ってください！ +該当するものがない場合は、[一般的な規約](/docs/specs/semconv/general/attributes/)をチェックしてください。 + +### ネストされたネットワークとその他のスパン {#nested-network-and-other-spans} + +ネットワーク呼び出しは通常、対応するクライアントの実装を通して、OpenTelemetry 自動計装でトレースされます。 + +![JaegerのUIでのネストされたデータベースとHTTPスパン](../nested-spans.svg) + +OpenTelemetryがネットワーククライアントのトレースをサポートしていない場合、最善の判断をしてください。 + +- ネットワーク呼び出しをトレースすることで、ユーザーやあなたのサポート能力が向上するでしょうか +- あなたのライブラリは、公開され、ドキュメント化されたRPC API上のラッパーですか。問題が発生した場合、ユーザーは基礎となるサービスからサポートを受ける必要がありますか。 + - ライブラリーを計装し、個々のネットワークトライをトレースしましょう。 +- スパンを使ってこれらの呼び出しをトレースすると、非常に冗長になりますか、それともパフォーマンスに顕著な影響を与えますか。 + - 冗長性やスパンイベントにはログを使いましょう。ログは親（パブリックAPIコール）に関連付けられ、スパンイベントはパブリックAPIスパンに設定されるべきです。 + - スパンである必要がある場合（ユニークなトレースコンテキストを伝送し、伝播するため）、設定オプションで指定するようにさせ、デフォルトでは無効にしましょう。 + +OpenTelemetryがすでにネットワーク呼び出しのトレースをサポートしているのであれば、おそらく、それを複製する必要はないでしょう。 +以下のように例外もあります。 + +- 自動計装を使用しないユーザーをサポートする場合（環境によっては機能しない場合や、ユーザーがモンキーパッチに懸念を持つ場合がある） +- 基礎となるサービスとのカスタム（レガシー）相関およびコンテキスト伝播プロトコルを有効にする場合 +- 自動計装ではカバーされない、絶対に必要なライブラリ／サービス固有の情報でRPCスパンを充実させる場合 + +警告：重複を避けるための一般的なソリューションは現在作成中です 🚧 + +### イベント {#events} + +トレースは、アプリが発するシグナルの一種です。 +イベント（またはログ）とトレースは、互いに補完し合うものであり、重複するものではありません。 +冗長性を持たせる必要がある場合は、トレースよりもログの方が適しています。 + +あなたのアプリは、すでにロギングか、似たようなモジュールを使っている可能性があります。 +あなたのモジュールは、すでに OpenTelemetry と統合されているかもしれません。それを調べるには、[レジストリ](/ecosystem/registry/) を参照してください。 +統合は通常、すべてのログにアクティブなトレースコンテキストを埋め込むことで、ユーザがそれらを関連付けられるようになります。 + +あなたの言語とエコシステムが共通のロギングサポートを持っていない場合、[スパンイベント][span events]を使って追加のアプリの詳細を共有します。 +属性も追加したい場合は、イベントの方が便利かもしれません。 + +経験則として、詳細データにはスパンではなくイベントまたはログを使用しましょう。 +常に、計装が作成したスパンインスタンスにイベントを添付してください。 +アクティブスパンの使用は、それが何を参照しているのか制御できないため、できる限り避けてください。 + +## コンテキスト伝搬 {#context-propagation} + +### コンテキストの抽出 {#extracting-context} + +もしあなたがライブラリやサービス、たとえばウェブフレームワークやメッセージングコンシューマーなどの上流の呼び出しを受信するような仕事をしているなら、受信するリクエスト／メッセージからコンテキストを抽出する必要があります。 +OpenTelemetryは `Propagator` APIを提供していて、これは特定の伝播基準を隠して、トレースされた `Context` をワイヤーから読み取ります。 +単一のレスポンスの場合、ワイヤー上のコンテキストは1つだけです。これはライブラリが作成する新しいスパンの親になります。 + +スパンを作成した後、スパンをアクティブにすることで、新しいトレースコンテキストをアプリケーションコード（コールバックまたはハンドラー）に渡す必要があります。 + +```java +// コンテキストを抽出する +Context extractedContext = propagator.extract(Context.current(), httpExchange, getter); +Span span = tracer.spanBuilder("receive") + .setSpanKind(SpanKind.SERVER) + .setParent(extractedContext) + .startSpan(); + +// スパンをアクティブにし、ネストされたテレメトリーが相関するようにする +try (Scope unused = span.makeCurrent()) { + userCode(); +} catch (Exception e) { + span.recordException(e); + span.setStatus(StatusCode.ERROR); + throw e; +} finally { + span.end(); +} +``` + +ここに[Java でのコンテキスト抽出の例](/docs/languages/java/instrumentation/#context-propagation) の完全なものがあります。 + +メッセージングシステムの場合、一度に複数のメッセージを受け取ることがあります。 +受信したメッセージは、作成したスパンの[_リンク_](/docs/languages/java/instrumentation/#create-spans-with-links)になります。 +詳しくは[メッセージング規約](/docs/specs/semconv/messaging/messaging-spans/)を参照してください（警告：メッセージング規約は[策定中](https://github.com/open-telemetry/oteps/pull/173) 🚧 です）。 + +### コンテキストを注入する {#injecting-context} + +外部呼び出しを行う場合、通常はコンテキストを下流のサービスに伝搬させたくなります。 +この場合、外部呼び出しをトレースする新しいスパンを作成し、`Propagator` API を使ってメッセージにコンテキストを注入します。 +非同期処理用のメッセージを作成する場合など、コンテキストを注入したいケースは他にもあるかもしれません。 + +```java +Span span = tracer.spanBuilder("send") + .setSpanKind(SpanKind.CLIENT) + .startSpan(); + +// スパンをアクティブにすることで、ネスト化されたテレメトリを相関させる +// ネットワークコールでも、スパン、ログ、イベントのネスト化されたレイヤーがあるかもしれない +try (Scope unused = span.makeCurrent()) { + // コンテキストを注入 + propagator.inject(Context.current(), transportLayer, setter); + send(); +} catch (Exception e) { + span.recordException(e); + span.setStatus(StatusCode.ERROR); + throw e; +} finally { + span.end(); +} +``` + +[Javaにおけるコンテキスト注入の例](/docs/languages/java/instrumentation/#context-propagation)の全体はこちらを参照してください。 + +下記のように例外もあるかもしれません。 + +- 下流のサービスはメタデータをサポートしていないか、未知のフィールドを禁止している +- 下流のサービスが相関プロトコルを定義していない。将来のサービスのバージョンで、互換性のあるコンテキスト伝播がサポートされる可能性はありますか。ないなら入れましょう！ +- 下流のサービスは、カスタム相関プロトコルをサポートしている + - カスタムプロパゲーターでベストエフォートで対応している。互換性があればOpenTelemetryトレースコンテキストを使いましょう。 + - あるいはスパンにカスタム相関IDを生成して埋め込みましょう。 + +### プロセス内 {#in-process} + +- **スパンをアクティブにする**（別名カレント）。スパンをログやネストされた自動計装と関連付けられます。 +- ライブラリーにコンテキストの概念がある場合、アクティブスパンに加えて、**オプションで**明示的なトレースコンテキストの伝搬をサポートしましょう。 + - ライブラリが作成したスパン（トレースコンテキスト）を明示的にコンテキストに置き、そのアクセス方法をドキュメント化しましょう。 + - ユーザーが自分のコンテキストにトレースコンテキストを渡せるようにしましょう。 +- ライブラリ内で、トレースコンテキストを明示的に伝播させましょう。コールバック中にアクティブなスパンが変更される可能性があります！ + - パブリックAPIの上のユーザーからアクティブなコンテキストをできるだけ早く取得し、それをスパンの親コンテキストとして使用します。 + - コンテキストを受け渡し、明示的に伝播されたインスタンスに属性、例外、イベントを埋め込みます。 + - これは、スレッドを明示的に開始したり、バックグラウンド処理を行ったり、その他、使用する言語の非同期コンテキストフローの制限によって壊れる可能性がある場合に不可欠です。 + +## その他 {#misc} + +### 計装レジストリ {#instrumentation-registry} + +[OpenTelemetryレジストリ](/ecosystem/registry/)にあなたの計装ライブラリを追加してください。 + +### パフォーマンス {#performance} + +OpenTelemetryのAPIは、アプリケーションにSDKがない場合、no-opで、非常にパフォーマンスが良いです。 +OpenTelemetry SDK が設定されると、[バインドされたリソースを消費します](/docs/specs/otel/performance/)。 + +実際のアプリケーション、特に大規模なものでは、ヘッドベースのサンプリングが頻繁に設定されます。 +サンプリングアウトされたスパンは安価であり、属性の入力中に余分な割り当てや高価な計算を避けるために、スパンが記録されているかどうかをチェックできます。 + +```java +// サンプリングに重要な属性がある場合は、作成時に提供する必要がある +Span span = tracer.spanBuilder(String.format("SELECT %s.%s", dbName, collectionName)) + .setSpanKind(SpanKind.CLIENT) + .setAttribute("db.name", dbName) + ... + .startSpan(); + +// スパンが記録される場合は、他の属性、特に計算コストのかかる属性を追加する必要がある +if (span.isRecording()) { + span.setAttribute("db.statement", sanitize(query.statement())) +} +``` + +### エラーハンドリング {#error-handling} + +OpenTelemetry APIは、[実行時に寛容です](/docs/specs/otel/error-handling/#basic-error-handling-principles)。 +無効な引数では失敗せず、決して例外をスローせずに飲み込みます。 +このようにして、計装の問題がアプリケーションロジックに影響を与えないようにします。 +OpenTelemetry が実行時に隠す問題に気づくために、計装をテストしてください。 + +### テスト {#testing} + +OpenTelemetry にはさまざまな自動計装があるので、あなたの計装が他のテレメトリー（受信リクエスト、送信リクエスト、ログなど）とどのように相互作用するかを試してみるのは便利です。 +計装を試すときは、一般的なフレームワークとライブラリを使い、すべてのトレースを有効にした典型的なアプリケーションを使ってください。 +あなたのライブラリと似たライブラリがどのように表示されるかをチェックしてください。 + +ユニットテストでは、通常、`SpanProcessor`と`SpanExporter`をモックまたはフェイクできます。 + +```java +@Test +public void checkInstrumentation() { + SpanExporter exporter = new TestExporter(); + + Tracer tracer = OpenTelemetrySdk.builder() + .setTracerProvider(SdkTracerProvider.builder() + .addSpanProcessor(SimpleSpanProcessor.create(exporter)).build()).build() + .getTracer("test"); + // テストを実行... + + validateSpans(exporter.exportedSpans); +} + +class TestExporter implements SpanExporter { + public final List exportedSpans = Collections.synchronizedList(new ArrayList<>()); + + @Override + public CompletableResultCode export(Collection spans) { + exportedSpans.addAll(spans); + return CompletableResultCode.ofSuccess(); + } + ... +} +``` + +[instrumentation libraries]: /docs/specs/otel/overview/#instrumentation-libraries +[span events]: /docs/specs/otel/trace/api/#add-events diff --git a/content/ja/docs/concepts/instrumentation/zero-code.md b/content/ja/docs/concepts/instrumentation/zero-code.md new file mode 100644 index 000000000000..c04e70d7ba49 --- /dev/null +++ b/content/ja/docs/concepts/instrumentation/zero-code.md @@ -0,0 +1,39 @@ +--- +title: ゼロコード +description: >- + コードを書かずにアプリケーションにオブザーバビリティを追加する方法を学ぶ +weight: 10 +default_lang_commit: d8c5612 +--- + +[運用担当者](/docs/getting-started/ops/)として、ソースを編集することなく、1つ以上のアプリケーションにオブザーバビリティを追加したいと思うかもしれません。 +OpenTelemetry を使えば、[コードベースの計装](/docs/concepts/instrumentation/code-based) のための OpenTelemetry API & SDK を使わなくても、サービスのオブザーバビリティを素早く得られます。 + +ゼロコード計装は、OpenTelemetry APIとSDKの機能を使って、通常、エージェントあるいはそれに準ずる機能をアプリケーションに追加します。 +具体的なメカニズムは言語によって異なり、バイトコード操作、モンキーパッチ、あるいはeBPFから、アプリケーションにOpenTelemetry APIとSDKへの呼び出しを注入します。 + +通常、ゼロコード計装は、使用しているライブラリの計装を追加します。 +つまり、リクエストとレスポンス、データベース呼び出し、メッセージキュー呼び出しなどが計装の対象となります。 +しかし、アプリケーションのコードは通常、計装されません。 +コードを計装するには、[コードベース計装](/docs/concepts/instrumentation/code-based)を使う必要があります。 + +さらに、ゼロコード計装では、読み込まれた[計装ライブラリ](/docs/concepts/instrumentation/libraries)や[エクスポーター](/docs/concepts/components/#exporters)を設定を行うことができます。 + +環境変数や、システムプロパティや初期化メソッドに渡される引数のような他の言語固有のメカニズムを通して、ゼロコード計装を設定できます。 +開始するには、選択したオブザーバビリティバックエンドでサービスを識別できるように設定されたサービス名だけが必要です。 + +その他、以下のような設定オプションがあります。 + +- データソース固有の設定 +- エクスポーターの設定 +- プロパゲーターの設定 +- リソースの設定 + +ゼロコード計装は以下の言語に対応しています。 + +- [.NET](/docs/zero-code/net/) +- [Go](/docs/zero-code/go) +- [Java](/docs/zero-code/java/) +- [JavaScript](/docs/zero-code/js/) +- [PHP](/docs/zero-code/php/) +- [Python](/docs/zero-code/python/) diff --git a/content/pt/_index.md b/content/pt/_index.md new file mode 100644 index 000000000000..44b22fa3d7cb --- /dev/null +++ b/content/pt/_index.md @@ -0,0 +1,90 @@ +--- +title: OpenTelemetry +description: >- + Telemetria de alta qualidade, abrangente e portátil para permitir uma observabilidade eficaz +developer_note: + O shortcode blocks/cover (usado abaixo) vai servir como imagem de background + para qualquer arquivo de imagem que contenha "background" no nome. +show_banner: true +default_lang_commit: 08799298 +--- + +
+ +{{< blocks/cover image_anchor="top" height="max" color="primary" >}} + + +![OpenTelemetry](/img/logos/opentelemetry-horizontal-color.svg) +{.otel-logo} + + +{{% param description %}} +{.display-6} + +
+ +- [Saiba mais](docs/what-is-opentelemetry/) +- [Experimente a demonstração](docs/demo/) +- [Explore as integrações](/ecosystem/integrations) + +
+ +
+Comece baseado na sua área +
+
+ +- [Dev](docs/getting-started/dev/) +- [Ops](docs/getting-started/ops/) + +
+{{< /blocks/cover >}} + +{{% blocks/lead color="white" %}} + +O OpenTelemetry é uma coleção de APIs, SDKs e ferramentas. Use-o para instrumentar, +gerar, coletar e exportar dados de telemetria (métricas, logs e rastros) para ajudar +você a analisar o desempenho e o comportamento do seu software. + +> O OpenTelemetry está **disponível** em +[diversas linguagens](docs/languages/) e está pronto para uso em produção. + +{{% /blocks/lead %}} + +{{% blocks/section color="dark" type="row" %}} + +{{% blocks/feature icon="fas fa-chart-line" title="Rastros, Métricas, Logs"%}} + +Crie e colete dados de telemetria a partir de seus serviços e softwares, e depois +encaminhe-os para uma variedade de ferramentas de análise. {{% /blocks/feature %}} + +{{% blocks/feature icon="fas fa-magic" title="Instrumentação de Fácil Integração"%}} + +O OpenTelemetry é integrável com frameworks e bibliotecas populares como +[Spring](https://spring.io), +[ASP.NET Core](https://docs.microsoft.com/aspnet/core), +[Express](https://expressjs.com), [Quarkus](https://quarkus.io), e muito mais! +A instalação e integração podem ser feitas com algumas linhas de código. + +{{% /blocks/feature %}} + +{{% blocks/feature icon="fab fa-github" title="Open Source, Agnóstico a Fornecedor" %}} + +100% Gratuito e Open Source, o OpenTelemetry é adotado e apoiado por +[líderes da indústria](/ecosystem/vendors/) no ecossistema da observabilidade. + +{{% /blocks/feature %}} + +{{% /blocks/section %}} + +{{% blocks/section color="secondary" type="cncf" %}} + +**O OpenTelemetry é um projeto em [incubação][] da [CNCF][]**.
Formado por meio de uma junção dos projetos OpenTracing e OpenCensus. + +[![CNCF logo][]][cncf] + +[cncf]: https://cncf.io +[cncf logo]: /img/logos/cncf-white.svg +[incubação]: https://www.cncf.io/projects/ + +{{% /blocks/section %}} diff --git a/data/registry/collector-builder.yml b/data/registry/collector-builder.yml index b16c5ae33865..18735d681336 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.104.0 + version: v0.105.0 quickInstall: false diff --git a/data/registry/collector-exporter-alertmanager.yml b/data/registry/collector-exporter-alertmanager.yml index 3b6737fd87db..5c93e7740752 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.104.0 + version: v0.105.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 6dddc71e5c07..3299d407660d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-aws-xray.yml b/data/registry/collector-exporter-aws-xray.yml index 7fe2dda6844e..3041990300d7 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-awscloudwatchlogs.yml b/data/registry/collector-exporter-awscloudwatchlogs.yml index b808ebc037cf..1b3ad4ad4fc0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-awsemf.yml b/data/registry/collector-exporter-awsemf.yml index fd7c185d7dfc..4965b183f626 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-awss3.yml b/data/registry/collector-exporter-awss3.yml index 0f3fa6993f2c..202fd9f3cfff 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-azure-monitor.yml b/data/registry/collector-exporter-azure-monitor.yml index f255c3d56493..4a9980f5db87 100644 --- a/data/registry/collector-exporter-azure-monitor.yml +++ b/data/registry/collector-exporter-azure-monitor.yml @@ -16,4 +16,4 @@ createdAt: 2020-06-06 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/azuremonitorexporter - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-azuredataexplorer.yml b/data/registry/collector-exporter-azuredataexplorer.yml index 2897f403c59f..c661ec514039 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-carbon.yml b/data/registry/collector-exporter-carbon.yml index 0143d83b5ef6..e1b722cc01d2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-cassandra.yml b/data/registry/collector-exporter-cassandra.yml index 1f1d72b6a90e..7c857b06e592 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-clickhouse.yml b/data/registry/collector-exporter-clickhouse.yml index 39d23f0c37ce..370c3415b29d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-coralogix.yml b/data/registry/collector-exporter-coralogix.yml index 6b2dd1339cc9..07690a217c56 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-datadog.yml b/data/registry/collector-exporter-datadog.yml index 4c32ed92f04c..a16740c7585e 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-dataset.yml b/data/registry/collector-exporter-dataset.yml index 30bb5f3b90e5..c31a36532649 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-debug.yml b/data/registry/collector-exporter-debug.yml index 0100a53e1930..8e7699e45594 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-elasticsearch.yml b/data/registry/collector-exporter-elasticsearch.yml index cc04d6fdca11..da276866a8aa 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-file.yml b/data/registry/collector-exporter-file.yml index 17521256a5a1..c3bfebf631c8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-googlecloud.yml b/data/registry/collector-exporter-googlecloud.yml index 1a4520cc7198..5b1bfbb4fa6f 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-googlecloudpubsub.yml b/data/registry/collector-exporter-googlecloudpubsub.yml index 2aa5125222c3..a92465621ab4 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-googlemanagedprometheus.yml b/data/registry/collector-exporter-googlemanagedprometheus.yml index ebb47a46d8d4..2135b5ecbd08 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-honeycombmarker.yml b/data/registry/collector-exporter-honeycombmarker.yml index 71bd03f80802..022218371246 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-influxdb.yml b/data/registry/collector-exporter-influxdb.yml index 44cfc0470c9e..034b6a9e5db2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-instana.yml b/data/registry/collector-exporter-instana.yml index 8942db961c5f..5f90418331a0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-kafka.yml b/data/registry/collector-exporter-kafka.yml index 0ced42887b74..d2cdc6fc0dca 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-kinetica.yml b/data/registry/collector-exporter-kinetica.yml index fb2f66b71568..6d946f01b3e6 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-load-balancing.yml b/data/registry/collector-exporter-load-balancing.yml index 25ff01b6e5bc..9270d696b880 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-logicmonitor.yml b/data/registry/collector-exporter-logicmonitor.yml index b969ca65c769..48febf17e235 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-logzio.yml b/data/registry/collector-exporter-logzio.yml index 58a032012588..6bd268bdba01 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-loki.yml b/data/registry/collector-exporter-loki.yml index 2b6d7ceed5ff..8f6c88af2ebf 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-mezmo.yml b/data/registry/collector-exporter-mezmo.yml index 7e67fdba056d..145c0fefc623 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-nop.yml b/data/registry/collector-exporter-nop.yml index 7ab6d74c8212..d580bf5bc6fe 100644 --- a/data/registry/collector-exporter-nop.yml +++ b/data/registry/collector-exporter-nop.yml @@ -19,4 +19,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: go.opentelemetry.io/collector/exporter/nopexporter - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-opencensus.yml b/data/registry/collector-exporter-opencensus.yml index 647017a400ad..5068152ca6db 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-opensearch.yml b/data/registry/collector-exporter-opensearch.yml index b06c072e2ce0..9b61fcbaa5f1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-otelarrow.yml b/data/registry/collector-exporter-otelarrow.yml index 8472052a313e..1ee260d8e0f5 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-otlp.yml b/data/registry/collector-exporter-otlp.yml index 423d08289a43..d182f6d53d6d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-prometheus-remote-write.yml b/data/registry/collector-exporter-prometheus-remote-write.yml index 5e7643646a5b..191e85c012a5 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-prometheus.yml b/data/registry/collector-exporter-prometheus.yml index cf4914a8cf26..929a216e25b5 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-pulsar.yml b/data/registry/collector-exporter-pulsar.yml index 705682eed3b2..1acc502b2bdf 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-rabbitmq.yml b/data/registry/collector-exporter-rabbitmq.yml index adb4079ab507..27dd6619f620 100644 --- a/data/registry/collector-exporter-rabbitmq.yml +++ b/data/registry/collector-exporter-rabbitmq.yml @@ -17,4 +17,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/rabbitmqexporter - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-sapm.yml b/data/registry/collector-exporter-sapm.yml index 1623efb0289a..c767166b28f1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-sentry.yml b/data/registry/collector-exporter-sentry.yml index b5cd49eda517..50e2a98189ea 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-signalfx.yml b/data/registry/collector-exporter-signalfx.yml index 1bcd5b99f6db..eb67875030a3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-skywalking.yml b/data/registry/collector-exporter-skywalking.yml deleted file mode 100644 index 183a5c3c66d0..000000000000 --- a/data/registry/collector-exporter-skywalking.yml +++ /dev/null @@ -1,21 +0,0 @@ -# cSpell:ignore skywalking skywalkingexporter -title: SkyWalking gRPC Exporter -registryType: exporter -language: collector -tags: - - go - - exporter - - collector -license: Apache 2.0 -description: - Exports data via gRPC using skywalking-data-collect-protocol format. By - default, this exporter requires TLS and offers queued retry capabilities. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/exporter/skywalkingexporter -createdAt: 2022-10-27 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/skywalkingexporter - version: v0.104.0 diff --git a/data/registry/collector-exporter-splunk-hec.yml b/data/registry/collector-exporter-splunk-hec.yml index b79241b2896f..f9b210f665ae 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-splunk-sapm.yml b/data/registry/collector-exporter-splunk-sapm.yml index 89dc3b5181e0..df10e8d86919 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-sumologic.yml b/data/registry/collector-exporter-sumologic.yml index 210dd35bafde..d265c591c141 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-syslog.yml b/data/registry/collector-exporter-syslog.yml index 5522e2385291..e4d37c5d084a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-tencentcloudlogservice.yml b/data/registry/collector-exporter-tencentcloudlogservice.yml index effdaac3be52..b0b99b5d1c7b 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-exporter-zipkin.yml b/data/registry/collector-exporter-zipkin.yml index e0a9cbd587ec..5ac440d449dd 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-ack.yml b/data/registry/collector-extension-ack.yml index 9eaab300c414..920fdc5e8bed 100644 --- a/data/registry/collector-extension-ack.yml +++ b/data/registry/collector-extension-ack.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/ackextension - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-asapauth.yml b/data/registry/collector-extension-asapauth.yml index b3743cc6e7a7..fb02b54b8b40 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-basicauth.yml b/data/registry/collector-extension-basicauth.yml index 390ae33eb00f..5bb8ccf06c68 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-bearertokenauth.yml b/data/registry/collector-extension-bearertokenauth.yml index a56521db2c5b..cf5faba94090 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-encoding.yml b/data/registry/collector-extension-encoding.yml index 6de0c206c441..f7e1a588cae8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-googleclientauth.yml b/data/registry/collector-extension-googleclientauth.yml index 094046b3f214..804082d4c7ad 100644 --- a/data/registry/collector-extension-googleclientauth.yml +++ b/data/registry/collector-extension-googleclientauth.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/googleclientauthextension - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-headerssetter.yml b/data/registry/collector-extension-headerssetter.yml index c85d668a1013..304cdc3dd97f 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-healthcheck.yml b/data/registry/collector-extension-healthcheck.yml index fc5821b213c9..9a6b17c3e1ce 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-http-forwarder.yml b/data/registry/collector-extension-http-forwarder.yml index cc72cfbfa004..c3ba22c07d14 100644 --- a/data/registry/collector-extension-http-forwarder.yml +++ b/data/registry/collector-extension-http-forwarder.yml @@ -18,4 +18,4 @@ createdAt: 2021-02-24 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarderextension - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-jaegerremotesampling.yml b/data/registry/collector-extension-jaegerremotesampling.yml index c9d9370960c8..31318e9687e1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-memorylimiter.yml b/data/registry/collector-extension-memorylimiter.yml index 5ddaec020c52..851f7b4d7d3e 100644 --- a/data/registry/collector-extension-memorylimiter.yml +++ b/data/registry/collector-extension-memorylimiter.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: go.opentelemetry.io/collector/extension/memorylimiterextension - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-oauth2clientauth.yml b/data/registry/collector-extension-oauth2clientauth.yml index dd1fedfcb9a4..99db0efc25aa 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-oidcauth.yml b/data/registry/collector-extension-oidcauth.yml index cfe7102bd279..a3834420059e 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-opamp.yml b/data/registry/collector-extension-opamp.yml index df04f2ec0d1f..6f275626100e 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-pprof.yml b/data/registry/collector-extension-pprof.yml index 75f5a03a8b37..0d39dbbc7b04 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-remotetap.yml b/data/registry/collector-extension-remotetap.yml index 66d4ffad862c..5ffa90330fcf 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-sigv4auth.yml b/data/registry/collector-extension-sigv4auth.yml index 403368f11724..94f3f364c214 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-solarwindsapmsettings.yml b/data/registry/collector-extension-solarwindsapmsettings.yml index 3604eb9ffce0..2a424e5c7fa2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-extension-sumologic.yml b/data/registry/collector-extension-sumologic.yml index 38bc68d42565..d08f77acc94c 100644 --- a/data/registry/collector-extension-sumologic.yml +++ b/data/registry/collector-extension-sumologic.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/extension/sumologicextension - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-attributes.yml b/data/registry/collector-processor-attributes.yml index 1ec63ae96a87..812f58135074 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-batch.yml b/data/registry/collector-processor-batch.yml index 676a431550d0..11b9f831f486 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-cumulativetodelta.yml b/data/registry/collector-processor-cumulativetodelta.yml index 1d8dc6a80edf..c3ec7a3881f5 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-deltatocumulative.yml b/data/registry/collector-processor-deltatocumulative.yml index 81b6007b0a15..bbff2f96d08c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-deltatorate.yml b/data/registry/collector-processor-deltatorate.yml index f16bfb26cfd7..2ba5f19f1449 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-filter.yml b/data/registry/collector-processor-filter.yml index 9d1bf3e62b5a..2c509f209ec1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-geoip.yml b/data/registry/collector-processor-geoip.yml new file mode 100644 index 000000000000..3107421f727c --- /dev/null +++ b/data/registry/collector-processor-geoip.yml @@ -0,0 +1,20 @@ +# cSpell:ignore geoip geoipprocessor +title: GeoIP Processor +registryType: processor +language: collector +tags: + - geoip + - processor + - collector +urls: + repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/geoipprocessor +license: Apache 2.0 +description: + The geoIP processor `geoipprocessor` enhances resource attributes by appending + information about the geographical location of an IP address. To add + geographical information, the IP address must be included in the resource + attributes using the [`source.address` semantic conventions key + attribute](https://github.com/open-telemetry/semantic-conventions/blob/v1.26.0/docs/general/attributes.md#source). +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/collector-processor-group-by-trace.yml b/data/registry/collector-processor-group-by-trace.yml index 9f724d290c74..31136e59fe00 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-groupbyattrs.yml b/data/registry/collector-processor-groupbyattrs.yml index 26a9c60f4c9d..8f98faae23be 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-interval.yml b/data/registry/collector-processor-interval.yml index 297f682d27b5..226ccb298deb 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-k8sattributes.yml b/data/registry/collector-processor-k8sattributes.yml index 4a4852cbb096..a694235240ee 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-logstransform.yml b/data/registry/collector-processor-logstransform.yml index 1ee1ee787202..6638bf3d3f5a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-metrics-transform.yml b/data/registry/collector-processor-metrics-transform.yml index a01d99271fd2..3035d76a5e40 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-metricsgeneration.yml b/data/registry/collector-processor-metricsgeneration.yml index ad9de1910556..96f604fa8f49 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-probabilisticsampler.yml b/data/registry/collector-processor-probabilisticsampler.yml index 9e6e17ced73e..f552fad65b69 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-redaction.yml b/data/registry/collector-processor-redaction.yml index 019462fb125a..b5982e97acad 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-remotetap.yml b/data/registry/collector-processor-remotetap.yml index 11356a8c99d1..c4c9519eac31 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-resource-detection.yml b/data/registry/collector-processor-resource-detection.yml index eed69403e1f3..642851cd10c1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-resource.yml b/data/registry/collector-processor-resource.yml index 47b7cbfbab9d..765e62abd95c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-routing.yml b/data/registry/collector-processor-routing.yml index b1501c864c99..8cd1700ebea7 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-schema.yml b/data/registry/collector-processor-schema.yml index acfc5e413f7c..e12b4cea25a3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-span.yml b/data/registry/collector-processor-span.yml index 4ac56f8dfa8e..b0a5dc4b54ca 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-sumologic.yml b/data/registry/collector-processor-sumologic.yml index 45c6d6a90c7a..6fb25953a61c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-tail-sampling.yml b/data/registry/collector-processor-tail-sampling.yml index de2d4ae221c1..542d52394db3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-processor-transform.yml b/data/registry/collector-processor-transform.yml index 73106387d568..bcaa3e52dadb 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-activedirectoryds.yml b/data/registry/collector-receiver-activedirectoryds.yml index 5c2a36b59cd8..e4b081eb218a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-aerospike.yml b/data/registry/collector-receiver-aerospike.yml index 2d66865f5b29..492c817867df 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-apache.yml b/data/registry/collector-receiver-apache.yml index f11b3881f89c..5765ed175942 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-apachespark.yml b/data/registry/collector-receiver-apachespark.yml index c8b7606a2043..f4781a76023b 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-aws-ecs-container-metrics.yml b/data/registry/collector-receiver-aws-ecs-container-metrics.yml index 6345d35303fc..d2d3eb122d42 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-aws-xray.yml b/data/registry/collector-receiver-aws-xray.yml index 4dc580b9d93a..da1de9ac9ed2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-awscloudwatch.yml b/data/registry/collector-receiver-awscloudwatch.yml index 77a3ccf449f7..926b06009a23 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-awscloudwatchmetrics.yml b/data/registry/collector-receiver-awscloudwatchmetrics.yml index 347c311a9699..7741d869788b 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-awscontainerinsight.yml b/data/registry/collector-receiver-awscontainerinsight.yml index 0bb0c80f4fe8..8502e06eb86a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-awsfirehose.yml b/data/registry/collector-receiver-awsfirehose.yml index d51446758b56..98777424c976 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-awss3.yml b/data/registry/collector-receiver-awss3.yml index 010b1129ed7f..171198742e0f 100644 --- a/data/registry/collector-receiver-awss3.yml +++ b/data/registry/collector-receiver-awss3.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/awss3receiver - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-azureblob.yml b/data/registry/collector-receiver-azureblob.yml index 542cd7e53074..5aff95019c2b 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-azureeventhub.yml b/data/registry/collector-receiver-azureeventhub.yml index 7906104d6b46..df0911362f20 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-azuremonitor.yml b/data/registry/collector-receiver-azuremonitor.yml index ef0b17b94517..8473c3a32b17 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-bigip.yml b/data/registry/collector-receiver-bigip.yml index c5d87e91eef3..1b5a62663776 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-carbon.yml b/data/registry/collector-receiver-carbon.yml index 578b91f70817..f1c6f4e52f03 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-chrony.yml b/data/registry/collector-receiver-chrony.yml index 0332d5d1a1d4..a225c6c284e8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-cloudflare.yml b/data/registry/collector-receiver-cloudflare.yml index 22a969ec953f..e543da161103 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-cloudfoundry.yml b/data/registry/collector-receiver-cloudfoundry.yml index 3da44fd1bf33..b085d9963704 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-collectd.yml b/data/registry/collector-receiver-collectd.yml index 9dc079facb55..f3e82679bdec 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-couchdb.yml b/data/registry/collector-receiver-couchdb.yml index 9ee4e714a0f6..862b6a7bd08f 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-datadog.yml b/data/registry/collector-receiver-datadog.yml index 5b2a4e4071af..a60b9efff8dc 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-docker-stats.yml b/data/registry/collector-receiver-docker-stats.yml index 5a3f321711a0..e4d307e3cd58 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-elasticsearch.yml b/data/registry/collector-receiver-elasticsearch.yml index df54ed58b3d7..9d2539f3d8b0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-expvar.yml b/data/registry/collector-receiver-expvar.yml index d5d801ecb97f..322ee67d51db 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-file.yml b/data/registry/collector-receiver-file.yml deleted file mode 100644 index f0dd8bc1e9ba..000000000000 --- a/data/registry/collector-receiver-file.yml +++ /dev/null @@ -1,21 +0,0 @@ -# cSpell:ignore filereceiver -title: File Receiver -registryType: receiver -language: collector -tags: - - file - - receiver - - collector -license: Apache 2.0 -description: - The File Receiver reads the output of a File Exporter, converting that output - to metrics, and sending the metrics down the pipeline. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filereceiver -createdAt: 2022-10-25 -package: - registry: go-collector - name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/filereceiver - version: v0.94.0 diff --git a/data/registry/collector-receiver-filelog.yml b/data/registry/collector-receiver-filelog.yml index bdcc62d17567..4163840dcce6 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-filestats.yml b/data/registry/collector-receiver-filestats.yml index 4009dc33146a..59257767592f 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-flinkmetrics.yml b/data/registry/collector-receiver-flinkmetrics.yml index 85b73d069ccf..bca7e6f765a8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-fluent-forward.yml b/data/registry/collector-receiver-fluent-forward.yml index ecc3df7b3386..a432a02fbcc0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-gitprovider.yml b/data/registry/collector-receiver-gitprovider.yml index 972e5a89da9a..afe42d707d10 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-googlecloudpubsub.yml b/data/registry/collector-receiver-googlecloudpubsub.yml index 6e89711fdea5..d447bcf65f03 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-googlecloudspanner.yml b/data/registry/collector-receiver-googlecloudspanner.yml index 0c8777f08391..76c98096a5bb 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-haproxy.yml b/data/registry/collector-receiver-haproxy.yml index 9297d170cbfd..e34e1b0035cf 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-host-metrics.yml b/data/registry/collector-receiver-host-metrics.yml index 56e8cf17b497..b8eb98b81ff9 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-httpcheck.yml b/data/registry/collector-receiver-httpcheck.yml index 231b03d346c0..e99b90e76467 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-iis.yml b/data/registry/collector-receiver-iis.yml index 4030eb41c4e6..e11abd8c2bfe 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-influxdb.yml b/data/registry/collector-receiver-influxdb.yml index 65adae39f65b..759eaa80e719 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-jaeger.yml b/data/registry/collector-receiver-jaeger.yml index 7e581c459514..773053259b50 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-jmx.yml b/data/registry/collector-receiver-jmx.yml index 95d58bd339b5..dca2248ea204 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-journald.yml b/data/registry/collector-receiver-journald.yml index bfc0cdfdd302..acd6c90953e6 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-k8s-cluster.yml b/data/registry/collector-receiver-k8s-cluster.yml index 4f761fee8f06..01172c2b7ad3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-k8sevents.yml b/data/registry/collector-receiver-k8sevents.yml index 7d723e226e53..3571db7a82b3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-k8sobjects.yml b/data/registry/collector-receiver-k8sobjects.yml index 0a915fe9b76f..e877a9e2ae2c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-kafka.yml b/data/registry/collector-receiver-kafka.yml index fef5278953c4..758e1c5d5801 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-kafkametrics.yml b/data/registry/collector-receiver-kafkametrics.yml index cdeb019061e5..34a4a8551ee4 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-kubelet-stats.yml b/data/registry/collector-receiver-kubelet-stats.yml index 1ee4ec2179d4..e00ec190f3b4 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-loki.yml b/data/registry/collector-receiver-loki.yml index c5c412de79e8..99672b12e71b 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-memcached.yml b/data/registry/collector-receiver-memcached.yml index 6fe4617224c1..0a6f947f7510 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-mongodb.yml b/data/registry/collector-receiver-mongodb.yml index 774e8c0bebcf..012fb0692ad1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-mongodbatlas.yml b/data/registry/collector-receiver-mongodbatlas.yml index b0c0141b2591..f5e90b6644a7 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-mysql.yml b/data/registry/collector-receiver-mysql.yml index ac205fc01c43..b2df0ff4a7cc 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-namedpipe.yml b/data/registry/collector-receiver-namedpipe.yml index 6973a5e1f42e..5185d2e1750d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-nginx.yml b/data/registry/collector-receiver-nginx.yml index 77a174c1d653..03707c9a7f6d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-nop.yml b/data/registry/collector-receiver-nop.yml index 484cc1053481..b0295f811088 100644 --- a/data/registry/collector-receiver-nop.yml +++ b/data/registry/collector-receiver-nop.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: go.opentelemetry.io/collector/receiver/nopreceiver - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-nsxt.yml b/data/registry/collector-receiver-nsxt.yml index cb4594e751ff..33fab6f19699 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-opencensus.yml b/data/registry/collector-receiver-opencensus.yml index 3078a43e4f89..2c289e3369d0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-oracledb.yml b/data/registry/collector-receiver-oracledb.yml index 381b8127d2a1..e95952e1709c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-osquery.yml b/data/registry/collector-receiver-osquery.yml index 705e79804e2f..6e6bdc5e9ed2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-otelarrow.yml b/data/registry/collector-receiver-otelarrow.yml index 6e3c71e8cd28..c9ff99cdd56b 100644 --- a/data/registry/collector-receiver-otelarrow.yml +++ b/data/registry/collector-receiver-otelarrow.yml @@ -18,4 +18,4 @@ createdAt: 2024-04-18 package: registry: go-collector name: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/otelarrowreceiver - version: v0.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-otlp.yml b/data/registry/collector-receiver-otlp.yml index 480ea3daf655..6bdb7e71d734 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-otlpjsonfile.yml b/data/registry/collector-receiver-otlpjsonfile.yml index 5287542c7180..54219e33135f 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-podman.yml b/data/registry/collector-receiver-podman.yml index 6d20feaaca86..9bf399bffeb2 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-postgresql.yml b/data/registry/collector-receiver-postgresql.yml index ce794ea1a0a2..571f51367032 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-prometheus.yml b/data/registry/collector-receiver-prometheus.yml index 0419872f7043..2d2454f513d9 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-pulsar.yml b/data/registry/collector-receiver-pulsar.yml index 8e5ee879a98a..0de00d4b749c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-purefa.yml b/data/registry/collector-receiver-purefa.yml index 73be9e31e126..07ca76aefc3a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-purefb.yml b/data/registry/collector-receiver-purefb.yml index 9a5b1c9d7d25..cf278e011877 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-rabbitmq.yml b/data/registry/collector-receiver-rabbitmq.yml index d9c3cf86d03f..bb4f4b653d36 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-receiver-creator.yml b/data/registry/collector-receiver-receiver-creator.yml index 3fddcfb60fe7..2721957f8e80 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-redis.yml b/data/registry/collector-receiver-redis.yml index 82f435834d73..a47bef9270fb 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-riak.yml b/data/registry/collector-receiver-riak.yml index d35c98d6114d..4dd03c222e39 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-saphana.yml b/data/registry/collector-receiver-saphana.yml index a9a3d68b5279..30e9b3872e65 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-sapm.yml b/data/registry/collector-receiver-sapm.yml index 24ab1ee48781..2b4db3785955 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-signalfx.yml b/data/registry/collector-receiver-signalfx.yml index a4a08b775be6..7fe41fe9f1ea 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-simple-prometheus.yml b/data/registry/collector-receiver-simple-prometheus.yml index ba348deefb11..d86fac751e9c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-skywalking.yml b/data/registry/collector-receiver-skywalking.yml index 303298b174a5..528b8008727d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-snmp.yml b/data/registry/collector-receiver-snmp.yml index 206b0e3ba426..7a12a7edcf65 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-snowflake.yml b/data/registry/collector-receiver-snowflake.yml index 604ed620b914..f4e94fc63289 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-solace.yml b/data/registry/collector-receiver-solace.yml index 56b8b573d585..3992ba605a53 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-splunk-hec.yml b/data/registry/collector-receiver-splunk-hec.yml index 193584320e01..38ca27cae056 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-splunkenterprise.yml b/data/registry/collector-receiver-splunkenterprise.yml index 92532fa0f657..f3a774d3a086 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-sqlquery.yml b/data/registry/collector-receiver-sqlquery.yml index 5ca999fe7818..f4744c8b401e 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-sqlserver.yml b/data/registry/collector-receiver-sqlserver.yml index 0cad7a32c340..12bfc19971d0 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-sshcheck.yml b/data/registry/collector-receiver-sshcheck.yml index e62eba2e3f99..aa98a8c241a8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-statsd.yml b/data/registry/collector-receiver-statsd.yml index 64c5a88af4d8..951daffcedc3 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-syslog.yml b/data/registry/collector-receiver-syslog.yml index 8f3b044e19f0..029092313f9a 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-tcplog.yml b/data/registry/collector-receiver-tcplog.yml index 5b16b58ae6f1..2fb8a8e630cf 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-udplog.yml b/data/registry/collector-receiver-udplog.yml index c46afca7fbff..d982c3c65df1 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-vcenter.yml b/data/registry/collector-receiver-vcenter.yml index 9562a2385e76..35752f40abd8 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-wavefront.yml b/data/registry/collector-receiver-wavefront.yml index 382879915bda..8d27c5f74902 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-webhookevent.yml b/data/registry/collector-receiver-webhookevent.yml index fd26fb256cf3..079b7f1ce17c 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-windows-perf-counters.yml b/data/registry/collector-receiver-windows-perf-counters.yml index 7fd488078328..ed98f6a48b26 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-windowseventlog.yml b/data/registry/collector-receiver-windowseventlog.yml index d4d9a0837efe..dac14fd8a92d 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.104.0 + version: v0.105.0 diff --git a/data/registry/collector-receiver-zipkin.yml b/data/registry/collector-receiver-zipkin.yml index a8a0fbeec879..babb3d68b604 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.104.0 + version: v0.105.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 c03dbd108b9a..adaa1cc1b5ab 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.104.0 + version: v0.105.0 diff --git a/data/registry/exporter-dotnet-azure.yml b/data/registry/exporter-dotnet-azure.yml index c87d35750387..b5e646a86e0a 100644 --- a/data/registry/exporter-dotnet-azure.yml +++ b/data/registry/exporter-dotnet-azure.yml @@ -13,7 +13,7 @@ authors: package: name: Azure.Monitor.OpenTelemetry.Exporter registry: nuget - version: 1.3.0 + version: 1.4.0-beta.1 urls: repo: https://github.com/Azure/azure-sdk-for-net/tree/main/sdk/monitor/Azure.Monitor.OpenTelemetry.Exporter createdAt: 2021-11-01 diff --git a/data/registry/exporter-js-instana.yml b/data/registry/exporter-js-instana.yml index 524611d278b4..00e2353fd54b 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.14.3 + version: 3.14.4 diff --git a/data/registry/exporter-rust-jaeger.yml b/data/registry/exporter-rust-jaeger.yml deleted file mode 100644 index bfccf6e0d705..000000000000 --- a/data/registry/exporter-rust-jaeger.yml +++ /dev/null @@ -1,17 +0,0 @@ -title: Jaeger Exporter -registryType: exporter -language: rust -tags: - - rust - - exporter -license: Apache 2.0 -description: The OpenTelemetry Jaeger Exporter for Rust. -authors: - - name: OpenTelemetry Authors -urls: - repo: https://github.com/open-telemetry/opentelemetry-rust/tree/main/opentelemetry-jaeger -createdAt: 2020-08-28 -package: - registry: crates - name: opentelemetry-jaeger - version: 0.20.0 diff --git a/data/registry/instrumentation-dotnet-aspnetcore.yml b/data/registry/instrumentation-dotnet-aspnetcore.yml index 71acbef5573d..e19af860289e 100644 --- a/data/registry/instrumentation-dotnet-aspnetcore.yml +++ b/data/registry/instrumentation-dotnet-aspnetcore.yml @@ -13,7 +13,7 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.AspNetCore + repo: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.AspNetCore createdAt: 2022-11-07 package: registry: nuget diff --git a/data/registry/instrumentation-dotnet-confluentkafka.yml b/data/registry/instrumentation-dotnet-confluentkafka.yml new file mode 100644 index 000000000000..c9523743779d --- /dev/null +++ b/data/registry/instrumentation-dotnet-confluentkafka.yml @@ -0,0 +1,15 @@ +title: Confluent.Kafka client instrumentation for OpenTelemetry +registryType: instrumentation +language: dotnet +tags: + - confluent + - kafka + - instrumentation + - dotnet +urls: + repo: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.ConfluentKafka +license: Apache 2.0 +description: Confluent.Kafka client instrumentation for OpenTelemetry +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-dotnet-grpcnetclient.yml b/data/registry/instrumentation-dotnet-grpcnetclient.yml index d657f4523642..95ed0781e057 100644 --- a/data/registry/instrumentation-dotnet-grpcnetclient.yml +++ b/data/registry/instrumentation-dotnet-grpcnetclient.yml @@ -13,7 +13,7 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.GrpcNetClient + repo: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.GrpcNetClient createdAt: 2022-11-07 package: registry: nuget diff --git a/data/registry/instrumentation-dotnet-http.yml b/data/registry/instrumentation-dotnet-http.yml index 64b9f3968492..c13fce8d045a 100644 --- a/data/registry/instrumentation-dotnet-http.yml +++ b/data/registry/instrumentation-dotnet-http.yml @@ -13,7 +13,7 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.Http + repo: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.Http createdAt: 2022-11-07 package: registry: nuget diff --git a/data/registry/instrumentation-dotnet-sqlclient.yml b/data/registry/instrumentation-dotnet-sqlclient.yml index 77a9e6e9f731..6e7df293932b 100644 --- a/data/registry/instrumentation-dotnet-sqlclient.yml +++ b/data/registry/instrumentation-dotnet-sqlclient.yml @@ -13,7 +13,7 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-dotnet/tree/main/src/OpenTelemetry.Instrumentation.SqlClient + repo: https://github.com/open-telemetry/opentelemetry-dotnet-contrib/tree/main/src/OpenTelemetry.Instrumentation.SqlClient createdAt: 2022-11-07 package: registry: nuget diff --git a/data/registry/instrumentation-java-apacheshenyu.yml b/data/registry/instrumentation-java-apacheshenyu.yml new file mode 100644 index 000000000000..786bd76e5e7c --- /dev/null +++ b/data/registry/instrumentation-java-apacheshenyu.yml @@ -0,0 +1,16 @@ +# cspell:ignore shenyu +title: Apache ShenYu instrumentation +registryType: instrumentation +language: java +tags: + - apache + - shenyu + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/apache-shenyu-2.4 +license: Apache 2.0 +description: Settings for the Apache ShenYu instrumentation +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-java-armeria.yml b/data/registry/instrumentation-java-armeria.yml index 98102bf4b303..72a581c3e70f 100644 --- a/data/registry/instrumentation-java-armeria.yml +++ b/data/registry/instrumentation-java-armeria.yml @@ -12,5 +12,5 @@ description: authors: - name: OpenTelemetry Authors urls: - repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/armeria-1.3 + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/armeria/armeria-1.3 createdAt: 2020-11-05 diff --git a/data/registry/instrumentation-java-influxdb.yml b/data/registry/instrumentation-java-influxdb.yml new file mode 100644 index 000000000000..b614c69c556c --- /dev/null +++ b/data/registry/instrumentation-java-influxdb.yml @@ -0,0 +1,14 @@ +title: influxdb instrumentation +registryType: instrumentation +language: java +tags: + - influxdb + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/influxdb-2.4 +license: Apache 2.0 +description: influxdb instrumentation +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-java-javalin.yml b/data/registry/instrumentation-java-javalin.yml new file mode 100644 index 000000000000..d2867a084a91 --- /dev/null +++ b/data/registry/instrumentation-java-javalin.yml @@ -0,0 +1,15 @@ +# cspell:ignore javalin +title: javalin instrumentation +registryType: instrumentation +language: java +tags: + - javalin + - instrumentation + - java +urls: + repo: https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/main/instrumentation/javalin-5.0 +license: Apache 2.0 +description: javalin instrumentation +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-js-prisma.yml b/data/registry/instrumentation-js-prisma.yml index 3419de332d81..22fa2390acc4 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.16.2 + version: 5.17.0 diff --git a/data/registry/instrumentation-php-cakephp.yml b/data/registry/instrumentation-php-cakephp.yml new file mode 100644 index 000000000000..d50b330f602a --- /dev/null +++ b/data/registry/instrumentation-php-cakephp.yml @@ -0,0 +1,16 @@ +title: OpenTelemetry CakePHP instrumentation library +registryType: instrumentation +language: php +tags: + - cake + - instrumentation + - php +urls: + repo: https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/CakePHP +license: Apache 2.0 +description: + Please read for instructions on how to + install and configure the extension and SDK. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-php-psr6.yml b/data/registry/instrumentation-php-psr6.yml new file mode 100644 index 000000000000..14a8e7423a82 --- /dev/null +++ b/data/registry/instrumentation-php-psr6.yml @@ -0,0 +1,16 @@ +title: OpenTelemetry PSR-6 instrumentation library +registryType: instrumentation +language: php +tags: + - psr6 + - instrumentation + - php +urls: + repo: https://github.com/open-telemetry/opentelemetry-php-contrib/tree/main/src/Instrumentation/Psr6 +license: Apache 2.0 +description: + Please read for instructions on how to + install and configure the extension and SDK. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 diff --git a/data/registry/instrumentation-ruby-actionmailer.yml b/data/registry/instrumentation-ruby-actionmailer.yml new file mode 100644 index 000000000000..b128f9959b31 --- /dev/null +++ b/data/registry/instrumentation-ruby-actionmailer.yml @@ -0,0 +1,22 @@ +title: OpenTelemetry ActionMailer Instrumentation +registryType: instrumentation +language: ruby +tags: + - action + - mailer + - instrumentation + - ruby +urls: + repo: https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/main/instrumentation/action_mailer +license: Apache 2.0 +description: + The ActionMailer instrumentation is a community-maintained instrumentation for + the ActionMailer portion of the [Ruby on Rails][rails-home] web-application + framework. +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 +package: + registry: gems + name: opentelemetry-instrumentation-action_mailer + version: 0.1.0 diff --git a/data/registry/instrumentation-ruby-active-job.yml b/data/registry/instrumentation-ruby-active-job.yml index 1daa7a839536..876bfcc9eb01 100644 --- a/data/registry/instrumentation-ruby-active-job.yml +++ b/data/registry/instrumentation-ruby-active-job.yml @@ -15,4 +15,4 @@ createdAt: 2020-11-09 package: registry: gems name: opentelemetry-instrumentation-active_job - version: 0.7.2 + version: 0.7.3 diff --git a/data/registry/instrumentation-ruby-awslambda.yml b/data/registry/instrumentation-ruby-awslambda.yml new file mode 100644 index 000000000000..889a21542547 --- /dev/null +++ b/data/registry/instrumentation-ruby-awslambda.yml @@ -0,0 +1,22 @@ +title: OpenTelemetry AWS-Lambda Instrumentation +registryType: instrumentation +language: ruby +tags: + - aws + - lambda + - instrumentation + - ruby +urls: + repo: https://github.com/open-telemetry/opentelemetry-ruby-contrib/tree/main/instrumentation/aws_lambda +license: Apache 2.0 +description: + The OpenTelemetry `aws-lambda` gem is a community-maintained instrumentation + for [AWS Lambda + functions](https://docs.aws.amazon.com/lambda/latest/dg/ruby-handler.html). +authors: + - name: OpenTelemetry Authors +createdAt: 2024-07-08 +package: + registry: gems + name: opentelemetry-instrumentation-aws_lambda + version: 0.1.0 diff --git a/data/registry/log-bridge-go-logrus.yml b/data/registry/log-bridge-go-logrus.yml new file mode 100644 index 000000000000..84c0ca8fc8e5 --- /dev/null +++ b/data/registry/log-bridge-go-logrus.yml @@ -0,0 +1,17 @@ +# cSpell:ignore sirupsen logrus otellogrus +title: logrus log bridge +registryType: log-bridge +language: go +tags: + - logrus + - log-bridge + - go +license: Apache 2.0 +description: + Package otellogrus provides an OpenTelemetry log bridge for + `github.com/sirupsen/logrus`. +authors: + - name: OpenTelemetry Authors +urls: + repo: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otellogrus +createdAt: 2024-05-21 diff --git a/data/registry/log-bridge-go-slog.yml b/data/registry/log-bridge-go-slog.yml new file mode 100644 index 000000000000..762fd5f7ad55 --- /dev/null +++ b/data/registry/log-bridge-go-slog.yml @@ -0,0 +1,16 @@ +# cSpell:ignore otelslog +title: slog log bridge +registryType: log-bridge +language: go +tags: + - slog + - log-bridge + - go +license: Apache 2.0 +description: + Package otelslog provides an OpenTelemetry log bridge for `log/slog`. +authors: + - name: OpenTelemetry Authors +urls: + repo: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelslog +createdAt: 2024-04-05 diff --git a/data/registry/log-bridge-go-zap.yml b/data/registry/log-bridge-go-zap.yml new file mode 100644 index 000000000000..1a989b0bbaaf --- /dev/null +++ b/data/registry/log-bridge-go-zap.yml @@ -0,0 +1,16 @@ +# cSpell:ignore uber otelzap +title: zap log bridge +registryType: log-bridge +language: go +tags: + - zap + - log-bridge + - go +license: Apache 2.0 +description: + Package otelzap provides an OpenTelemetry log bridge for `go.uber.org/zap`. +authors: + - name: OpenTelemetry Authors +urls: + repo: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelzap +createdAt: 2024-07-22 diff --git a/data/registry/log-bridge-go-zerolog.yml b/data/registry/log-bridge-go-zerolog.yml new file mode 100644 index 000000000000..25b689d44cdf --- /dev/null +++ b/data/registry/log-bridge-go-zerolog.yml @@ -0,0 +1,17 @@ +# cSpell:ignore zerolog otelzerolog +title: zerolog log bridge +registryType: log-bridge +language: go +tags: + - zerolog + - log-bridge + - go +license: Apache 2.0 +description: + Package otelzerolog provides an OpenTelemetry log bridge for + `github.com/rs/zerolog`. +authors: + - name: OpenTelemetry Authors +urls: + repo: https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelzerolog +createdAt: 2024-07-22 diff --git a/hugo.yaml b/hugo.yaml index 72b78bf57eed..4521db1c1af7 100644 --- a/hugo.yaml +++ b/hugo.yaml @@ -20,6 +20,11 @@ languages: languageName: 日本語 (Japanese) params: description: OpenTelemetryプロジェクト公式サイト + pt: # cSpell:ignore Português Projeto + languageName: Português + languageCode: pt-BR + params: + description: Site do Projeto OpenTelemetry zh: languageName: 中文 (Chinese) languageCode: zh-cn @@ -263,6 +268,19 @@ module: target: content/docs lang: zh + ## pt + - source: content/pt + target: content + lang: pt + # fallback pages + - source: content/en/announcements + target: content/announcements + lang: pt + - excludeFiles: specs/* + source: content/en/docs + target: content/docs + lang: pt + ## static - source: static target: static diff --git a/layouts/partials/ecosystem/registry/entry.html b/layouts/partials/ecosystem/registry/entry.html index 488269f342f4..7107e29ac8ba 100644 --- a/layouts/partials/ecosystem/registry/entry.html +++ b/layouts/partials/ecosystem/registry/entry.html @@ -48,7 +48,7 @@ "icon" "fab fa-rust") -}} - {{ $isNativ := and (eq .registryType "instrumentation") (.isNative) }} + {{ $isNative := and (eq .registryType "instrumentation") (.isNative) }} {{ $isFirstParty := and (eq .registryType "instrumentation") (.isFirstParty) }} {{ $currentTime := (time now) -}} {{ $delta := $currentTime.Sub (time.AsTime .createdAt) -}} @@ -64,7 +64,7 @@ {{ if $isNew -}} {{ $highlightStyle = "border-info" -}} {{ end -}} - {{ if $isNativ -}} + {{ if $isNative -}} {{ $highlightStyle = "border-success" -}} {{ end -}} {{ if $isFirstParty -}} @@ -87,7 +87,7 @@

{{ if $isNew -}} new {{ end -}} - {{ if $isNativ -}} + {{ if $isNative -}} native {{ end -}} {{ if $isFirstParty -}} @@ -205,4 +205,4 @@

Quick Install
{{- end -}} - {{ end -}} \ No newline at end of file + {{ end -}} diff --git a/static/refcache.json b/static/refcache.json index e6be91010c15..aa6044a2accf 100644 --- a/static/refcache.json +++ b/static/refcache.json @@ -51,6 +51,10 @@ "StatusCode": 206, "LastSeen": "2024-06-04T17:29:49.77219755+02:00" }, + "https://7asecurity.com/reports/pentest-report-opentelemetry.pdf": { + "StatusCode": 206, + "LastSeen": "2024-07-22T14:20:49.972502516Z" + }, "https://access.redhat.com/products/ansible-tower-red-hat": { "StatusCode": 200, "LastSeen": "2024-01-18T08:05:55.59597-05:00" @@ -995,6 +999,10 @@ "StatusCode": 206, "LastSeen": "2024-01-18T08:52:54.099142-05:00" }, + "https://docs.aws.amazon.com/lambda/latest/dg/ruby-handler.html": { + "StatusCode": 206, + "LastSeen": "2024-07-10T17:01:44.550734457Z" + }, "https://docs.aws.amazon.com/lambda/latest/dg/services-xray.html": { "StatusCode": 206, "LastSeen": "2024-01-30T16:14:28.171642-05:00" @@ -1239,6 +1247,10 @@ "StatusCode": 200, "LastSeen": "2024-01-30T06:05:57.197702-05:00" }, + "https://docs.gradle.org/current/userguide/dependency_resolution.html#sec:version-conflict": { + "StatusCode": 206, + "LastSeen": "2024-07-23T10:18:05.857983751+02:00" + }, "https://docs.greptime.com/user-guide/clients/otlp": { "StatusCode": 200, "LastSeen": "2024-01-30T15:24:43.194115-05:00" @@ -1315,6 +1327,10 @@ "StatusCode": 206, "LastSeen": "2024-02-17T16:19:07.140338072Z" }, + "https://docs.micrometer.io/micrometer/reference/implementations/otlp.html": { + "StatusCode": 206, + "LastSeen": "2024-07-15T14:03:44.726797719+02:00" + }, "https://docs.microsoft.com/aspnet/core": { "StatusCode": 200, "LastSeen": "2024-01-18T08:53:25.01054-05:00" @@ -3447,6 +3463,10 @@ "StatusCode": 200, "LastSeen": "2024-07-02T05:06:30.374629805Z" }, + "https://github.com/open-telemetry/opentelemetry-collector/releases/tag/cmd%2Fbuilder%2Fv0.105.0": { + "StatusCode": 200, + "LastSeen": "2024-07-17T10:45:43.412272909Z" + }, "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" @@ -3855,6 +3875,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:55:35.674322-05:00" }, + "https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues": { + "StatusCode": 200, + "LastSeen": "2024-07-15T14:03:44.295338372+02:00" + }, "https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues/7413": { "StatusCode": 200, "LastSeen": "2024-02-22T15:50:20.20139382Z" @@ -6491,6 +6515,10 @@ "StatusCode": 206, "LastSeen": "2024-06-04T11:05:52.856746897+02:00" }, + "https://opentelemetry.io/docs/instrumentation/php/automatic/": { + "StatusCode": 206, + "LastSeen": "2024-07-10T17:01:42.679794935Z" + }, "https://opentelemetry.io/docs/languages/cpp/exporters/": { "StatusCode": 206, "LastSeen": "2024-04-30T09:31:38.598060401Z" @@ -6567,6 +6595,18 @@ "StatusCode": 206, "LastSeen": "2024-05-15T19:23:47.920456821+03:00" }, + "https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#capturing-http-request-and-response-headers": { + "StatusCode": 206, + "LastSeen": "2024-07-18T12:15:23.404682814Z" + }, + "https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#configuring-known-http-methods": { + "StatusCode": 206, + "LastSeen": "2024-07-18T12:15:25.914328974Z" + }, + "https://opentelemetry.io/docs/zero-code/java/agent/instrumentation/http/#enabling-experimental-http-telemetry": { + "StatusCode": 206, + "LastSeen": "2024-07-18T12:15:30.126385341Z" + }, "https://opentelemetry.io/ecosystem/integrations/": { "StatusCode": 206, "LastSeen": "2024-03-19T10:16:49.992495889Z" @@ -7607,6 +7647,14 @@ "StatusCode": 200, "LastSeen": "2024-05-10T11:02:15.508410781Z" }, + "https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelzap": { + "StatusCode": 200, + "LastSeen": "2024-07-18T09:04:56.296529985Z" + }, + "https://pkg.go.dev/go.opentelemetry.io/contrib/bridges/otelzerolog": { + "StatusCode": 200, + "LastSeen": "2024-07-22T08:21:47.06167143Z" + }, "https://pkg.go.dev/go.opentelemetry.io/contrib/detectors/aws/ec2": { "StatusCode": 200, "LastSeen": "2024-05-27T15:24:39.997553+02:00" @@ -8023,6 +8071,10 @@ "StatusCode": 200, "LastSeen": "2024-01-22T17:25:05.672589+01:00" }, + "https://rubygems.org/gems/opentelemetry-instrumentation-action_mailer": { + "StatusCode": 200, + "LastSeen": "2024-07-10T17:01:43.869580741Z" + }, "https://rubygems.org/gems/opentelemetry-instrumentation-action_pack": { "StatusCode": 200, "LastSeen": "2024-01-22T15:38:22.124468+01:00" @@ -8051,6 +8103,10 @@ "StatusCode": 200, "LastSeen": "2024-01-16T17:59:00.831876+01:00" }, + "https://rubygems.org/gems/opentelemetry-instrumentation-aws_lambda": { + "StatusCode": 200, + "LastSeen": "2024-07-10T17:01:44.79848698Z" + }, "https://rubygems.org/gems/opentelemetry-instrumentation-aws_sdk": { "StatusCode": 200, "LastSeen": "2024-01-22T15:38:27.079086+01:00" @@ -9679,6 +9735,10 @@ "StatusCode": 200, "LastSeen": "2024-01-18T19:55:46.046387-05:00" }, + "https://www.ostif.org/otel-audit-complete/": { + "StatusCode": 200, + "LastSeen": "2024-07-22T14:20:47.739450411Z" + }, "https://www.otelbin.io/": { "StatusCode": 200, "LastSeen": "2024-01-30T16:14:44.039011-05:00"