Version 7.7.0

  • The behavior of create_or_update has changed. If you’re using it please see the updated function.
  • Added Group.first_release column.
  • Added SavedSearch model for future features.
  • The explore feature is now deprecated and links have been hidden.

Version 7.6.0

This releases entirely removes Access Groups. If you’re upgrading from an installation that had yet to migrate away from this system you should first upgrade to a previous version, run the migration wizard, and then continue the upgrade.

  • The project-wide Alert system has been removed (to be re-implemented in the future).
  • Access groups have been permanently removed.
  • Added ‘access_token’ to data blacklist.
  • The legacy (unused) search tables have been removed.
  • Upgrades must now be applied manually via sentry upgrade or with sentry start --upgrade. (Don’t forget to use --noinput if you’re doing this via automated tooling!)
  • Event.checksum and Group.checksum have been removed.
  • The cleanup task has been removed (the command is still available).
  • Various optimizations to cleanup for Postgres users.
  • Within single organization mode users will automatically be added to the default organization.
  • Added Organization.merge_to() helper to assist with merging organizations. (i.e. in an on-premise install which wants to convert to a single organization)
  • New import and export commands now exist for creating backups of critical metadata (i.e. api keys, projects, user settings)

Version 7.5.4

  • Yet another case where valid team membership was being excluded.

Version 7.5.3

  • Fix another case where valid team membership was being excluded

Version 7.5.2

  • Correctly support SENTRY_PROJECT.

Version 7.5.1

  • Fix case where certain pages were not correctly including valid team membership
  • Fix default user creation (regain automated signal)
  • Fix sampling of internal metrics

Version 7.5.0

This release removes the ability to login or create accounts using a social auth backend.

If your install was based purely on social accounts you’ll need to use the standard reset password flows to recover accounts.

Redis must be at least version 2.6.12.

  • Interface.compute_hashes() now receives the platform of the event.
  • Server-side data scrubbers were incorrectly filtering invalid interface aliases.
  • The sensitive_fields option is now exposed in project settings.
  • The default logger name is now an empty value.
  • Celery has been upgraded to 3.1 and is now available at ‘sentry.celery’.
  • Facebook, Google, and Twitter identities are no longer available.
  • Plugin’s inheriting from TagPlugin are now based on v2 of the API.
  • Metrics (counters) are now collected both in sentry.tsdb and an optionally configured statsd instance.
  • Organizations can now toggle open membership which allows members to freely join/leave any team.
  • ProjectKey.user has been removed.
  • Organization API keys are now exposed in the UI.
  • Team.owner has been removed.
  • TeamMember has been removed.
  • PendingTeamMember has been removed.
  • Added OrganizationMember.counter.
  • Added ‘sentry.db.postgres’ optimized Postgres backend.
  • Added ReleaseTrackingPlugin and various release-focused endpoints.
  • Dedicated configuration pages for Release Tracking and Issue Tracking integrations now exist.
  • Several additions to the Release schema.
  • Notification integrations are now present within project’s notification settings.
  • Fixed an issue with tag key deletion not following explicit constraints.

Version 7.4.3

  • Corrected various issues involving sampled data. Things should now sample according to actual MATH.

Version 7.4.2

  • Corrected invalid reference to SENTRY_ALLOW_REGISTRATION.

Version 7.4.1

  • Correct an issue with AuthProvider’s migrations on MySQL.

Version 7.4.0

  • A new features subsystem was added, and many optional features are now run through it.
  • The ‘add_organization’ permission is no longer used.
  • The ‘add_team’ permission is no longer used.
  • SENTRY_ALLOW_REGISTRATION is deprecated in favor of SENTRY_FEATURES[‘auth:register’].
  • SOCIAL_AUTH_CREATE_USERS is deprecated in favor of SENTRY_FEATURES[‘social-auth:register’].
  • SENTRY_SERVER_EMAIL is no longer used.
  • Added first pass API at storing javascript artifacts via release APIs.
  • Improved error reporting for JavaScript source/sourcemap errors.
  • Improved configuration handling on sentry.cache.
  • Added various release API endpoints.
  • Added various organization API endpoints.
  • Added various tag API endpoints.
  • Sourcemaps will now always treat sourceRoot as a path.
  • Changed many permissions to use new sentry.access abstractions which are now scoped based, shared with the API scopes.
  • Initial first pass at the SSO subsystem.
  • The Sentry internal client will now aggressively prevent recursive errors, but allow more internal errors to be recorded to itself.
  • An XSS vulnerability with tag values not being escaped (on the group details page) has been resolved.

Version 7.3.2

  • Fixed missing beacon task import.

Version 7.3.1

  • Updated Gunicorn version and default configuration.
  • Fixed periodic task for beacon.

