Sentry

Sentry is a realtime event logging and aggregation platform. At its core it specializes in monitoring errors and extracting all the information needed to do a proper post-mortem without any of the hassle of the standard user feedback loop.

Users Guide

• Quickstart
  • Hardware
  • Setting up an Environment
  • Install Sentry
  • Initializing the Configuration
  • Configure Outbound Mail
  • Running Migrations
  • Starting the Web Service
  • Setup a Reverse Proxy
  • Running Sentry as a Service
  • Additional Utilities
  • Enabling Social Auth
  • What’s Next?
• Upgrading
  • Upgrading from 1.x
  • Upgrading to >= 5.1
  • Upgrading from <= 5.3
• Configuration
  • Authentication
  • Notifications
  • Services
• Utilizing the Queue
  • Running a Worker
  • Enable the Queue
• Utilizing Update Buffers
  • Available Backends
  • The Redis Backend
• Utilizing the UDP Server
  • Configuration
• Throttles and Rate Limiting
  • Rate Limiting with IPTables
  • Enabling Quotas
  • Using Cyclops (Client Proxy)
• Command Line Usage
  • Builtin Commands
• Available Clients
  • Client Criteria
• Plugins
  • Bundled Plugins
  • 3rd Party Extensions

Developers

• Contributing
  • Localization
  • Developing Against HEAD
  • Coding Standards
  • Running the Test Suite
  • Static Media
  • Developing with Django
  • Contributing Back Code
• Writing a Client
  • Client Usage (End-user)
  • Parsing the DSN
  • Building the JSON Packet
  • Authentication
  • A Working Example
  • Reading the Response
  • Handling Failures
  • Scrubbing Data
  • Tags
• Writing a Plugin
  • Structure
  • Next Steps
• Interfaces
  • Aliases
  • Provided Interfaces

Reference

• Changelog
• Incompatible Changes
• Protocol Version 4
• Alerts
• Filters
• Other Changes
• Protocol Version 3
• Other Changes
• License

Resources

• Transifex (Translate Sentry!)
• Bug Tracker
• Code
• Mailing List
• IRC (irc.freenode.net, #sentry)

Screenshots

Aggregated Events

Event Details

Deprecation Notes

Milestones releases are 1.3 or 1.4, and our deprecation policy is to a two version step. For example, a feature will be deprecated in 1.3, and completely removed in 1.4.