Skip to content
Merged
Changes from all commits
Commits
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
42 changes: 41 additions & 1 deletion modules/otel-config-instrumentation.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ include::snippets/technology-preview.adoc[leveloffset=+1]

|`configPath`
|Location of the Apache HTTP Server configuration.
|/usr/local/apache2/conf
|`/usr/local/apache2/conf`

|`env`
|Environment variables specific to the Apache HTTP Server.
Expand Down Expand Up @@ -397,6 +397,46 @@ instrumentation.opentelemetry.io/container-names: "<container_1>,<container_2>"
The Go auto-instrumentation does not support multi-container auto-instrumentation injection.
====

[id="otel-multi-container-pods-multi-instrumentations_{context}"]
== Multi-container pods with multiple instrumentations

Injecting instrumentation for an application language to one or more containers in a multi-container pod requires the following annotation:

[source,yaml]
----
instrumentation.opentelemetry.io/<application_language>-container-names: "<container_1>,<container_2>" # <1>
----
<1> You can inject instrumentation for only one language per container. For the list of supported `<application_language>` values, see the following table.

.Supported values for the `<application_language>`
[options="header"]
[cols="a, a"]
|===
|Language |Value for `<application_language>`

|ApacheHTTPD
|`apache`

|DotNet
|`dotnet`

|Java
|`java`

|NGINX
|`inject-nginx`

|NodeJS
|`nodejs`

|Python
|`python`

|SDK
|`sdk`

|===

[id="otel-using-instrumentation-cr-with-service-mesh_{context}"]
== Using the instrumentation CR with Service Mesh

Expand Down