Protect Performance troubleshooting

  • Updated

Problem

Protect is designed to add as little overhead as possible to running applications, and should have minimal impact on performance. If enabling Protect should significantly affect an application's performance, this can often be traced back to specific inputs, endpoints, or unsupported frameworks. In order to troubleshoot Protect performance issues, we would need some information on the technologies used and some application details. In particular, we do need the following:

 

Required For All Environments

  • Operating system and version, and OS resources, such as memory, disk space, cpu and cpu core count.
  • Application language and frameworks used
  • Web or application server type and version 
  • Contrast agent type/version
  • An example of the problematic request and/or a sample payload, if applicable
  • APM flame graphs and stack traces
  • JFR collection
  • An agent DEBUG or TRACE log, if possible

 

Additional Information Required for Containerized Environments

  • Cloud host environment
  • Deployment type
  • A copy of the Dockerfile or the image you are running 
  • CPU and Memory resource allocations on the container

 

To open a support ticket, please submit this information to our online support portal.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request