Skip to content

Docker API call wrongly assigned to service #1035

@mariomac

Description

@mariomac

How to reproduce:

  • Run the docker-compose-multiexec.yml compose file
  • In a terminal, keep running docker ps (e.g. watch docker ps)

Don't invoke any of the services defined in docker-compose-multiexec.yml. The Docker API client will be instrumented and wrongly assigned to python-service (the service running in port 7773).

The emitted metrics show /v1.43/containers/json invoked in python-services (port 7773).

http_client_request_body_size_bytes_sum{host_id="9a2f38c9c2f9", host_name="beyla", http_request_method="GET", http_response_status_code="200", http_route="/v1.43/containers/json", instance="beyla:472", job="multi-k/python-service", os_type="linux", server_address="docker", server_port="4", service_instance_id="beyla:472", service_name="python-service", service_namespace="multi-k", telemetry_sdk_language="go", telemetry_sdk_name="opentelemetry-ebpf-instrumentation", telemetry_sdk_version="unset", url_path="/v1.43/containers/json"}
traces_spanmetrics_calls_total{host_id="9a2f38c9c2f9", host_name="beyla", instance="beyla:472", job="multi-k/python-service", os_type="linux", service_instance_id="beyla:472", service_name="python-service", service_namespace="multi-k", source="obi", span_kind="SPAN_KIND_CLIENT", span_name="GET /v1.43/containers/json", status_code="STATUS_CODE_UNSET", telemetry_sdk_language="go", telemetry_sdk_name="opentelemetry-ebpf-instrumentation", telemetry_sdk_version="unset"}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions