Sentry

Configure Sentry to watch services and it will collect errors and problems inside its dashboard.

Developers can then inspect them in detail and take the appropriate course of action.

Sentry is a must-have tool for developers performing testing/debugging or for customer care services.

Sentry can work with services in Python (Django, Flask), Node.js (Connect, Express), JavaScript, PHP and Java.

What is new in this release:

• 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.
• Added Release.new_groups column.
• The explore feature is now deprecated and links have been hidden.
• Expanded various API endpoints for future usage.
• Initial prototype of embeddable crash reports. This adds the UserReport model.
• Added basic UI reporting for status checks.
• Added celery/beat alive check.
• Added celery app version check.
• Added queue overview to internal administration.
• Upped TSDB's storage of 10s to 60m of data.
• Added protocol version 7 to client spec.

What is new in version 7.5.3:

• 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.

What is new in version 7.4.3:

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

What is new in version 7.3.2:

• Fixed missing beacon task import.

What is new in 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.

What is new in version 7.1.1:

• Suggest realip module over X-Forwarded-For.

What is new in version 7.0.0:

• 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.

What is new in version 6.4.0:

• Some initial support for time zones (user setting).
• 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 ``sentry.utils.email``.
• 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.
• Search has been abstracted from the simple search manager, and now lives within ``sentry.search``.
• A new application called ``nodestore`` now manages the event blob data.

What is new in 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.

What is new in 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.

What is new in version 6.1.0:

• Added Rate Limit controls.

What is new in version 6.0.0:

• 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.

What is new in version 5.4.0:

• 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).

What is new in version 5.3.2:

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

What is new in version 5.2.2:

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

What is new in version 5.1.0:

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

What is new in version 5.0.5:

• 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.

What is new in 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.

What is new in version 4.9.0:

• Social authentication is now supported. GitHub, Twitter, Facebook and Google are supported.

What is new in version 4.8.0:

• Tags are now able to be created dynamically.
• Can also configure which tags will show up as filters in the sidebar via a project's settings page. By default all tags will show up.

What is new in version 4.7.7:

• 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.

What is new in version 4.6.0:

• Changing "Top Events" to "Trends" (if supported by your RDBMS).
• Time interval selections for both widgets.
• 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).

What is new in version 4.5.1:

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

What is new in version 4.4.1:

• Two new columns were added to the ``Group`` model.
• The dashboard's "New Events" will now use the active_at date rather than the original first seen date on an event.