How do we decide on a safe value for concurrency for Chronicle destination?
How do we decide on a safe value for concurrency for Chronicle destination? We keep seeing a log of these errors. The default value is 5
Answers
-
Are there any issues with the Chronicle side accepting data from Cribl?
0 -
The data is being eventually accepted. We did increase the concurrency from 5 to 10.
0 -
ok
0 -
I was going to ask if you increased the concurrency
0 -
But the bigger problem we are having is that we are pulling this data from an S3 bucket and then pushing to Chronicle. If we run the job as adhoc, data is discovered and collected. If we schedule the same job, the data is discovered and not collected, or the job is cancelled.
0 -
Does it give you any errors for the scheduled job?
0 -
stack:"HeartbeatMissedTaskError: taskId: collect.14 at v.<anonymous>
0 -
<@U01BVH0E872> if you have a few min, can we jump into a call. Terry and I have spent quite some time working on this but not able to figure out why scheduled job is not collecting anything
0 -
Sure
0 -
can you all jump on the call now?
0 -
yes
0 -
i'll pm you the zoom
0 -
thank you
0 -
np
0
