Marc Pichler

@dyladan are you planning to use this for the semconv update in the http instrumentation? :thinking: It adds to the public interface of `@opentelemetry/core` so I'd like to be extra-sure...

> Those factory-functions could be introduced in the 2.x line, slowing deprecating (but not removing) the class-based creation, leading up to 3.0. Yes that was also my thinking - doing...

marking as `needs:refinement` as this needs to be broken down into smaller chunks of work.

Reopened this as the fix for it might've broken a common case where the interval is set but the timeout is not. We may have to look into alternative ways...

@martinkuba friendly ping 🙂 Trying to figure out if there's still appetite to land this feature 🤔

Hi @metcoder95 - this is great news! We're super happy to see this being officially instrumented by fastify authors 🎉 I'll sync with the other maintainers today how we go...

> I'll sync with the other maintainers today how we go about deprecating the component - I'll document what we talked about here. Alright, this is the full plan: -...

@dormesica the way I understand `fastify@4`'s LTS support [ends June 30, 2025](https://fastify.dev/docs/latest/Reference/LTS/#schedule) - so that'd be 3 months on top of what's the current plan. I'd be okay with keeping...

@metcoder95 yep, makes sense. I'll change the PR to keep it around until June 30 then. Thanks for the feedback 🙂 Edit: PRs updated.

Thanks for answering this @t2t2. This is correct, there's no exception to record here as fetch does not throw. Closing this issue.