Version 7.3.0

  • The SENTRY_ADMIN_EMAIL setting now exists, and should be the technical contact for the install.
  • Fixed an issue that would cause job fanout in deletions.
  • Notifications are now sent when someone assigns you to an event.
  • Release objects are now created automatically.
  • Changed team-based API endpoints to use slugs.
  • New API endpoints: - Help page list - Help page details - Group tag values - Project tag values
  • Moved JavaScript sourcemap processing into language extension. - Sourcemap processing errors are now annotated into the frame.
  • Refactored API to be scope-based permissions.
  • Added backend support for organization API keys.
  • Moved sentry_webhooks into builtins.
  • Added reporting Beacon (see docs).

Version 7.2.0

  • A py.test plugin now exists to make extension testing easier.
  • A Mailgun webhook endpoint is now available for incoming email.
  • Added security token for JS source expansion.
  • Duct tape workaround for event navigation buttons repeating the same event.
  • Origins now support custom protocols as well as relaxed support on other components.
  • Minor optimizations for deletion tasks and endpoints.
  • Minor optimizations for Redis buffer.
  • Added the ability to enable/disable project keys.
  • Added audit log entries for project keys.
  • Added UI, API, and async task for deleting project tag keys.
  • Various fixes/improvements to regression windows.
  • Rules will no longer execute duplicate actions.
  • EventFrequencyCondition will now fire a maximum of once every 30 minutes.

Version 7.1.4

  • Fixed an issue with hourly rollups not expiring accurately in TSDB

If you’ve been running a 7.x series release for a while you may considering running a cleanup script to ensure erroneous values dont still exist in Redis:

Version 7.1.3

  • Resolved an issue with migrations we created in 7.1.2.

Version 7.1.2

  • Fix migrations to ensure org/teams arent created with empty slugs.

Version 7.1.1

  • Suggest realip module over X-Forwarded-For

Version 7.1.0

Plugin v2

The beginnings of version 2 of the plugin interface have landed. This will expand over time but currently includes the following hooks:

  • get_actions
  • get_annotations
  • get_event_preprocessors
  • get_notifiers
  • get_rules
  • get_tags

Other Changes

  • crossdomain.xml no longer supports projects-by-slug.
  • A basic file storage abstraction is now available internally.
  • The project group list API endpoint now has pagination.
  • Several API endpoints have been added to public docs.
  • X-Forwarded-For is now handled automatically (and we do not support non-proxy installs).
  • Various tweaks to GroupMeta caching.
  • The raven-python Sentry server-specific client code is now part of Sentry.
  • Various improvements to tag rendering.
  • Various improvements to bulk deletion strategies.
  • Added NodeStore.multi_delete.

Version 7.0.0

Between version 6.4.x and 7.0 a significant number of changes have landed (approximately a years worth of commits). There are a large number of overall architecture changes, as well as various API compatibility changes. This document does not attempt to cover them all.

As many things have changed, it’s strongly recommended that you regenerate your (using sentry init) and merge in your custom settings.

Backwards Incompatible Changes

  • Django has been upgraded to 1.6
  • The buffer API has been rewritten and the Redis buffer has had its performance greatly improved.
  • The UDP server has been removed. Threaded/async models or a buffer proxy are the preferred replacement.
  • The is_rate_limited plugin hook has been removed in favor of singular quota managers.
  • The trends feature has been removed until it can be reimplemented in a more scalable way.
  • Filters have been removed. Integrations should use the tagging infrastructure instead.
  • NodeStore.generate_id() now returns a base64-encoded UUID.
  • The API for interfaces has been rewritten.
  • GroupMeta.objects.get_value no longer errors when a value is missing.
  • sentry.plugins.sentry_sites has been removed.
  • The Search API has been rewritten and now powers the entire stream.
  • Removed Event.{logger,site,logger,level,culprit} references/columns. Legacy attributes for transitional behavior are available.
  • Removed Project.owner.
  • Removed Team.owner.
  • is_new in Plugin.post_process will only be set if the event is brand new.
  • Project-based URLs are changed to be organization scoped instead of team scoped.
  • Static assets are no longer bundled as part of the repository and are instead compiled during the sdist/installation phases (as needed). See installation notes for further information.
  • Graphs have been transitiong to sentry.tsdb (historical data is not preserved)
  • Workers must now also run celerybeat. This can be done either via passing -B to worker, or by running another process: sentry celerybeat.
  • Access Groups are now deprecated and will be removed in a version version.


Organizations are the new top-level item of your Sentry install. All membership and team management has been moved into the new organization hub.

Generally for self-hosted installations you’ll only have a single organization.

Migrations will happen automatically for this, and while these were able to applied cleanly and automatically on, we suggest considering snapshotting your database before running them. Additionally consider doing this at a period of the day where users generally wont be tweaking options to team membership.


A new time-series backend is now used (removing the legacy SQL-based graphing solutions). The only currently supported/bundled backend requires Redis. More information can be found in sentry.tsdb.


