When you say you have set up an alert, what are your configured Trigger Conditions and then the following Alert Actions that follow? These can be found in the Edit Alert menu and looks like this. ...
See more...
When you say you have set up an alert, what are your configured Trigger Conditions and then the following Alert Actions that follow? These can be found in the Edit Alert menu and looks like this. Where does the outputlookup come into play here? I dont see it in you SPL shared but it is in the title. From just the title of this question alone it sounds like you would like to gather results and instead of storing them in a lookup to send them to a summary index via alert_action or collect command. But from the body of the question it sounds like you are just having issues seeing results of a scheduled search trigger an alert. If you run the search ad-hoc and are seeing results, then I would check Trigger conditions, the configured alert actions if the trigger conditions are met. If those look good then I would check the ownership of the Alert itself and does the owner have access to the KVStore. You should be able to look into internal logs about the status of previous runs as well with something like this. index=_internal savedsearch_name="<alert_name>"
| table _time, savedsearch_name, user, app, status, dispatch_time, run_time, result_count, alert_actions, action_time_ms where <alert_name> is the name of your alert. I also noticed on your search that you had a lot of eval doing sort of the same function, I think a foreach loop might be useful here if you want to try it out. | inputlookup path_principals_lookup
| foreach domain_id, domain_name, group, non_tier_zero_principal, path_id, path_title, principal, tier_zero_principal, user
[
| eval
<<FIELD>>=if(
isnull('<<FIELD>>'),
"NULL_<<FIELD>>",
'<<FIELD>>'
)
]
| dedup domain_id, domain_name, group, non_tier_zero_principal, path_id, path_title, principal, tier_zero_principal, user