Expert
Product ManagerMatt_Whitney I'm not aware of anything explicit that says CDPs aren't supported by Synthetics. I could not find your case to double check the details, nor do I have a Synthetics test environment to test in at the moment.
If there is really a technical limitation, we'd likely have to do the same work to allow you or us to add the CDPs. There are no immediate plans to make these improvements to Synthetics.
A workaround that you could do today is, create a Service Insight, add the synthetic resource as the only member, pass the Status code thru with min or max under Metrics, and define a more specific 430 alert with a different route on that datapoint.
ExpertThanks Mike_Rodrigues - the support ticket number is 00307439. Would be happy to demonstrate the issue for you on a call if that helps.
The datasource does allow me to add a CDP, but when I do then the datasource stops polling altogether until I remove it.
Support also recommended using a service insight, which could work in the short term. But service insights are not scalable so would not be a good solution for us since we would have to manually create a service for each synthetic check in order to effectively alert. Maybe a dynamic service insight could work once they are released.
It would really benefit us and others who use synthetics if we are able to create complex datapoints, so that we don't have to use additional licensing on service insights just to do the same thing as a CDP.
Product ManagerThanks for the reference number Matt_Whitney . Given that it allows you to add a CDP but breaks collection, there's likely backend work required to get CDPs operating. This is a bigger change than something like allowing a slightly differently named module to apply to a Synthetics resource.
Dynamic Service Insights has been GA for a month or so, but not ideal from a licensing perspective for this use case.