A new system for basic controls around notifications (called Rules) has been added. These are per-project hooks for doing dynamic customization of “what happens when a new event is seen?”.


The first offering a public API has landed. You’ll find it with the new embedded docs (at /docs/).

Protocol Version 6

Version 6 of the protocol has been introduced. The only change is the addition of the release attribute.


All integer fields have been replaced with bigint’s. This migration is not automated (due to it causing locking) and if you need it locally you will need to sort out the migration on your own, as well as set SENTRY_USE_BIG_INTS = True in your configuration.

Help Pages

The beginnings of bundled documentation now exists. The defaults are generated from disk (see sentry/data/help_pages/).

Version 6.4.0

Some major backend changes are introduced in Sentry 6.4.0.


The builtin Django authentication module is no more. The Group and Permission models are no longer used, and the User model has been replaced with sentry.User.

Event Storage

A new application called nodestore now manages the event blob data. By default it uses a Django-based backend (storing each node as a row in a table), however a Riak backend is included and fully supported.

Additional Changes

  • Some initial support for time zones (user setting).
  • You can now choose which tag annotations are applied to the event stream via Project Settings -> Tags.
  • A new subsystem for handling email is available in
  • You can now receive email notifications for notes.
  • Charts now show tooltips describing the datapoint.
  • JavaScript sourcemaps now support embedded sources.
  • Stream annotations can now be customized to show any tags (not just number of users).
  • Stacktrace frames now get truncated down to a maximum length of 50.

Protocol Version 5

  • sentry_version should be sent as ‘5’.
  • The stacktrace interface now accepts a ‘frames_omitted’ tuple.

Version 6.3.0

  • Most of the db utilities were refactored into sentry.db.
  • The user interface now accepts an ip_address attribute.
  • User tracking will now use the ip_address attribute if available.
  • time_spent is now expected to be sent as an integer in milliseconds.
  • A new Notes feature is available for leaving comments on an event.

Version 6.2.0

  • Added tracking to which users have seen which groups
  • The stream now reflects if you’ve viewed an event since it was created or regressed.
  • The group details page shows other users who have glanced at an event.
  • Streams which have recorded user data will now show the number of unique users an event has happened to.
  • Various stream polling fixes and improvements.

Version 6.1.1 (Security Release)

Sentry 6.1.1 is a security release which patches a remote code execution exploit.

This only affects servers hosted public clients (e.g. raven.js).

The following commit demonstrates the exploit, as well as the patch:

Version 6.1.0

  • Added Rate Limit controls.

Version 6.0.0

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.
  • Project keys are no longer created for individuals by default
  • sentry.conf.settings has been removed
  • LOG_LEVELS, DEFAULT_LOG_LEVEL, and DEFAULT_LOGGER_NAME 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.
  • 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.


A basic alert system has been added.

  • Configured at the project level.
  • Signaled via Plugin.on_alert.


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.

Version 5.4.0

SENTRY_PUBLIC now dictates whether or not a Sentry install should be considered accessible by all users or not. This should better solve the use-case of companies hosting a Sentry instance internally and not necessarily needing the permissions that teams give you.

If enabled, all teams and all projects will be accessible all members (for any endpoint which does not require a certain level of access). Project.is_public now dictates the implied state of all events, but will not allow a non-member to browse events.

Additionally, this includes the following other items:

  • [Important!] The URLS for social authentication have been moved.
  • Improved rendering of data values in all interfaces.
  • django-compressor was replaced with django-static-compiler.
  • A better defined public view of events (which removes several items from being visible).
  • Improved SourceMap discovery.
  • Most events will no longer cause a hard error when validation fails. Instead we attempt to drop any non-required data so that at least a partial event is stored.
  • MessageCountByMinute was renamed to GroupCountByMinute.
  • MessageFilterValue was renamed to GroupTag.
  • Syntax highlighting was disabled (pending performance solutions).
  • Added Team.date_added column.
  • Lots of various design changes.
  • Trending SQL queries can now be disabled by setting SENTRY_USE_TRENDING = False

Version 5.3.0

A brand new Sentry design has landed.

Some things of note:

  • An improved dashboard.
  • Improved activity feeds on aggregate details.
  • Similar event navigation links on aggregate details.
  • Redesigned team management flow.


  • Aggregates now happen on (project, checksum), which means events that have different levels or culprits can now be grouped together.
  • Sentry now requires authentication for all pages.
  • SENTRY_PUBLIC behavior has changed to signify the default state of projects.
  • Project slug’s are now only unique within a team.

Version 5.2.2

  • [New] The dashboard will now stream updates to the new and trending event components.

Version 5.2.1

  • [Fix] Trends sorting options on the Stream page work correctly again.

