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.

[R_v_Engelen · Accepted solution]

Are there any plans that you're aware of to have this limitation removed in the near future? Using a service user only works if you have a small set of users on your platform that can make these AD. We have opened up the flatform to thousands of users across hundreds of teams. The service user would mean restricting access to the app and having a dedicated team create and maintain these configs, which is exactly what we are trying to avoid

[O11y_Noob]

anyone who is creating the DAD can set the service user as a Actor and that will overcome this problem 

[O11y_Noob · Accepted solution]

hi @AK , we have changed the actor of the DAD alerts to a Service user and it will work even with owner who has not available as a user and even after they left , dont have to create the alert again , in the advance setting below the query you can see Actor option , once you have the Service user you will see it popping for every DAD alert , as a best practice you can set the service user for all alerts so it will be working even after the user who creates the DAD leaves 

[O11y_Noob]