First of all I really like Sentry but there is one architectural fact I can’t really wrap my head around. I’m sure I lack some understanding of the topic, so perhaps someone might be able to explain it to me properly.
We’re using PHP and I really dislike the fact that I’m capturing errors and sending them to a different host (where Sentry will be running) during the HTTP request a customer is performing. At the moment we’re logging to files with specific context and use the ELK-stack with Filebeat to index and search them. What if the Sentry host is unavailable or slow to respond, this will directly impact the HTTP requests our customers are performing. Am I missing something that would negate this issue? Is there a way to send traces to Sentry without blocking our own HTTP requests?
Thanks in advance.