Change the ownership of Davis Anomaly Detector

[AK]

Hi Folks,

By seeing the benefits of Davis anomaly detection, we started using it instead of metric events.

However, if user (who created Davis anomaly) left the organization the Davis anomaly detector created by that user goes into error state stating that, Anomaly detector failed with an unauthorized request. Fix the required permissions in the authorization settings.

Both owner and actor field started showing unknown

One way we can fix is to duplicate it and delete the old anomaly detector.

But we also have understanding that, 'service user' can be used to configure the Davis anomaly detection (please correct me if I'm wrong) and if this is the case, is there a way to change ownership of Davis anomaly detector to 'service user'?

Regards,
AK

[ChadTurner]

this is a very good ask! I wonder if you can override the owner via the API

[R_v_Engelen]

This is something that we as admins really need to be able to change.  
Whenever the original creator of the AD leaves the company for example, you're left with resources that you cannot change ownership for. Same goes for ownership of Dashboards, Notebooks and launchpads, and maybe even more I am not aware of.

[t_pawlak]

Hi,
IMO it’s currently not possible. There is no UI option and no API to change the owner of an existing Davis Anomaly Detector. If the original creator leaves the company, the detector may end up with owner/actor = unknown and fail with an unauthorized request. This is a known platform limitation, similar to Dashboards, Notebooks, and Launchpads.

Workaround:
You need to recreate (or duplicate) the detector and delete the old one.

Mabye, good practice will be create anomaly detectors using a service user to avoid ownership issues—though the exact approach may depend on your organization’s policies.