Ben Lambert

Hey :wave: Thanks for raising this! Yep, it's indeed a problem, and something that we want to make easier to enable. Little bit of background here, is that the `user`...

Been thinking about this a little bit, but I'm wondering if something like `plugin` scoped `integrations` config could work best. ```yaml integrations: plugins: catalog: github: - host: github.com token: abc...

Needs a rebase too :pray:

Thanks :tada:

@SonilPro, are you using new backend system or the legacy? Are you making sure to put this code in the `packages/backend/src` and importing it as early as possible to avoid...

@SonilPro can you try moving around the imports somewhat. Put the initialization code in another file, and require that file first in `backend/src/index.ts` rather than requiring other imports? Does that...

Oh right, that makes more sense. I wonder if we can use something like this: https://github.com/open-telemetry/opentelemetry-js-contrib/tree/main/metapackages/auto-instrumentations-node#usage-auto-instrumentation to require the `auto-instrumentations` first before the init. Try passing in `NODE_OPTIONS` and see...

Have you tried doing both?

@CasperGN the scaffolder metrics aren't on OpenTelemetry I think yet - They're still using prom-client I believe. https://github.com/backstage/backstage/blob/685b693fc0e9ce5d59f5883e1c4a7e43bd51d111/plugins/scaffolder-backend/src/util/metrics.ts#L29-L73 This will all need updating to use `opentelemetry/metrics` instead.

So if I follow the current guide, by putting `import './instrumentaton'` at the top of `packages/backend/src/index.ts` as line 1, then I get instrumentation like `http.server.duration` and `http.client.duration`. What other instrumentation...