WARN: Ignoring propagator because maximum reached

Issue

WARN - Ignoring propagator base-io-18 because maximum reached

Cause

Propagation events model how data flows between an untrusted source like a form parameter and a vulnerable API like SQL query.

Examples of common propagation events are string operations such as concatenation, lower casing, substring, etc.

Propagation events can be very numerous and in order to limit their impact on memory, the agent sets a cap, by default, of 250 such events per HTTP request.

If you see indications of this limit being reached in the logs, it could result in reduced accuracy.

Resolution

This default cap of 250 can be increased with an agent property. 

Environment Variable: CONTRAST__ASSESS__MAX_PROPAGATION_EVENTS
System Property: -Dcontrast.assess.max_propagation_events

The warning messages can also be safely ignored by setting the log level to ERROR, either in the UI or via the following property:   

Environment Variable: CONTRAST__AGENT__LOGGER__LEVEL=ERROR
System Property: -Dcontrast.agent.logger.level=ERROR

More information on Java agent configuration can be seen here in our documentation.