feat(appsec): support transaction id header for request tracing#4124
Conversation
|
@LaurenceJJones: There are no 'kind' label on this PR. You need a 'kind' label to generate the release automatically.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
|
@LaurenceJJones: There are no area labels on this PR. You can add as many areas as you see fit.
DetailsI am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository. |
…acing Allow incoming HTTP requests to provide a custom transaction ID via X-Crowdsec-Transaction-Id header. This ID will be used for both inband and outband processing, enabling consistent request tracing across web server logs and CrowdSec logs. - Extract transaction ID from X-Crowdsec-Transaction-Id header if present - Fall back to generating UUID if header is not provided (backward compatible) - Remove header before passing to Coraza (consistent with other special headers) - Same transaction ID used for both inband and outband Coraza transactions
dda176c to
647466b
Compare
|
/kind enhancement |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #4124 +/- ##
==========================================
- Coverage 62.87% 62.85% -0.03%
==========================================
Files 464 464
Lines 33286 33290 +4
==========================================
- Hits 20929 20924 -5
- Misses 10237 10243 +6
- Partials 2120 2123 +3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
fix #3997
Allow incoming HTTP requests to provide a custom transaction ID via
X-Crowdsec-Appsec-Transaction-Idheader. This ID will be used for both inband and outband processing, enabling consistent request tracing across web server logs and CrowdSec logs.X-Crowdsec-Appsec-Transaction-Idheader if present