What is a good tail sampling configuration for long running celery tasks #44573
Unanswered
skippaydevs
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I have a few celery tasks that run for a very long time (which is not the best design but it is what it is). The time they can run for is 1 hour. After that, they get killed and the SoftTimeLimitException is raised. I would like to sample traces for these tasks in 100 % of cases. For tasks that finish successfully, I want to trace only 10 % of these.
This is my configuration:
My understanding is this:
decision_wait- I want to wait for the whole trace, which is 1 hour and a bit longer to make sure the tasks failed with soft time limit get to be sampled correctlynum_traces- There are about 20 celery tasks per hour being processed, so just to be sure, this is twice the necessary sizeexpected_new_traces_per_sec- that would be about 0.005, not sure I can set float, so 1decision_cache- 8 for sampled, 80 for non_sampled, probably a bit more than necessaryDoes this configuration make sense? What is the recommended approach for sampling long running celery tasks?
Beta Was this translation helpful? Give feedback.
All reactions