zeffron

What's preventing latency from working across multiple machines? With PTP to synchronize, submillisecond resolution should still be possible cross machines, which would be useful.

That makes sense, thanks!

For us, this is related to #756 in that the synthetics are what we'd like to be able to tag. However, I don't believe this should _depend on_ #756. It...

> Update from the team: We are currently in the process of migrating Synthetics to the new API's. So you can soon expect a better solution than `sleep` 😅 Thanks...

> do not recommend by default adding CAP_SYS_ADMIN (or CAP_NET_ADMIN which I would think would also be needed for some of this sort of thing) to the packaging. IMHO, we...

Also, it appears the workaround documented to close #1987 is incomplete. In addition to using `terraform rm` on the `newrelic_synthetics_monitor_script` resource, it also needs to be applied to the associated...

Here is the script I'm using to do migration, in case it helps anyone else (it takes the Terraform workspace as its only argument): ```bash #!/bin/bash set -ue -o pipefail...

@mbazhlekova I have no issue with that, but it's not tested outside of my specific use case, and doesn't have safeguards in case of errors or anything. So I'm not...

Is there an ETA for when this will be resolved? We're now encountering this issue when using only public location. The Terraform provider should not be relying on a fix...

Disagree. I included an explanation of what Terraform can do to work around this in my original description: > It should check if the monitor creation was actually successful and...