We're running a microservices architecture and tracing requests across services has been a pain point. Does Sentry handle distributed tracing well? We're also already using OpenTelemetry, wondering if we'd have to re-instrument everything or if it works with our existing setup.
We're looking at consolidating our observability stack and Sentry has come up as an option. Curious how it compares to something like Datadog or New Relic, is it a full observability platform or more of a debugging tool?
We have a pretty mixed stack, web frontend, a couple of backend services, and a mobile app. Before we commit to Sentry, I want to make sure it actually supports everything we're running without needing separate configurations for each.
We're evaluating APM tools and Sentry keeps coming up. We already use it for error tracking, but I'm wondering if it's worth using for performance monitoring too, or if we'd be better off with a dedicated APM tool.
I've seen Seer mentioned a few times while looking into Sentry but I'm not totally clear on what it is or what it does. Is it just an AI chatbot?
We've been using Sentry for errors for a while and it works well for that. Curious how far it actually goes though, is performance monitoring, logs, and tracing genuinely useful in Sentry, or should we just use dedicated tools for that stuff?