forked from getsentry/sentry
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathCHANGES
1124 lines (816 loc) · 37 KB
/
CHANGES
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Version 7.0.0
-------------
- 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 are the preferred replacement.
Version 6.4.0
-------------
Some major backend changes are introduced in Sentry 6.4.0.
django.contrib.auth
===================
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.
Search
======
Search has been abstracted from the simple search manager, and now lives within
``sentry.search``. Currently only the Django backend is supported, but some sample
code for Solr Cloud integration is also available.
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 ``sentry.utils.email``.
- 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:
https://github.com/getsentry/sentry/commit/5793c6cac19aeb7d2e19f9a09f4421b771af4306
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.
- 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.
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.
Additionally:
- 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 on the quickstart 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``.
Additionally:
- 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::
sentry.plugins.sentry_useragents
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.
Additionally:
- 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.
Additionally:
- 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 (https://github.com/dcramer/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 SENTRY_MAIL_INCLUDE_LOGGERS setting.
* Added SENTRY_MAIL_EXCLUDE_LOGGERS 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).
Version 1.8.6.2
---------------
* Reverted change which required distribute.
* Cleaned up configuration defaults.
Version 1.8.6.1
---------------
* Include distribute_setup.py 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/sentry.conf.py if --config is not passed to it.
Version 1.8.5.1
---------------
* 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.
Version 1.8.4.2
---------------
* Added missing invalid_message_id template.
Version 1.8.4.1
---------------
* 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.
Version 1.8.3.1
---------------
* 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.