Deployment Architecture

Skipped search - Is it possible to have skipped reports due to the nobody user?

robertlynch2020
Motivator

I am having a lot of skipped reports - but I think it is due to the nobody user.

Increasing the system setting in limits.conf does not have an impact on reports that runs for NOBODY.

On a beta site, I increase the number of max_hist_searches to a huge number but I still get the same errors. 

robertlynch2020_1-1649953242280.png

Other users can have unlimited, but because this role is not official am I correct to say I need to give all these alerts.

robertlynch2020_3-1649953390152.png

This is the reason I am getting. So i think if i assign the reports to a user, it will fall under a role and then it will work?

robertlynch2020_2-1649953263238.png

robertlynch2020_0-1649954206010.png

 

Labels (1)
Tags (2)
0 Karma
1 Solution

richgalloway
SplunkTrust
SplunkTrust

It's a good idea (IMO) to create a service account (or several) to use for scheduled reports.  The account can be assigned a role with higher limits than normal users so reports are less likely to be canceled.

---
If this reply helps you, Karma would be appreciated.

View solution in original post

richgalloway
SplunkTrust
SplunkTrust

It's a good idea (IMO) to create a service account (or several) to use for scheduled reports.  The account can be assigned a role with higher limits than normal users so reports are less likely to be canceled.

---
If this reply helps you, Karma would be appreciated.
Get Updates on the Splunk Community!

Admin Your Splunk Cloud, Your Way

Join us to maximize different techniques to best tune Splunk Cloud. In this Tech Enablement, you will get ...

Cloud Platform | Discontinuing support for TLS version 1.0 and 1.1

Overview Transport Layer Security (TLS) is a security communications protocol that lets two computers, ...

New Customer Testimonials

Enterprises of all sizes and across different industries are accelerating cloud adoption by migrating ...