Yep. You're overthinking it a bit. Either you have a field containing the job state (Starting/Completed) or you can create one by | eval state=case(searchmatch("Starting",_raw),"Starting",searchmatc...
See more...
Yep. You're overthinking it a bit. Either you have a field containing the job state (Starting/Completed) or you can create one by | eval state=case(searchmatch("Starting",_raw),"Starting",searchmatch("Completed"),"Completed",1=1,null()) Then you need to check the state for each separate job | stats values(state) as states by whatever_id_you_have_for_each_job (If you want to retain the jobname, which I assume is a more general clasifier than a single job identifier, add values(aJobName) to that stats command. Then you can filter to see only non-finished jobs by | where NOT states="Completed" Keep in mind that matching multivalued fields can be a bit unintuitive at first.