Open NickStallman opened 1 year ago
I'm seeing this behavior with what I believe is a reasonable configuration.
I have:
DD_TRACE_ENABLED=0
in the environment, which should be equivalent to datadog.trace.enabled = Off
datadog.appsec.enabled = Off
, but this is not exactly true.The default for datadog.appsec.enabled
depends on datadog.remote_config_enabled
, which defaults to On
. I've created a separate issue for this default in #242.
Description
It's possible to have a misconfiguration that throws some errors visibly on the website.
You get this when you have:
It's a silly configuration, however I'd expect it to throw a warning in the PHP log file when the module is loaded, and reset appsec.enabled to Off if it doesn't detect trace.enabled is On. I wouldn't expect that kind of error to be thrown on page loads.
Tested on the latest versions of ddtrace and appsec.