Anyone had any success with implementing Contrast security on systems that have Dynatrace enabled?
Seeing pods fail with crashloop backoffs with the below in the logs
/ 2025-02-18 05:12:10,536 [main B] INFO - java.class.version 61.0[Contrast] Tue Feb 18 05:12:11 EST 2025 Contrast not enabled. Check log for details - /contrast/data/logs/contrast_agent.logjava.lang.UnsatisfiedLinkError: 'long com.dynatrace.agent.cloudevents.CloudEventsNative.createConfig(java.lang.String)' at com.dynatrace.agent.cloudevents.CloudEventsNative.createConfig(Native Method) at com.dynatrace.agent.cloudevents.CloudEvents.createConfig(CloudEvents.java:46) at com.dynatrace.agent.introspection.cloudevents.outgoing.OutgoingHttpCloudEvents.createOkHttp(OutgoingHttpCloudEvents.java:28) at com.dynatrace.agent.introspection.cloudevents.outgoing.OutgoingHttpCloudEvents.<init>(OutgoingHttpCloudEvents.java:20) at com.dynatrace.agent.Agent.getOutgoingHttpCloudEvents(Agent.java:636
From the contrast vendor
"It sounds like Dynatrace enabled a feature called CloudNative that has caused this issue. We have had other customers back out of this change to find the issue resolved.
Ultimately the issue results from Dynatrace instrumenting our agent classes, particularly our third-party dependencies. We would recommend configuring Dynatrace to tell them to stop instrumenting classes that start with com.contrastsecurity. to help move this compatibility along"
