refactor(auto-instrumentations-node): use env var utility functions to setup diagnostics logging #2778
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which problem is this PR solving?
With open-telemetry/opentelemetry-js#5443 we've introduced new utility functions for getting getting environment variables in an OTel Spec compliant manner, and we've migrated from using the old getEnv() utility function (#2708).
However, to provide an easier upgrade-path, for users of getEnv() we've also introduced a utility function to get a log level from a string, so the mapping we now do is now obsolete and we should align it with the core repo.
Refs #2774
Short description of the changes
Removed unnecessary utility function, map and tests. Replaced with new core utility functions.