You did it — you made the move from a monolith to a collection of microservices in the name of optimizing performance and cost. Now you have the flexibility to scale multiple teams in different locations and the freedom to tackle a new feature or let an existing service handle it.
Flexibility and freedom come with a price: visibility. In a perfect world, APIs are well-defined, giving you insight into where errors occur in any microservice.
Unfortunately, we don't live in a perfect world, and errors can't always be pinpointed across microservices. You can waste a lot of time toggling between these microservices, trying to track them down.
Save time by sending errors from each service to Sentry. Pinpoint the code behaving unexpectedly by correlating errors with a unique identifier that traces the error across services and languages.
if (resp.status !== 200) { throw error; }
throw Error('Something went wrong');
Just look at all the high-quality security
features all accounts get, regardless of plan.
4M developers at over 100K companies already use Sentry. Why don’t you?
Here’s a quick look at how Sentry handles your personal information (PII).
×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?We may disclose your PII to the following type of recipients:
You may have the following rights related to your PII:
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.