Version 5.2.0

  • [New] A new activity stream exists on event pages.
  • [New] Syntax highlighting now exists on all context frames.
  • [New] Support for JavaScript Sourcemaps now exists.
  • [New] The server will now fetch remote source files for JavaScript events.
  • [New] Sentry will now ask for your project’s platform.
  • [Fix] Resolved -> Regressed state change is now atomic.
  • [Fix] cleanup now runs with lower resource overhead.
  • [Fix] Cookies will now be coerced to dicts if possible.
  • More (storage only still) work on user tracking.
  • Several indexes were added to speed up various queries.
  • Removed savepoint use in plugin hooks (99% of the time there were no queries).

Additional, the following client protocol changes are part of this release:

  • Cookies should be not be sent by default.
  • POST data should not be sent by default.
  • Recommended values regexp for sanitizing credit cards was updated.
  • colno was added to the Stacktrace spec.
  • Timestamps that are more than one minute in the future are now discarded.
  • (Undocumented) Client-side support now exists for GET + Referrer store requests.

We’ve also reduced the test suite time down to 25% of what it originally was (thanks, Alex!)

Version 5.1.3

A new user’s affected-tracking mechanism is present (storage only). This will become available in the UX in a future version, and relies on the existing HTTP and User interface datas.

  • [Fix] Correct a bug with search queries.
  • [New] Group.users_seen will now track unique users when possible.
  • [New] Team and project owners can now change ownership (non-superuser).
  • [Fix] Counts are now formatted correctly when number of visible digits > 3.

Version 5.1.2

  • [Fix] Option schema (key length = 64).
  • [Fix] Template interface now renders correctly.
  • [Fix] Update design on admin status pages.
  • [New] iOS client documentation.
  • Improved client documentation visuals.

Version 5.1.1

Several schema changes are made in this upgrade:

  • A new model: LostPasswordHash
  • Two new fields on ProjectKey: date_added and user_added
  • A new field on Event: platform
  • A new field on Group: platform

The following changes are also part of this release:

  • [New] A new plugin, sentry-interface-types will now automatically tag the available interface types in an event.
  • [New] The platform value sent with an event is now recorded in the database.
  • [New] A recover account flow has been added.
  • [New] There is now a sticky nav on the event details pages.
  • [New] getting started page now shows if there’s no data for a project.
  • [New] An API key management page now exists (under project settings).
  • [New] A tag overview page now exists for group details pages.
  • [Fix] Line numbers now show correctly in collapsed source context.
  • [Fix] Pending members now show correctly on the team management page (under project settings).
  • [Fix] The time since value now updates correctly when events change.
  • Various changes to how event details components render.
  • Various fixes for breadcrumbs and header styles.
  • Most plugins will no longer default to enabled on new projects.

Version 5.1.0

Minor point releases now signify major changes (5.1.0 is a major release). Bugfix and smaller releases will continue as normal.

This release includes a very large set of changes from 5.0.0, including a new client protocol and an overhaul to the frontend code (specifically the JavaScript).

If you’re a contributor, take note that there is now a JavaScript test suite. You can run all test suites with the make test command.

Protocol Version 3

Sentry 5.1 removes support for version 1.0 of the protocol, and maintains a compatibility layer for version 2.0.

Additionally, the following changes apply to the new protocol:

  • sentry_version should be sent as ‘3’ (not 3.0).
  • Signed messages are no longer supported (signatures are not calculated). - sentry_signature is no longer used. - sentry_timestamp is no longer used.
  • Clients must pass sentry_secret for server-side requests as part of the auth header. This check runs in the event that there is no Origin header sent. - version 2.0 supports validation of this, version 3 requires it.
  • The project attribute in the JSON packet is no longer required.
  • The platform attribute is now recommended.
  • The tags attribute is now recommended.

Other Changes

  • Aggregation ‘Views’ have been removed.
  • All streaming components are now powered by Backbone.js.
  • Frontend has been updated to Bootstrap 2.1.
  • The event stream now includes sparklines representing the last 24 hours of data for each event.
  • Trends have greatly improved.
  • Grouping events that have identical stacktraces other than the function name (e.g. dynamically generated functions) is not possible.
  • SiteFilter has been removed, as has the sites plugin.
  • If frames are included in a stacktrace that have the attribute in_app: false, they will be hidden by default in the details view.
  • crossdomain.xml support is now available (see documentation).
  • The search feature now uses buffers to better handle write concurrency.
  • Early support for WSGI (should be functional) exists as sentry.wsgi.
  • Many fixes around cache usage.

Version 5.0.0

  • Variable versions of Django are no longer supported. Django 1.4.x must now be used.
  • Public projects are restricted to viewing without being authenticated.
  • The default behavior of Sentry is to now use timezone-aware datetimes everywhere.
  • Permissions have been refactored to be more precise.

Version 4.10.0

  • A new IssuePlugin base is available.
  • Charts have been refactored to show 7 days worth of data.
  • django.contrib.staticfiles is now supported.
  • django.contrib.messages is now supported.

Version 4.9.0

