-
Notifications
You must be signed in to change notification settings - Fork 419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
appsec/api-security: http request schema collection and sensitive data scanning #2381
Conversation
BenchmarksBenchmark execution time: 2023-12-12 09:49:00 Comparing candidate commit 9aa2e40 in PR branch Found 0 performance improvements and 3 performance regressions! Performance is the same for 36 metrics, 2 unstable metrics. scenario:BenchmarkSingleSpanRetention/no-rules-24
scenario:BenchmarkSingleSpanRetention/with-rules/match-all-24
scenario:BenchmarkSingleSpanRetention/with-rules/match-half-24
|
a0f4b9f
to
1e1d3ff
Compare
bb3eb6f
to
1e9e091
Compare
f977c1d
to
379fed1
Compare
System-tests workflow: https://github.com/DataDog/dd-trace-go/actions/runs/7126006639 |
156e93e
to
b6f411c
Compare
b6f411c
to
b30e192
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job.
I did a couple of suggestions. Only one is major: the use of AddAPISecurityTags
in the request path instead of being at the end of the request like we do for events.
d4d356c
to
8816481
Compare
Co-authored-by: Romain Marcadier <romain@datadoghq.com>
cf59a5a
to
5402395
Compare
Co-authored-by: Julio Guerra <julio@datadog.com>
What does this PR do?
Tags()
Motivation
Reviewer's Checklist
For Datadog employees:
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!