sentry: Implement performance tracing
A new init param and env var for our sentry integrations to enable performance tracing
traces_sample_rate
(env var SWH_SENTRY_TRACES_SAMPLE_RATE
): an optional float that defaults to None
. None
means completely disable tracing, 0.5 means enable tracing on 50% of the transactions (for example in swh-web a transaction means a whole HttpRequest cycle).
Merge request reports
Activity
assigned to @rboyer
Jenkins job DCORE/gitlab-builds #289 failed in 1 min 5 sec.
See Console Output, Blue Ocean and Coverage Report for more details.I'm wondering if the trace propagation (across multiple services) will be as magic as they pretend it is.
I also wonder whether our sentry install will like the increased load, but there's not much else to do than TIAS...
Jenkins job DCORE/gitlab-builds #290 failed in 1 min 11 sec.
See Console Output, Blue Ocean and Coverage Report for more details.I'm wondering if the trace propagation (across multiple services) will be as magic as they pretend it is.
Every time, it works 60% of the time
I also wonder whether our sentry install will like the increased load, but there's not much else to do than TIAS...
In my previous job, we were at 30% in production and the impact was not insignificant but the insights it provided made it worthwhile.
Jenkins job DCORE/gitlab-builds #292 succeeded in 1 min 0 sec.
See Console Output, Blue Ocean and Coverage Report for more details.Jenkins job DCORE/gitlab-builds #293 succeeded in 1 min 19 sec.
See Console Output, Blue Ocean and Coverage Report for more details.added 2 commits
Jenkins job DCORE/gitlab-builds #296 succeeded in 1 min 18 sec.
See Console Output, Blue Ocean and Coverage Report for more details.mentioned in issue swh/infra/sysadm-environment#5535