[AWS Cloudwatch] No test result returned.Error: Protocol error (Runtime.callFunctionOn): Target closed error about dynatrace-api

[myieye]

Hi @robbiealixsantos,

Thanks for working on this!

A couple questions:

• What version of the exporter script is being used? (As long as it wasn't removed, it should be at the top of the script. Current version is v1.0.3)
• So, effectively the canary doesn't work on the AWS side? I.e. there are no results?
• With your changes there are no more error logs and results are visible in both AWS and Dynatrace? (If that's the case, nice work! 👍)
• As much of the canary script (including the exporter script) as you're allowed to share would be helpful. (Maybe an internal ticket?)

Currently, I don't see any reason why your changes would have made a difference 🤔.

[robbiealixsantos]

Hi @myieye

• The version is v1.0.3

• At the moment the Canary test results do push to DT Synthetic side. On AWS canary side there are no results, it only returns with a "No test result returned.Error: Protocol error (Runtime.callFunctionOn): Target closed". Kind of like a false positive - results on DT side make it look OK but it shows as a failed test on Canary AWS

Pre update:

Post update:

• Will update the ticket accordingly :)

Thank you!

[RegorgG]

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries_Troubleshoot.html mentions the probable underlying problem:

Error: Protocol error (Runtime.callFunctionOn): Target closed.
This error appears if there are some network requests after the page or browser is closed. You might have forgotten to wait for an asynchronous operation. After executing your script, CloudWatch Synthetics closes the browser. The execution of any asynchronous operation after the browser is closed might cause target closed error.

[myieye]

Closing due to inactivity (and the issue likely being correctly addressed).