SG-Dynatrace Common Failure Scenarios [v.1.11]Below section will help solve customer issues we encountered so far with Service Graph Connector for Observability - Dynatrace [v1.11] Issue #1:Flow actions failing with error "Response size exceeds limit" For a given response payload from a REST step it is possible that it can exceed the default payload size. The execution context would contain an error like the following: ..failed with error: com.snc.process_flow.exception.OpException: Response size exceeds limit, allowed :xxxxx actual size: xxxxx Cause: REST response Payload size might exceed the allowed limit of 5MB (5120KB)Resolution: To address that error message, add the respective properties to the [sys_properties] table for the given step being used.REST Property:glide.pf.rest.response_payload_max_sizeNote 1: Please note that the value is in KB, so 10MB = 10240 (10 * 1024KB).Note 2: If the respective flow is configured to use a MID Server, you would add the respective property to the MID Server properties table and not [sys_properties].The maximum value that can be specified is: 10240Please Note: If the response attachment is more than 10MB, then the Flow Action will need to utilise "Save As Attachment" (under "Response Handling"), to accomodate and process larger payload we need to do the following Please deploy the following update set attached with the KB in the below order [SG-Dynatrace_Common_Issue_Fixes_v1.0.xml] Try to run the integration one more time, check the result and if you get the same error as before, try the below step (Otherwise it's not needed)Open the connection record with name "Dynatrace Connection", in the related list & update the connection properties record with name "saveRESTResponseAsAttachment" to "true" and run the integration. Issue #2:Kubernetes Data Sources failing with error "java.lang.ClassCastException" This error is commonly seen when a payload few special characters as incoming response object key(s)For example: "helm.sh/chart":"xxxxxxxxxxxxxxxxxxxxxxxx", "app.kubernetes.io/managed-by":"yyyyyyyyyyyyy" Cause: System not able to process these special characters like "-" etc.,Resolution:Clean up unwanted keys coming as part of the payload, which is again not used for processing. Please Note: In the import log you may see this exception Please deploy the following update set attached with the KB in the below order [SG-Dynatrace_Common_Issue_Fixes_v1.0.xml] Try to run the integration one more time. If you are still facing issue(s), please reach out to support.Most of these issues will be fixed in the upcoming version of the Service Graph Connector for Observability - Dynatrace [v1.12]Next Release is on May 2025.