Security

How to delete a private orphaned search of a user?

nishantskhsbc
Explorer

Hi,

I created an alert for monitoring orphaned enabled searches . It is getting saved searches for private searches of user who are deleted.
Now i don't know how to get them deleted.

My question is that, should i be even worried about them. Since they are private searched and user is deleted it wouldn't be running. Also, is it is not running why is it showing enabled.
If i should be worried how i can delete it. Since it is not showing in the place where all saved search are shown.?

0 Karma
1 Solution

harsmarvania57
Ultra Champion

Hi,

I'll suggest to create local user with same userid who were deleted and then remove private searches associated with those users & then remove those locally created user OR re-assign those private searches to other users and then remove it.

To remove it from your environment or not, I'll suggest to tidy up your environment. In longer run it will help a lot.

View solution in original post

harsmarvania57
Ultra Champion

Hi,

I'll suggest to create local user with same userid who were deleted and then remove private searches associated with those users & then remove those locally created user OR re-assign those private searches to other users and then remove it.

To remove it from your environment or not, I'll suggest to tidy up your environment. In longer run it will help a lot.

Get Updates on the Splunk Community!

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...

Real-Time Fraud Detection: How Splunk Dashboards Protect Financial Institutions

Financial fraud isn't slowing down. If anything, it's getting more sophisticated. Account takeovers, credit ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...