Open source feature flagging and experimentation platform for stress free deployments, measured impact, and smarter decisions.

GrowthBook Users

You should not include the `/metrics` part in your endpoint.  That is added automatically by the OpenTelemetry library we're using.

I think it's trying to hit `/metrics/metrics` now and that's why it's throwing a 404 error

I am getting the exact same behaviour with this

```root@growthbook-api-web-c4f677c8-wh749:/usr/local/src/app# env | grep -i otel
OTEL_EXPORTER_OTLP_ENDPOINT=<http://prometheus-pushgateway:9091>```

Hmm.  Looks like there may be some issues with using prometheus pushgateway with Open Telemetry.  <https://github.com/open-telemetry/opentelemetry-js/issues/1278>

ah ok. so the opentelemetry exporter library used in GB cannot use prometheus pushgateway as `OTEL_EXPORTER_OTLP_ENDPOINT`  if I understand correctly?

That's what it looks like.  I haven't tested this myself, so not 100% sure.   I have tested with the OTEL collector - <https://opentelemetry.io/docs/collector/> although I was sending to different destinations, not Prometheus.  They do list Prometheus as supported there, so it will likely work.

hm ok. if anything comes up on this do let us know, it would be highly appreciated

FWIW, the <https://github.com/open-telemetry/opentelemetry-js-contrib/blob/d83b57b444fa75e0518805bb7c8dcfa8b0ddcb91/detectors/node/opentelemetry-resource-detector-aws/src/detectors/AwsEksDetector.ts#L90|exception> `Process is not running on k8s` seems to be related to a check of whether the app is running *specifically* on EKS. I have no experience on `node.js` but could the library be useful only on EKS? (don't think so but just asking)