Getting Data In

| rest /services/search/jobs Source?

andrewkenth
Communicator

Is there a way to find the source of a job that ran? For instance is it on a dashboard or is it a preconfigured report and if so show the proper names of the items (report name, dashboard panel name)? It seems there is only a title (label) when it's run on the scheduler.

| rest /services/search/jobs
Tags (2)
0 Karma

somesoni2
Revered Legend

Try this: (just per my understanding, may need revision)

| rest /services/search/jobs | eval Job_type=if(delegate="scheduler","Scheduled","Adhoc")| rex field=id "(?<jobId>[^//]*)$"| rename eai:acl.app as App | eval searchType=case(isnum(jobId),"Regular Search", LIKE(jobId,"sch%"), "Scheduled Search",1=1,"Dashboard Search") | where searchType="Scheduled Search" | eval searchType=if(mvindex(split(jobId,"_"),5)==label AND isBatchModeSearch=1,"Scheduled Report", searchType) | table Job_type, App, label , searchType , updated
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...