Metrics tell you something happened, but they don't tell you why.
Sentry's Application Metrics are trace-connected, so you can click from a spike straight into the exact request that caused it 👀
Try for free: sentry.io/product/metric…
Comparison pages almost never provide the value people think they do.
You need to know who your competitors are, and be able to talk expertly about your strengths and weaknesses. You need to do that when you're talking to the customer, or making decisions internally. You don't
what do @neilsuperduper , @codybrouwers , @jacobmparis and @tmilewski have in common?
they'll be chatting with me on Tuesday, July 14th about loops, debugging systems in production and their favourite restaurants in Toronto.
Join @sentry and @clerk at Bellwoods on Ossington
Logs are underrated 🪵
When in doubt, add a few targeted log lines. They're the fastest way to understand what your app is actually doing in production.
Our latest blog post by @BenjaminCoe walks through what to log, when to log it, and when to remove it. Concrete examples
I've spent *maybe too much* time thinking about logging.
At npm, logging was my main tool for debugging the registry. At Google, I learned to log proactively so debugging rarely required a deployment.
Now, as a PM at Sentry, I get to learn how developers across many companies
We just shipped a new issue type at @getsentry: AI-detected low-value spans. Here's what happened when we ran it on our own infrastructure (and how Seer fixed it and saved us ~$10k/year) 🧵
Visit us at @WeAreDevs booth A14 and you might be able to snag a log 🪵
You can also catch our CEO, @virtualmilin, on the main stage tomorrow for not one, but TWO exciting chats. See you there 👇
Last night we borrowed one of Paris' best rooftops to bring together founders, engineering leads, and the people actually building the next era of AI and dev infra.
No panel this time, just golden hour cocktails, a Pierre Hermé macaron bar, and a live DJ to set the vibes.
Huge
You can't write a test for the bug you haven't seen yet.
Evals and tests catch what you already knew to check for.
Sentry shows you what actually broke in production (the errors, traces, and context you didn't know to look for) so you can fix what's real, not just what you
