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
OpenTelemetry eBPF Instrumentation (OBI) provides zero-code auto-instrumentation for Kubernetes applications using eBPF technology. It automatically captures HTTP/S requests, gRPC calls, and database queries without requiring code changes or application restarts.
263
+
264
+
### Prerequisites
265
+
266
+
- Kubernetes 1.19+
267
+
- Linux kernel 5.8+ (for full eBPF support)
268
+
- Privileged security context with specific capabilities
OBI will automatically send traces to the `logzio-apm-collector` service within the cluster.
284
+
285
+
### Service Discovery
286
+
By default, OBI instruments all applications in all namespaces. Customize via `config.discovery`:
287
+
288
+
```yaml
289
+
config:
290
+
discovery:
291
+
instrument:
292
+
- k8s_namespace: "production"
293
+
exclude_instrument:
294
+
- k8s_namespace: "kube-system"
295
+
```
296
+
297
+
### Configuration Options
298
+
299
+
Override OBI settings:
300
+
301
+
```shell
302
+
--set obi.hostNetwork=true \
303
+
--set obi.network.enabled=true
304
+
```
305
+
306
+
> [!WARNING]
307
+
> OBI has limitations with gRPC and HTTP/2 protocols. See [Context Propagation Guide](https://github.com/logzio/logzio-helm/blob/master/charts/obi/CONTEXT_PROPAGATION.md) for details.
0 commit comments