Auto-instrumenting Lambda Monitoring didn’t originate through a focus group or business plan. It started as a hackathon project in which our growth team used Cloudwatch to build a prototype that could instrument Lambda functions with Sentry. We did this by using Cloudformation’s stack to automatically create resources in a customer environment while streaming CloudWatch Logs to Sentry through the Kinesis Firehose.
Top of search for you means top of mind for your customers. And with Google’s upcoming Page Experience update to Web Vitals taking place in a few weeks, now’s the right time to optimize your user experience. But before you can optimize your user’s experience, you need to be able to measure it. We’re kicking off Measurement May by breaking down breaking down how Google uses Web Vitals data — and how you can instrument that data with Sentry.
Responding to and ignoring notifications can be a full-contact sport. It makes sense, though, from GitHub, Slack, to Jira and Sentry; our world revolves around robots telling us everything is important, critical, and urgent. Just like that, it’s near impossible to see what actually matters so you can solve quicker and more comprehensively.
Recently, Sentry converted 100% of its frontend React codebase from JavaScript to TypeScript. This year-long effort spanned over a dozen members of the engineering team, 1,100 files, and 95,000 lines of code. In this blog post, we share our process, techniques, challenges, and ultimately, what we learned along this journey.
From testing in production to running A/B tests, feature flags have a range of uses. At Sentry, one way we use feature flags is to safely allow beta access to new features for some of our “Early Adopter” customers. Because you can set multiple combinations of feature flags, every user is likely to have a different experience.
