Allow configuring sample rate.
I'm using sentry-cli to try to upload errors found in valgrind to the same place where we capture other errors from the same program in other contexts. I convert the valgrind output to json events which I then try to upload, but it seems most of them are getting dropped. I assume this is because the sample rate is less than 1 since debug logs don't show network issues.
Hi, thank you for the report. I'll get back to you as soon as possible.
After more investigation I'm not sure if it is a sample rate issue or a rate limiting issue. Switching to the following fixed my issue but is not ideal since it doesn't really go as fast as it could and might still run into issues with rate limiting:
for i in $(seq 1 $N_ISSUES); do
curl \
-d "@path/to/issues/${i}.json" \
-H 'Content-Type: application/json' \
-H "X-Sentry-Auth: Sentry sentry_version=7, sentry_key=<key>, sentry_secret=<secret>, sentry_client=sentry-bash/1.0" \
'https://sentry.io/api/<project id>/store/'
sleep 0.1
done
Though I don't seem to be able to get the rate limiting headers described here in the response to figure out what the actual sleep number should be?
@loewenheim any thoughts here?
Sorry this took so long. Can you look at your organization stats in Sentry and see how many events get dropped?
It is hard to tell since this is an experimental new source of events I am working on. I don't see how that would relate to rate limiting headers not getting sent.
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!
"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
@loewenheim any thoughts?
Sorry, I've been very busy. Trying to find out what's up with these headers.