Skip to content

Fix a couple of links #799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
laurit merged 1 commit into from
Sep 10, 2025
Merged

Fix a couple of links #799

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions resource-detection-gcp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Resource Detection Example - GCP

An example application that shows what resource attributes will be detected by the [GCP Resource Detector](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources) and how the [Autoconfigure Resource Provider SPI](https://github.com/open-telemetry/opentelemetry-java/tree/main/sdk-extensions/autoconfigure#resource-provider-spi) automatically *attaches* the detected resource attributes to the generated telemetry.
An example application that shows what resource attributes will be detected by the [GCP Resource Detector](https://github.com/open-telemetry/opentelemetry-java-contrib/tree/main/gcp-resources) and how the [Autoconfigure Resource Provider SPI](https://opentelemetry.io/docs/languages/java/configuration/#spi-service-provider-interface) automatically *attaches* the detected resource attributes to the generated telemetry.

*For users looking to use the GCP Resource Detector with OpenTelemetry Java Agent for automatic instrumentation, refer to the instructions [here](https://opentelemetry.io/docs/languages/java/automatic/configuration/#enable-resource-providers-that-are-disabled-by-default).*

Expand Down Expand Up @@ -83,7 +83,7 @@ The detected resource attributes would depend on the environment in which the ap

## Viewing the result

The example produces a single span and uses [logging OTLP JSON exporter](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#logging-otlp-json-exporter) to export the produced span.
The example produces a single span and uses [logging OTLP JSON exporter](https://opentelemetry.io/docs/languages/java/configuration/#properties-exporters) to export the produced span.
After running the example successfully, you should see the emitted span in JSON form via JUL. It should look something like:

```
Expand Down
2 changes: 1 addition & 1 deletion telemetry-testing/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Gradle build script contains a task to download the OpenTelemetry Java Agent jar
Additionally, the OpenTelemetry is configured with properties:
- otel.exporter.otlp.protocol=http/protobuf - set up the telemetry protocol, default is grpc
- otel.metric.export.interval=5000 - set up the interval, between the start of two export attempts, default is 60s
More information about the configuration can be found in this [OpenTelemetry doc](https://github.com/open-telemetry/opentelemetry-java/blob/main/sdk-extensions/autoconfigure/README.md#otlp-exporter-span-metric-and-log-exporters).
More information about the configuration can be found in this [OpenTelemetry doc](https://opentelemetry.io/docs/languages/java/configuration/#properties-exporters).

The MockServer library is used to mock the collector web server. It's configured with port `4318`, because for
`http/protobuf` protocol, the otel exporter endpoint is by default set to `http://localhost:4318`.
Expand Down
Loading