Social authentication is now supported!

By configuring several options (documented in the getting started guide), you can allow users to signup and login with accounts from several social services. Additionally users can associate their existing accounts (via a new identities panel in their account settings) with any number of these services.

Currently, the following services are supported:

  • GitHub
  • Twitter
  • Facebook
  • Google

Version 4.8.0

Tags are now able to be created dynamically! See the documentation for more details on implementing it inside of your client.

You can also configure which tags will show up as filters in the sidebar via your project’s settings page. By default all tags will show up.

Version 4.7.0

User options are now available to plugins. The builtin mail plugin also now takes advantage of them.

  • sentry_mail will now use the alert_email option over your account email if specified.
  • sentry_mail now allows you to choose which projects to receive alerts for.
  • Numeric slugs will no longer return 404s.
  • Corrected the repair command with the –owner argument.

Version 4.6.0

Improvements to the dashboard are trickling in, with this update including:

  • Changing “Top Events” to “Trends” (if supported by your RDBMS)
  • Time interval selections for both widgets

Plugins now have a new interface for registering themselves. Please see the developer documentation for notes on how to use entry_points.


  • Signed messages are now deprecated. Save yourself some CPU cycles, and rely on SSL.
  • A new plugin which tags user’s email addresses.
  • Several UI cleanups in various areas, such as improvements to the account dropdown and lists of projects/teams.
  • Long awaited cleanup/fixes for applying the initial database migrations (sorry MySQL users).
  • Initial support for arbitrary event tagging (coming soon to a client near you).

Version 4.5.0

Builtin plugins have been refactored to be more concise. This includes changes to the servers, urls, and sites plugins. There is also a new builtin plugin:


With these changes, it now makes it even easier to create a basic plugin that just handles extra “tag”-like data. Take a look at one of the aforementioned plugins for an example.


  • The mail plugin now sends additional Sentry-specific headers.
  • Signatures are deprecated, and no longer required.
  • Several fixes regarding CORS support.

Version 4.4.0

Two new columns were added to the Group model:

  • resolved_at: The datetime at which this event was marked as resolved.
  • active_at: The datetime at which this event was marked as open.

The dashboard’s “New Events” will now use the active_at date rather than the original first seen date on an event.

Version 4.3.0

A new global dashboard now exists. The dashboard contains an event graph for all projects which you have access to, as well as a list of the top events, and new events.


  • API endpoints now properly send no-cache headers.
  • Added a countdown to update buffers.

Version 4.2.0

Sentry now has support for buffering a majority of its counters via Redis. For more information, check the buffer section of the configuration documentation.

  • Nearly all race conditions are now handled correctly using distributed cache locks.

Version 4.1.0

Sentry now maintains full support for CORS requests from external hosts. This means that clients like raven-js will now able to securely send messages to Sentry, without compromising their secret key.

In addition:

  • Trusted domains were removed. These were not fully implemented.
  • A new datepicker for selecting ranges of events.
  • raven-javascript and raven-ruby are now officially supported clients.
  • Added sentry repair.

Version 4.0.0

Introducing Teams!

Projects are now assigned to a single team, and that team may consist of many members. Additionally each team may own multiple projects. This makes it much easier to handle permissions across a single organization that has many projects.

This update also includes initial changes to how filters work. ServerName Filter and SiteFilter are no longer specified in the FILTERS setting, but instead are included automatically if you load the respective sentry_servers and sentry_sites plugins.

Additional changes:

  • Legacy data format is no longer supported (pre-Raven 1.x)
  • API will now validate data before sending it into the queue, enabling better debugging for clients.

Version 3.8.0

Plugins are now configurable per-project. This makes it easy to install a plugin globally and allow it to run only on selective projects.

Version 3.7.0

Several minor fixes, as well as a backwards incompatible change with filters.

All filters must now accept the project argument in the initializer. The signature is now __init__(request, project).

Version 3.6.0

This version focuses on improving membership control. It includes the ability to revoke project members access temporarily (by suspending them), as well as revoking users (outside of Sentry) via the user.is_active flag.

Additionally, it brings the beginnings of an “invite user” flow, allowing you to invite users who may or may not already have accounts in the system. We plan to improve this flow in an upcoming release to allow invitees easy registration within the system if they don’t already have an account.

Version 3.5.0

Several improvements and additions have been made around the administration, including performance improvements.

If you’re utilizing the queue, the installation guide now recommends you switch off the database backend, and move to something more efficient (such as Redis).

Version 3.4.0

Eventlet is no longer used as the default worker for gunicorn, and thus is no longer installed by default. If you’re using the udp worker, or send_fake_data you MUST install eventlet yourself. The recommended worker class for gunicorn is now gevent as it corrects some issues with async queries in psycopg2.

Version 3.3.0

The queue has been changed from direct Kombu, to utilizing Celery entirely. If you were already using the queue, the upgrade simply requires you to change “sentry start worker” to “sentry celeryd”.

