How Instacart Rebuilt Their Release Monitoring Workflow
For a company like Instacart, one of the largest grocery delivery services in the US, a single bug in the codebase could impact millions of customers, shoppers, and their orders. When it came to a major release last year, Instacart’s infrastructure engineering team realized their existing workflow for monitoring the health of hundreds of microservices was no longer sustainable. They needed a better way to detect issues in their codebase before they impacted users.
Join Igor Dobrovitski, Infrastructure Software Engineer at Instacart, and Dhrumil Parekh, PM at Sentry, as they walk through how Instacart used Sentry’s APIs to build a custom internal integration that automatically analyzes new software releases of their front-end and back-end services. In this workshop, we’ll cover:
- Why Instacart built an integration with Sentry
- What the development process was like
- How the team monitors and triages release health with the integration
- Tips and tricks when building with Sentry
At Sentry, we were curious about how developers were building on our tools to solve their problems. So we decided to ask them. This workshop series highlights the stories of developers who have built tools that extend Sentry’s code observability capabilities, from public integrations to internal tooling. Every episode, a new developer tells us what, why, and how they built what they did, along with the value it brings to their end users and any advice they have for others looking to build on Sentry.
Featuring
Igor Dobrovitski
Infrustructure Software EngineeringInstacart
Dhrumil Parekh
Senior Product ManagerSentry
Get in touch.
A peek at your privacy
Here’s a quick look at how Sentry handles your personal information (PII).
×Who we collect PII from
We collect PII about people browsing our website, users of the Sentry service, prospective customers, and people who otherwise interact with us.
What if my PII is included in data sent to Sentry by a Sentry customer (e.g., someone using Sentry to monitor their app)? In this case you have to contact the Sentry customer (e.g., the maker of the app). We do not control the data that is sent to us through the Sentry service for the purposes of application monitoring.
Am I included?PII we may collect about you
- PII provided by you and related to your
- Account, profile, and login
- Requests and inquiries
- Purchases
- PII collected from your device and usage
- PII collected from third parties (e.g., social media)
How we use your PII
- To operate our site and service
- To protect and improve our site and service
- To provide customer care and support
- To communicate with you
- For other purposes (that we inform you of at collection)
Third parties who receive your PII
We may disclose your PII to the following type of recipients:
- Subsidiaries and other affiliates
- Service providers
- Partners (go-to-market, analytics)
- Third-party platforms (when you connect them to our service)
- Governmental authorities (where necessary)
- An actual or potential buyer
We use cookies (but not for advertising)
- We do not use advertising or targeting cookies
- We use necessary cookies to run and improve our site and service
- You can disable cookies but this can impact your use or access to certain parts of our site and service
Know your rights
You may have the following rights related to your PII:
- Access, correct, and update
- Object to or restrict processing
- Port over
- Opt-out of marketing
- Be forgotten by Sentry
- Withdraw your consent
- Complain about us
If you have any questions or concerns about your privacy at Sentry, please email us at compliance@sentry.io.
If you are a California resident, see our Supplemental notice.