You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The operator can inject and configure OpenTelemetry auto-instrumentation libraries. Currently Apache HTTPD, DotNet, Go, Java, Nginx, NodeJSand Python are supported.
222
+
The operator can inject and configure OpenTelemetry auto-instrumentation libraries. Currently Apache HTTPD, DotNet, Go, Java, Nginx, NodeJS, Python and PHP are supported.
223
223
224
224
To use auto-instrumentation, configure an `Instrumentation` resource with the configuration for the SDK and instrumentation.
225
225
@@ -260,6 +260,13 @@ spec:
260
260
# so data must be sent to 4318 instead of 4317.
261
261
- name: OTEL_EXPORTER_OTLP_ENDPOINT
262
262
value: http://otel-collector:4318
263
+
php:
264
+
env:
265
+
# Required if endpoint is set to 4317.
266
+
# PHP autoinstrumentation uses http/proto by default
267
+
# so data must be sent to 4318 instead of 4317.
268
+
- name: OTEL_EXPORTER_OTLP_ENDPOINT
269
+
value: http://otel-collector:4318
263
270
EOF
264
271
```
265
272
@@ -307,6 +314,12 @@ instrumentation.opentelemetry.io/otel-dotnet-auto-runtime: "linux-x64" # for Lin
307
314
instrumentation.opentelemetry.io/otel-dotnet-auto-runtime: "linux-musl-x64"# for Linux musl based images
Go auto-instrumentation also honors an annotation that will be used to set the [OTEL_GO_AUTO_TARGET_EXE env var](https://github.com/open-telemetry/opentelemetry-go-instrumentation/blob/main/docs/how-it-works.md).
0 commit comments