Version 3.0.0

Version 3 of Sentry is centered around a restructure of the internal services and the architecture for running those. It also includes improvements to the plugin architecture.

The upgrade process should be trivial, just be aware that if you were using –config before you must change the way you pass it so that it’s before the subcommand. For example if you were doing sentry start --config... the command would now be changed to sentry --config... start.

  • Sentry no longer provides the ability to daemonize processes. This should now be done at the system level.
  • All of Sentry’s CLI is now handled through Logan (, which simply pipes commands to Django’s internal system utilizing custom configuration.
  • Plugins now have a hook for managing some level of permissions (beyond the required defaults).
  • The plugin interface (IPlugin) is now documented.
  • It is now recommended that clients allow the Sentry server to compute checksums.

Version 2.9.0

  • Plugins must now behave as singletons and be registered with a newly provided sentry.plugins.@register decorator.
  • The Bugzilla and Redmine extensions are no longer part of Sentry core.
  • Added a global overview of projects to the administration.

Version 2.8.0

  • Added an Account Settings panel which allows users to change their name, email, and password.
  • The default Sentry server now correctly wraps itself in its own middleware.
  • Improved Real-time JavaScript.

Version 2.7.0

  • Added first_seen and last_seen to all message filter values.
  • Added a new “since” option to the dashboard with a default value of 3 days.

Version 2.6.0

  • The built-in webserver is now powered by gunicorn.
  • Cleaned up several admin pages and split them into sub-pages.

Version 2.5.0

  • Corrected some queue behavior.
  • Resolve Feed now only resolves items active within current filters.
  • Handle unicode characters in POST body for replay request.
  • Ensure client side requests run checks on HTTP_REFERER
  • Adjust documentation for service settings.

Version 2.4.5

  • Corrected indexing behavior to handle non strings.
  • If queuing is enabled the indexer will now queue it’s jobs.
  • Moved group creation into a transaction.

Version 2.4.4

  • Mail configuration value of send_to now correctly uses ‘,’ as a separator (rather than ‘;’).
  • Changed rendering of sidebar widgets for all builtin extensions.
  • Added an event details slot to the sidebar pane for individual events.

Version 2.4.3

  • Correct some behavior with MySQL on the groups pane.
  • Correct generated configuration behavior to use absolute paths for run and log folders.

Version 2.4.2

  • Include DSN and member type on projects list grid.

Version 2.4.1

  • Change appearance of resolve states.
  • Adjust user management to link username (which is required) and not optional fields.

Version 2.4.0

  • Added user management for admins.
  • Resolved events should now appear differently.
  • Default membership access is now configurable.

Version 2.3.2

  • Maintaining some level of support for SQLite.

Version 2.3.1

  • Correct rendering of sites, urls, and servers on details panes.

Version 2.3.0

  • The polling API and JavaScript have been refactored.

    Events now stream in (they generally do not update if they already exist), and will maintain correct ordering in the feed.

    This API is available for most sort options, excluding trends.

  • The builtin plugin’s widgets have been fixed.

  • Sampling rates are now configurable.

  • Some minor design tweaks.

Version 2.2.5

  • The |date filter now forces things to UTC (it assumes local time).
  • Event templates have been updated to resemble groups.

Version 2.2.4

  • Improve error logging in API.
  • Update Celery client code to use new send_encoded interfaces.
  • Change JS datetimes to use UTC.
  • Force clients which specify version 2.0 or newer to pass identification.
  • Better default logging configuration.
  • Adjust eventlet to monkey patch the world before any imports happen.
  • Adjust default configuration to specify LOG and RUN directories.
  • upgrade now correctly handles the delete ghosts argument.

Version 2.2.3

  • Lower font size of counts on event list.
  • Align actions to right side (vertical).
  • Fix issue with long filters not transforming to selects.

Version 2.2.2

  • Corrected event_id key to contain (project_id, event_id).
  • Adjusted project form to default the user to the current user when accessed by an admin.
  • Change sentry admin to be /manage/ to avoid any unintentional conflict with the Django admin.

Version 2.2.1

  • Cleaned up several pages.

Version 2.2.0

  • Sentry has a brand new design utilizing Bootstrap 2.
  • Superusers can now create projects for users.

Version 2.1.3

  • Ensure we truncate tokens to 128 characters for SearchDocument.
  • Gracefully handle errors with indexing.
  • Gracefully handle errors with post_process.
  • Gracefully handle errors with regression_signal.
  • Fixed priority sort option not activating.

Version 2.1.2

  • Fixed an issue that was causing signals to not be registered.
  • Made date the default sort order for aggregate stream.

Version 2.1.1

  • Fixed an issue with indexing pre and post context on templates.

Version 2.1.0

  • pytz is now a requirement.
  • Changed default TIME_ZONE to be “UTC”.
  • Corrected some issues around how dates were localized.
  • Initial implementation of full-text search.
  • Fixed sending of regression_signal so it only happens if event has been marked as new.
  • Changed ProjectMember.get_dsn() to use request.get_host() which corrects a bug in some webservers.

Version 2.0.2

  • start no longer performs upgrade as its problematic.
  • Initial queue usage (optional).
  • Fix reference to bookmark_querystring.
  • Added DSN to project member details page.

Version 2.0.1

  • Skip logging of south in default server configuration as it proves to be problematic.
  • Remove use of deprecated logging handler in default server configuration.
  • Run upgrade as part of start.
  • Fix GroupBookmark related_name to be sentry namespaced.
  • Correctly handle before_events() hook in polling responses.
  • Removed integrated install documentation as it is no longer officially supported.
  • Gracefully handle rendering errors with interfaces.
  • Correct a bug with default email options.

Version 2.0

Sentry 2.0 is a major release which contains many new features as well as some large rearchitecting of the codebase.

If you were previously extending Sentry, it would be wise to test your extensions before upgrading.

  • Added project scoping to all data in sentry.
  • Added permissions to projects.
  • The authorization header is now X-Sentry-Auth to avoid certain default behaviors such as mod_wsgi’s “don’t pass HTTP Authorization header”.
  • sentry.client has been removed
  • The default key is now base64-encoded.
  • sentry.interfaces are now used for coercing and rendering structured data.
  • The store endpoint has a new API.
  • The from_kwargs method has a new API.
  • The class_name, traceback, an url fields have been removed.
  • GroupedMessage was renamed to Group.
  • Message was renamed to Event.
  • Switched to Bootstrap framework.
  • Added “Replay Request” action for events.
  • Graphs can now be generated for Projects.
  • There is now a trends sort option for aggregated events.
  • Added sentry manage command.
  • Sentry now has its own isolated queues (using Kombu).

Version 1.13.5

  • Level filters are now precise (they no longer show their level + messages from higher levels).

Version 1.13.4

  • Updated message details page to resemble look and feel of group details.

Version 1.13.3

  • Added back in the “raw traceback” view.

Version 1.13.2

  • Counts will now render differently with large values (e.g. 13000 will now be 13k)

Version 1.13.1

  • Search by message_id will now display a list of results if there are multiple matches.

Version 1.13.0

  • Deprecated the Sentry client, and added Raven to the as the default builtin.
  • Removed Highstock and replaced it with an awesome OPEN SOURCE alternative, jQuery Flot.
  • Default Sentry server options should now work out of the box.
  • Packaged Google Web Font as part of Sentry.

Version 1.12.2

  • Fixed infinite loop.

Version 1.12.1

  • Stabilize migration schema (solves problem with index creation fail introduced in 1.12.0).

Version 1.12.0

  • Adjusted message_id to include the checksum to avoid situations were the message_id that was generated did not exist due to sampling.

Version 1.11.4

  • Several design improvements for group/message details panes.

Version 1.11.3

  • Fixed a bug that was causing exception summary to not show.

Version 1.11.2

  • Cleaned up message and group details pages (adding back some missing information).
  • Cleaned up some design around odd margins/padding.

Version 1.11.1

  • Fixed a bug that would cause the admin (and potentially other modules) to get loaded multiple times.

Version 1.11.0

  • Added license headers.
  • Removed sentry.helpers and sentry.routers.
  • Global module versions are now cached to avoid continuous path walking and import overhead.

Version 1.10.1

  • Fixed an issue that was causing servers to show logger names.

Version 1.10.0

  • You can now pass extra={'stack': True} to logging methods to capture the current frames and their locals.
  • Code refactoring in various places related to stack extraction.
  • Denormalized graph data in MessageCountByMinute (stores at 5m intervals).
  • Denormalized filter counts into MessageFilterValue
  • Added message sampling (adapted from Yuri Baburov’s patch).
  • Added SENTRY_MAIL_LEVEL setting.
  • Added the level argument to the cleanup command.
  • The thrashed key is now set correctly in request.sentry.
  • Added user information to all messages that have request.
  • Changed the hashing function for messages that include stacktraces to ignore the message and line numbers.
  • Much improved test coverage.

Version 1.9.0

  • Load the Frequency chart asynchronously.
  • Frequency chart no longer shows for SQLite.
  • Switch graphing library to Highstock from Highcharts.

Version 1.8.10

  • Ensure dictionary keys are coerced to strings.
  • Fixed path to missing_permissions.html.

Version 1.8.9

  • Safely handle unpickling objects that may not have been stored in a valid format.

Version 1.8.8

  • Changed sentry cleanup to use a range query.

Version 1.8.7

  • Added “Clear Feed” option.
  • Version information will be read from pkg_resources if possible.
  • Cleared up documentation on configuration settings..
  • Performance improvements to Client.send().
  • Added default 404/500 pages.
  • Added support for Django’s LOGIN_URL setting.
  • Fixed a memory leak in the client (thanks to Ben Bangert).


  • Reverted change which required distribute.
  • Cleaned up configuration defaults.


  • Include in the MANIFEST to ship it in sdists.

Version 1.8.6

  • Corrected an issue which was causing certain settings (like WEB_HOST) to not take affect in custom configuration files.
  • The Sentry server will now pull in default server settings, as well as ~/.sentry/ if –config is not passed to it.


  • Fixed a bug which caused thrashing prevention to not function correctly.
  • Corrected an error in transform()’s recursion safety.
  • Changed packaging to use Distribute.

Version 1.8.5

  • Pulled test suite out of the Sentry namespace to avoid conflicts in projects.


  • Added missing invalid_message_id template.


  • Fixed an error that was causing LOG_LEVELS to not display correctly.

Version 1.8.4

  • The Sentry base client will now pass along the timestamp from when the message was generated.


  • Fixed a case where the client may hit a transaction aborted error when transforming variables.

Version 1.8.3

  • Added several settings which were Django specific so that they can be configured isolated to the Sentry instance.
  • Graceful failover for when a cache backend isnt working properly and throttling is enabled.
  • Better rendering of non-dict variables when passed within extra data.
  • Graceful failover for searching on message_id’s that aren’t found.

Version 1.8.0

  • Refactored Sentry server to run standalone (sentry –help).

Version 1.7.5

  • Implemented new client/server storage API and signing methods.
  • Fixed a bug where accessing __sentry__ would sometimes cause errors on certain code paths.

Version 1.7.4

  • Fixed a bug with potential recursion issues.
  • Fixed a bug with the storage API and unicode keys.

Version 1.7.3

  • Storage API has better responses when data fails to decode, or you send a bad request.
  • Documentation improvements for JSON storage API.

Version 1.7.2

  • All strings, lists, tuples, and sets are now shortened before sending to the server. Iterable data structures are truncated to the first 50 items, and strings are truncated to the first 200 characters.

    Both shorteners have configurable values in the settings.

Version 1.7.1

  • Fixed a bug that slipped through with blocktrans usage.

Version 1.7.0

  • Added score to GroupedMessage (schema change).
  • Added MessageIndex (schema change).
  • Added Async client (thanks to Yuri Baburov).
  • Added support for raw_post_data (thanks to Matthew Schinckel).
  • django-paging and django-indexer no longer need to be in INSTALLED_APPS.
  • Added an index for GroupedMessages.times_seen.
  • The score column will update atomically in PostgreSQL and MySQL.
  • Added the frequency sort option.
  • Better internationalization support.
  • Fixed a bug with Oracle’s date truncation support (changed to hh24).
  • Respect TIME_ZONE by using auto_now_* on DateTimeField’s.
  • Tests required Haystack and Celery are now skipped if module is not found.

Version 1.6.10

  • Added JSON support to storage API.
  • Changed default client to use JSON format.


  • Fixed an issue with encoding to UTF-8 for Haystack.

Version 1.6.9

  • Added URLs to default search parameters.
  • Fixed a bug to ensure template information is only added if its the correct loader


  • Search will now show when unauthenticated (e.g. when SENTRY_PUBLIC is enabled)

Version 1.6.8

  • Search no longer allows filters.
  • Search no longer allows arbitrary queries without Haystack.
  • Added logger, level, site, server, and url to search index.
  • Haystack has been updated for further flexibility.
  • SearchFilter is now unused (you should update your configs).

Version 1.6.7

  • Moved static media into /static/.
  • Added serve_static view to handle static media solely within Sentry.

Version 1.6.6

  • install will no longer install example_project.
  • Fixed an issue where __sentry__ would be called even if it wasn’t a callable.
  • Fixed an issue where transactions would attempt a rollback when not managed while creating the sort index.

Version 1.8.8

  • Set a last_message_id so when thrashing is hit there is still a point of reference for tracing.
  • Check correct permissions for Sentry.

Version 1.6.4

  • Fixed a memory leak due to TextNode’s being created from leading whitespace in realtime packets.

Version 1.6.3

  • Fixed a critical bug in the Sentry JS namespace preventing it from loading.

Version 1.6.2

  • LogHandler will attempt to pick up the request automatically using SentryLogMiddleware.
  • Updated AJAX CSRF support for Django 1.2.5.
  • request.sentry is now set in any event which has request as part of the parameters.

Version 1.6.0

  • Added message references (uuid’s) as message_id in Message
  • Fixed css compatibility issues with TextWidget
  • SearchFilter now allows searching by message reference id
  • Added Sentry404CatchMiddleware
  • Added SentryResponseErrorIdMiddleware
  • The request argument can now be passed into any create_from_ method.

(History beyond 1.6.0 is not present)