-
Notifications
You must be signed in to change notification settings - Fork 399
Enable Endpoint Collection feature by default #4931
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
Conversation
endpoint_collection_spec.rb
branch 'appsec-enable-endpoint-collection-by-default' on '4ab26d0b58'.
endpoint_collection_spec.rb
endpoint_collection_spec.rb
|
✅ Tests 🎉 All green!❄️ No new flaky tests detected 🎯 Code Coverage 🔗 Commit SHA: 8f44c50 | Docs | Was this helpful? Give us feedback! |
BenchmarksBenchmark execution time: 2025-10-02 16:09:06 Comparing candidate commit df5562b in PR branch Found 0 performance improvements and 2 performance regressions! Performance is the same for 42 metrics, 2 unstable metrics. scenario:profiling - Allocations ()
scenario:tracing - Propagation - Trace Context
|
spec/datadog/appsec/integration/contrib/rails/endpoint_collection_spec.rb
Outdated
Show resolved
Hide resolved
|
The title of this PR doesn't match the first statement in the description though the PR contains both changes - should the title reflect the feature being enabled by default? |
|
@p-datadog thanks, good catch! The PR was actually auto-generated from my commit title, and I forgot to change it. |
endpoint_collection_spec.rb
|
👍 |
What does this PR do?
It enables Endpoint Collection by default for AppSec users. I also adds a safeguard that rescues exceptions during routes serialization.
Motivation:
We want this feature to be enabled by default for AppSec users.
Change log entry
None. This change is internal.
Additional Notes:
I also added a
rescueto the method for reporting routes as a safeguard - in case Rails changes some internals and route serialization will start raising errors.APPSEC-59521
How to test the change?
CI