Sentry v6.0.0 Release Notes
-
Say hello to our new logomark! Version 6 of Sentry includes many changes within the core designed to improve future compatibility for various platforms.
It also includes quite a number of incompatible changes, so it's recommended 🔌 that plugin authors read through the notes carefully, and run some simply sanity checks. It also introduces version 4 of the protocol.
Incompatible Changes
- ⬆️ Django has been upgraded to 1.5. - django.contrib.auth.models.User has been replaced with sentry.models.User. - sentry_servers no longer exists, and the behavior is now always present. If you had it manually listed in INSTALLED_APPS, simply remove it. - 👀 Filters have been deprecated, and most functionality removed. See notes below. - 👀 TrackedUser, AffectedByUser, and Group.users_seen have been removed in favor of reusing the tagging architecture for user tracking. - Suspension of team members is no longer available. The feature was rarely used, and removing it greatly simplifies the auth logic in the API. - 🔌 **The mail plugin can no longer be disabled, and all mail-specific options have been removed.** - 👀 Nearly all data within an event now has a fixed max size. See client developer documentation for details. - 0️⃣ Project keys are no longer created for individuals by default - 🚚 sentry.conf.settings has been removed - 0️⃣ LOG_LEVELS, DEFAULT_LOG_LEVEL, and DEFAULT_LOGGER_NAME are no longer configurable. - DEFAULT_ALERT_PROJECT_THRESHOLD and DEFAULT_ALERT_GROUP_THRESHOLD are no longer configurable. - SENTRY_EMAIL_SUBJECT_PREFIX and SENTRY_SERVER_EMAIL are no longer used, and default to the appropriate Django options. - SENTRY_CACHE_BACKEND is no longer configurable. - SENTRY_AUTH_PROVIDERS is now AUTH_PROVIDERS. - Existing account recovery tokens are no longer valid. - 🚚 sentry.utils.router has been removed. Protocol Version 4 ~~~~~~~~~~~~~~~~~~ - sentry_version should be sent as '4'. - Aliases are now recommended instead of full interface names. - 👻 The exception interface now supports a bound stacktrace, and all events (in all protocols) which contain both an exception and a stacktrace will be rolled up. This should be sent as the ``stacktrace`` attribute. - 👻 The exception interface now supports chained exceptions, and should be sent as a list of exception values. Check the updated documentation for ordering details. Alerts ~~~~~~ A basic alert system has been added. - 🔧 Configured at the project level. - 🚦 Signaled via Plugin.on_alert. Filters ~~~~~~~ 🚚 The outdated filter system has been mostly removed. You should rely on 🏷 tagged data for filter generation. 🚚 If you were previously defining ``SENTRY_FILTERS`` you should remove it from your settings as it will be entirely obsolete in a future version. Other Changes ~~~~~~~~~~~~~ - Activity feeds will now attempt to filter out some duplicates. - 🏷 Tags now show on the event details page. - Corrected some invalid behavior when storing tags with an individual event. - 🏷 Plugin.get_tag_values was added. - A new team select dashboard exists if you are a member of multiple teams. - A new Sentry logo mark has replaced the simple text header. - C# has been added to experimental clients.