Wrong instance label on traces_.* metric

[gouthamve]

Discussed in #1481

I see this behavior in my environment as well. For every deployment, I see :<container> in the instance label but for beyla I see :number. Further, the data for this instance seems to be coming from rook and not Beyla itself. I am scraping metrics with honor_labels: true.

This with version v1.9.4

---

^{Originally posted by dscho99 December 26, 2024}
Hi Community
I'm a beginner with OpenTelemetry (otel) and Beyla.
I'm asking this question after installing the provided Helm chart.

Looking at the following metric:

traces_service_graph_request_total{client="tsdb-timescaledb", client_service_namespace="dscho-system", instance="beyla-mxk66:5289", job="dscho-system/python3.9", server="kubernetes", server_service_namespace="default", source="beyla"}

Q1. The instance label is set to beyla. What is the reason for this?

Q2. If this is the expected behavior, what is the reason for the Beyla instance being collected instead of the TSDB instance?

Q3. I couldn't find documentation related to this metric. Is there any documentation available that could provide more information?