Bandit instrumentation #357
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1 task
|
@bryannaegele 🙏 🥳 |
bryannaegele
added
major
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This gets Bandit instrumentation in line with Otel HTTP instrumentation specification, Semantic Conventions 1.26, and Bandit's request lifecycle as improved with Bandit 1.4. In addition, Phoenix instrumentation will now be able to support Bandit (forthcoming PR).
Predicate PRs before this is wrapped up:
Resolves #308
Resolves #360
Closes #136
Relies on open-telemetry/opentelemetry-erlang#733 and #358