Skip to content
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

Jump to bottom

Java agent config: link into local spec pages #1474

Merged
merged 1 commit into from
Jun 22, 2022
Merged

Java agent config: link into local spec pages #1474

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.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 6 additions & 5 deletions content/en/docs/instrumentation/java/automatic/agent-config.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Agent Configuration
linkTitle: Configuration
weight: 2
spelling: cSpell:ignore autoconfiguration Autoconfiguration Dotel HSET javaagent serverlessapis Servlet servlet
---

> <h3>NOTE: subject to change!</h3>
Expand Down Expand Up @@ -71,9 +72,9 @@ Common settings that apply to multiple instrumentations at once.

### Peer service name

The [peer service name](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/span-general.md#general-remote-service-attributes)
The [peer service name](/docs/reference/specification/trace/semantic_conventions/span-general/#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](https://github.com/open-telemetry/opentelemetry-specification/tree/main/specification/resource/semantic_conventions#service)
the [resource](/docs/reference/specification/resource/semantic_conventions/#service)
for the local service.

{{% config_option name="otel.instrumentation.common.peer-service-mapping" %}}
Expand Down Expand Up @@ -116,7 +117,7 @@ to disable it:
### Capturing HTTP request and response headers

You can configure the agent to capture predefined HTTP headers as span attributes, according to the
[semantic convention](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/semantic_conventions/http.md#http-request-and-response-headers).
[semantic convention](/docs/reference/specification/trace/semantic_conventions/http/#http-request-and-response-headers).
Use the following properties to define which HTTP headers you want to capture:

{{% config_option name="otel.instrumentation.http.capture-headers.client.request" %}}
Expand Down Expand Up @@ -305,11 +306,11 @@ 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](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind)
[SpanKind.Internal](/docs/reference/specification/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](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/trace/api.md#spankind)
[SpanKind.Server](/docs/reference/specification/trace/api/#spankind)
span.

{{% config_option
Expand Down