Skip to content
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

Not possible to disable appsec codepaths #3846

Open
tommoor opened this issue Dec 5, 2023 · 0 comments
Open

Not possible to disable appsec codepaths #3846

tommoor opened this issue Dec 5, 2023 · 0 comments
Labels
appsec bug Something isn't working

Comments

@tommoor
Copy link
Contributor

tommoor commented Dec 5, 2023

This might seem like a small issue, but I'm having huge problems with this particular code path exhausting system memory which I'll file an issue for once I'm confident of reproduction steps. In the meantime being unable to disable the code from running when there is seemingly a setting to do so is problematic.

Expected behaviour

tracer.init({
  appsec: { enabled: false },
})

or

tracer.init({
  appsec: false,
})

Should prevent /appsec/ codepaths from running

Actual behaviour

RemoteConfigManager is still polling, making requests etc.

image

Here, using 43% of heap – it should be completely disabled!

image

Environment

  • Operation system: Ubuntu 4.8.4
  • Node.js version: 20 LTS
  • Tracer version: 4.20.0
  • Agent version: N/A
  • Relevant library versions:
@tommoor tommoor added the bug Something isn't working label Dec 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
appsec bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants