Dashboards & Visualizations

help on loadjob command

jip31
Motivator

Hello

In my dashboard, I use loadjob command in order to call report every hour
I done this on my local machine
Every is working but just my computer is switched on since 2 or 3 hours
At the starting, when I execute my dashboard, I have always the message below:
Error in 'SearchOperator:loadjob': Cannot find artifacts for savedsearch_ident
Is there a workaround in order to avoid this message please?
Thanks

Tags (1)
0 Karma
1 Solution

iamarkaprabha
Contributor

Hi ,

Can you check on your job scheduler if today's run of that job has been completed or not.
The error you are getting maybe because of that . It can be possible that the job gets completed and returned 0 results.
or The job gets skipped for todays run

View solution in original post

iamarkaprabha
Contributor

Hi ,

Can you check on your job scheduler if today's run of that job has been completed or not.
The error you are getting maybe because of that . It can be possible that the job gets completed and returned 0 results.
or The job gets skipped for todays run

jip31
Motivator

hi
for the moment job has not been completed
it will be done at 8:00
what i dont understand is why the history of the dashboard is not saved

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...