Issue with OTEL Metrics from Helm Chart

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

User reports unexpected behavior with OTEL metrics in Airbyte Helm chart 1.1.1, receiving a metric from the server instead of the worker as expected.


Question

Hello everyone!

We are using airbyte helm chart 1.1.1 and I see a really strange behavior about OTEL metrics setup
as an example:

      MetricEmittingApps.WORKER,
      "attempt_created_by_release_stage",
      "increments when a new attempt is created. attempts are double counted as this is tagged by release stage."),```
but at the same time, I'm receiving that metric not from the worker, but from the server...

any ideas / recommendations?

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1733230118701519) if you want
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
['otel-metrics', 'helm-chart', 'airbyte', 'attempt-created-by-release-stage', 'worker', 'server']
</sub>
2

Please report this as a Github issue.