|摘要||Sentry 是一个实时的事件日志和聚合平台，基于 Django 构建。Sentry 可以帮助你将 Python 程序的所有 exception 自动记录下来，然后在一个好用的 UI 上呈现和搜索。处理 exception 是每个程序的必要部分，所以 Sentry 也几乎可以说是所有项目的必备组件。Sentry 8.0.0-rc1 发布，主要更新如下：-Sourcebuildsnowrequire...|
Sentry 是一个实时的事件日志和聚合平台，基于 Django 构建。Sentry 可以帮助你将 Python 程序的所有 exception 自动记录下来，然后在一个好用的 UI 上呈现和搜索。处理 exception 是每个程序的必要部分，所以 Sentry 也几乎可以说是所有项目的必备组件。
Sentry 8.0.0-rc1 发布，主要更新如下：
- Source builds now require Node 0.12.x or newer. - The ``public`` setting on projects has been removed - This also removes ``SENTRY_ALLOW_PUBLIC_PROJECTS`` - Clients which were only sending ``sentry_key`` and not using CORS will no longer be able to authenticate. - All incoming events now log through ``sentry.api``, which will additionally capture far more events with improved console formatting. - The 'sentry' user can no longer be removed. - The Cassandra nodestore backend was broken, and this has been resolved. - The ``has_perm`` plugin hook is no longer used. - Do not unconditionally map sys.stdout to sys.stderr - The HTTP interface's internal structure has greatly changed. Headers and Cookies are now lists. Body is now stored as a string. - The internal metrics backend now supports both Datadog and a simple logging implementation (useful in DEBUG). - Member roles can now view client keys (DSNs). - Documentation for configuration wizards is now pulled from docs.getsentry.com as part of the ``upgrade`` and ``repair`` processes. - The SSO flow for existing users has been greatly improved to avoid duplicate accounts. - Deletions are delayed for one hour and can be cancelled by changing the status back to ``VISIBLE``. - Membership permissions have been overhauled and have been flattened into a single tiered role. Additionally owners will no longer be automatically added to new teams. - ``NotificationPlugin`` now requires ``is_configured`` to be declared.