Underlying implementation of Evaluate JSON Path Expression Assertion

Hi CA team, we're seeing Evaluate JSON Path Expression Assertion taking about 30+ milliseconds to process a relative small json string. Our SLAs indicate that gateway process time needs to be under 10 milliseconds. We're wondering if we can write a custom assertion that can improve the performance of this assertion. We want to know the underlying implementation, or any technical documentation you have of this assertion before writing our own.

Please let me know if we need to reach out to support team for this request.

If you feel that the assertion is not performing well, I would suggest that you load up a copy of the assertion with the JSON Path and a sample payload being analyzed so we can test in our lab. Also please provide back the version of the gateway being used.

If you feel that the assertion is not performing well, I would suggest that you load up a copy of the assertion with the JSON Path and a sample payload being analyzed so we can test in our lab. Also please provide back the version of the gateway being used.