Getting Data In

Will a delayed report affect the next report?

hhhwang
Explorer

There are reports that run every 0 and 30 minutes. And there's a lot of reports that start every 5 minutes, 35 minutes. If the report that ran at 5 minutes is delayed and ends at 35 minutes, will the report that ran at 30 minutes have an effect?

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

gcusello
SplunkTrust
SplunkTrust

Hi @hhhwang,

if the job of the previous report is still running when the new report start, you'll have two jobs that runs at the same time.

If you have sufficient resources in your system you'll have no problems.

If you haven't sufficient resources, the new report will start at the end of the previous, but in this case, you have to analyze your system because you have a problem!

You can monitor the resources status of your system using the Monitoring Console.

Ciao.

Giuseppe

View solution in original post

gcusello
SplunkTrust
SplunkTrust

Hi @hhhwang,

if the job of the previous report is still running when the new report start, you'll have two jobs that runs at the same time.

If you have sufficient resources in your system you'll have no problems.

If you haven't sufficient resources, the new report will start at the end of the previous, but in this case, you have to analyze your system because you have a problem!

You can monitor the resources status of your system using the Monitoring Console.

Ciao.

Giuseppe

hhhwang
Explorer

Thank you for your answer.

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @hhhwang ,

good for you, see next time!

Please accept one answer for the other people of Community

Ciao and happy splunking

Giuseppe

P.S.: Karma Points are appreciated 😉

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

Note: This post outlines a proposed architecture and serves as an interest check. If we secure commitments ...