Reporting

Job Summary Endpoint "Fatal Error"

robsharp67
New Member

For 95% of my jobs the summary link fails with a fatal error

"No summary is available for this job."

https://172.16.0.122:8089/services/search/jobs/scheduler__nobody__search_VG9wIGZpdmUgc291cmNldHlwZXM...

Can anyone shed any light on this situation?

Tags (2)
0 Karma

Will_Hayes
Splunk Employee
Splunk Employee

Hi, The summary is used to populate the fileds picker in the search results UI. It does not get populated for all searches, especially when the search is kicked off from the report view or scheduler like above. You can force the scheduler to add the summary info but this is an expensive operation and not recommended. What information are you interested in capturing from the job? Its possible that info already exists in the job overview page. To force your scheduled searches to create summaries add the following line below the search stanza in savedsearches.conf:

dispatch.status_buckets = 1

Get Updates on the Splunk Community!

Wondering How to Build Resiliency in the Cloud?

IT leaders are choosing Splunk Cloud as an ideal cloud transformation platform to drive business resilience,  ...

Updated Data Management and AWS GDI Inventory in Splunk Observability

We’re making some changes to Data Management and Infrastructure Inventory for AWS. The Data Management page, ...

Introducing the Splunk Community Dashboard Challenge!

Welcome to Splunk Community Dashboard Challenge! This is your chance to showcase your skills in creating ...