What constitutes a "massive output load" for a scheduled export?

[Lucas_K]

In the scheduled export app it has the the following lines.

The only thing to keep in mind is constraint of alerts in terms of scalability. The alert action script has a limited lifetime before it’s being killed by the scheduler. The scheduler itself is also not designed for massive output loads. It should be perfectly fine for smaller scale output, though.

https://splunkbase.splunk.com/app/2914/#/documentation

From this i infer the limitation is on search time and not actual event volume (allowing for actual available disk space ).

If a search finishes successfully via a regular rest export command it should be fine to use this? I have searches that complete within 10 mins with a resulting raw out put of ~10gb.

[Damien_Dallimor · Accepted solution]

Nothing to do with search time or event volume.

It is to do with the amount of time it takes your Modular Alert script to run before the scheduler kills the script process. So if your script, for example, takes 30 minutes to do an FTP upload , that would not be so good.

Your use case above seems fine.