Skip to content

Exported Metrics

The following tables describe the metrics exported by OBI in both OpenTelemetry (OTEL) and Prometheus formats, for use within Coralogix observability workflows.

Application metrics

FamilyName (OTEL)Name (Prometheus)TypeUnitDescription
Applicationhttp.client.request.durationhttp_client_request_duration_secondsHistogramsecondsTime taken for outbound HTTP calls from client applications
Applicationhttp.client.request.body.sizehttp_client_request_body_size_bytesHistogrambytesSize of HTTP request payloads sent by clients
Applicationhttp.client.response.body.sizehttp_client_response_body_size_bytesHistogrambytesSize of HTTP responses received by clients
Applicationhttp.server.request.durationhttp_server_request_duration_secondsHistogramsecondsTime taken to process inbound HTTP requests on servers
Applicationhttp.server.request.body.sizehttp_server_request_body_size_bytesHistogrambytesSize of incoming HTTP request bodies received by servers
Applicationhttp.server.response.body.sizehttp_server_response_body_size_bytesHistogrambytesSize of outbound HTTP response bodies sent by servers
Applicationrpc.client.durationrpc_client_duration_secondsHistogramsecondsDuration of outbound gRPC service calls
Applicationrpc.server.durationrpc_server_duration_secondsHistogramsecondsDuration of inbound RPC service calls
Applicationsql.client.durationsql_client_duration_secondsHistogramsecondsTime taken for SQL client operations (Experimental)
Applicationredis.client.durationredis_client_duration_secondsHistogramsecondsTime taken for Redis client operations (Experimental)
Applicationmessaging.publish.durationmessaging_publish_durationHistogramsecondsTime taken for message publication (e.g., Kafka) (Experimental)
Applicationmessaging.process.durationmessaging_process_durationHistogramsecondsTime taken for message processing (e.g., Kafka) (Experimental)
Application Processprocess.cpu.timeprocess_cpu_time_seconds_totalCountersecondsTotal CPU time consumed, broken down by state (system/user/wait)
Application Processprocess.cpu.utilizationprocess_cpu_utilization_ratioGaugeratioCPU time usage change over time, normalized by CPU count
Application Processprocess.memory.usageprocess_memory_usage_bytesUpDownCounterbytesPhysical memory currently used
Application Processprocess.memory.virtualprocess_memory_virtual_bytesUpDownCounterbytesVirtual memory committed
Application Processprocess.disk.ioprocess_disk_io_bytes_totalCounterbytesTotal disk I/O bytes transferred
Application Processprocess.network.ioprocess_network_io_bytes_totalCounterbytesTotal network I/O bytes transferred
Networkobi.network.flow.bytesobi_network_flow_bytesCounterbytesBytes transmitted between source and destination network endpoints
Networkobi.network.inter.zone.bytesobi_network_inter_zone_bytesCounterbytesCross-zone network bytes within Kubernetes clusters (Experimental)

OBI also supports exporting Span metrics and Service Graph metrics, which can be toggled via feature configuration options.

Attribute selection for OBI metrics

Metrics and attributes follow OTEL dot.notation but are converted to Prometheus underscore_notation in Prometheus outputs.

You can customize which attributes are exposed or hidden by using the attributes->select section in the configuration.

Common attributes table

MetricsAttribute NameDefault
Application (all)http.request.methodshown
Application (all)http.response.status_codeshown
Application (all)http.routeshown if routes config exists
Application (all)k8s.daemonset.nameshown if Kubernetes metadata is on
Application (all)k8s.deployment.nameshown if Kubernetes metadata is on
Application (all)k8s.namespace.nameshown if Kubernetes metadata is on
Application (all)k8s.node.nameshown if Kubernetes metadata is on
Application (all)k8s.owner.nameshown if Kubernetes metadata is on
Application (all)k8s.pod.nameshown if Kubernetes metadata is on
Application (all)k8s.container.nameshown if Kubernetes metadata is on
Application (all)k8s.pod.start_timeshown if Kubernetes metadata is on
Application (all)k8s.pod.uidshown if Kubernetes metadata is on
Application (all)k8s.replicaset.nameshown if Kubernetes metadata is on
Application (all)k8s.statefulset.nameshown if Kubernetes metadata is on
Application (all)k8s.cluster.nameshown if Kubernetes metadata is on
Application (all)service.nameshown
Application (all)service.namespaceshown
Application (all)target.instanceshown
Application (all)url.pathhidden
Application (client)server.addresshidden
Application (client)server.porthidden
Application (process)various process-specific attributes (e.g., process.command, process.executable.path)shown if process metrics enabled
Application RPCvarious RPC attributes (rpc.method, rpc.grpc.status_code)shown
Application (server)client.addresshidden
Networknetwork-specific attributes (e.g., src.address, dst.address, iface)mostly hidden or conditional

Note: The obi.network.inter.zone.bytes metric shares the same attribute set as obi.network.flow.bytes but all are hidden by default except k8s.cluster.name, src.zone, and dst.zone.

Internal OBI metrics

OBI provides several internal Prometheus-format metrics to help monitor its own health and activity:
NameTypeDescription
obi_ebpf_tracer_flushesHistogramSize of trace groups flushed from eBPF to pipeline
obi_otel_metric_exports_totalCounterTotal metric batches sent to remote OTEL collector
obi_otel_metric_export_errors_totalCounterVecCount of OTEL metric export errors by type
obi_otel_trace_exports_totalCounterTotal trace batches sent to remote OTEL collector
obi_otel_trace_export_errors_totalCounterVecCount of OTEL trace export errors by type
obi_prometheus_http_requests_totalCounterVecPrometheus scrape endpoint request count by port and path
obi_instrumented_processesGaugeVecNumber of processes instrumented by Obi, labeled by process name
obi_internal_build_infoGaugeVecObi version information including build timestamp and commit ID