You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today, in certain cases Node SDK users will see warnings about a framework not being instrumented. In most cases, this is helpful because it tells you something will not work as expected, and thus it is good to let users know that something is bad.
However, there are also legimitate reasons for this. For example: #12056 (comment) if you have a version of a framework that is not (yet) supported by OTEL, like using express 5 beta.
For such cases, we should offer a way to silence these warnings, at least.
The text was updated successfully, but these errors were encountered:
Description
Today, in certain cases Node SDK users will see warnings about a framework not being instrumented. In most cases, this is helpful because it tells you something will not work as expected, and thus it is good to let users know that something is bad.
However, there are also legimitate reasons for this. For example: #12056 (comment) if you have a version of a framework that is not (yet) supported by OTEL, like using express 5 beta.
For such cases, we should offer a way to silence these warnings, at least.
The text was updated successfully, but these errors were encountered: