#SENTRY STORAGE FULL#

Because of this, it's important that in cases where you do need to be able to trace events you maintain them in your existing logging infrastructure.Īnother important differentiator between Sentry and generic logging is the amount of context captured. This effectively means that Sentry doesn't make guarantees of allowing you to find an exact historical error.

#SENTRY STORAGE FULL#

For example, Sentry won't store the full details of every error that comes in if it's one that already exists. Systems like Sentry lose a lot of data when computing rollups and transformations. Logging is very much intended to capture the entirety of your data, and give you maximum auditability. The most important difference between your general logging infrastructure and Sentry is how events are stored.

You'll need to determine what's right for you, but the important thing to remember is Sentry aims to support a lot, but it's primarily for capturing errors. As with errors, you'd still want to ensure you're logging these with your general logging infrastructure. Sentry aims to cater to these kinds of issues as well, but there's going to be various limitations and caveats. using continuous integration), but it's also something you might want to know about in production. This is something that you could easily capture in a validation phase (e.g. Use Example.goodbye() instead.') Click to Copy Logging.warn('The Example.hello() method has been deprecated. For example, you might be capturing deprecation warnings in Python. While Sentry is primarily used for reporting application exceptions, there's often cases where you want to capture other issues with your code. It does not replace the need for those logs, and it's also not a destination for things that aren't actionable errors or crashes. To summarize, Sentry works with your application logging infrastructure, often integrating directly. Sentry is fundamentally different because we focus on exceptions, or in other words, we capture application crashes.

Often those events are errors, but many times they're simply informational. The best way to think about things is this: logging provides you with a trail of events. When you start looking at mobile or desktop applications things start to become a bit more clear. It makes a lot of sense when you're looking at something like a web application, where your errors typically go to a logfile on disk. Often we get asked what the difference is between Sentry and traditional logging.

Sentry storage