Sentry error reporting adapter implementation.
This adapter integrates with Sentry (https://sentry.io) for production error tracking and monitoring. It implements all error reporting protocols to provide comprehensive exception tracking, context management, and alerting capabilities.
Features:
Configuration: The adapter requires a Sentry DSN (Data Source Name) and optionally accepts:
Example: (def sentry-reporter (create-sentry-error-reporter {:dsn "https://your-dsn@sentry.io/project-id" :environment "production" :release "1.0.0" :sample-rate 1.0 :debug false}))
Sentry error reporting adapter implementation.
This adapter integrates with Sentry (https://sentry.io) for production error tracking
and monitoring. It implements all error reporting protocols to provide comprehensive
exception tracking, context management, and alerting capabilities.
Features:
- Exception capture with stack traces
- Message-level reporting (debug, info, warning, error, fatal)
- Context management (user, tags, extra data, breadcrumbs)
- Environment and release tracking
- Sampling and filtering capabilities
- Runtime configuration management
Configuration:
The adapter requires a Sentry DSN (Data Source Name) and optionally accepts:
- Environment name (dev, staging, prod)
- Release identifier
- Sample rate (0.0 to 1.0)
- Debug mode flag
- Server name
Example:
(def sentry-reporter
(create-sentry-error-reporter
{:dsn "https://your-dsn@sentry.io/project-id"
:environment "production"
:release "1.0.0"
:sample-rate 1.0
:debug false}))(create-sentry-error-context config)Create a Sentry error context manager instance.
Create a Sentry error context manager instance.
(create-sentry-error-filter config)Create a Sentry error filter instance.
Create a Sentry error filter instance.
(create-sentry-error-reporter config)Create a Sentry error reporter instance.
Config map should contain:
Example: (create-sentry-error-reporter {:dsn "https://your-dsn@sentry.io/project-id" :environment "production" :release "1.0.0" :sample-rate 1.0})
Create a Sentry error reporter instance.
Config map should contain:
- :dsn (required) - Sentry Data Source Name
- :environment (optional) - Environment name (dev, staging, prod)
- :release (optional) - Release identifier
- :sample-rate (optional) - Sample rate 0.0 to 1.0 (default 1.0)
- :debug (optional) - Enable debug mode (default false)
- :server-name (optional) - Server name for grouping
Example:
(create-sentry-error-reporter
{:dsn "https://your-dsn@sentry.io/project-id"
:environment "production"
:release "1.0.0"
:sample-rate 1.0})(create-sentry-error-reporting-component config)Create a complete Sentry error reporting component that implements all protocols.
This is the recommended way to create Sentry error reporting for use with Integrant.
Create a complete Sentry error reporting component that implements all protocols. This is the recommended way to create Sentry error reporting for use with Integrant.
(create-sentry-error-reporting-components config)Create a map of Sentry error reporting components for Integrant system configuration.
Returns a map with keys:
Create a map of Sentry error reporting components for Integrant system configuration. Returns a map with keys: - :error-reporter - IErrorReporter implementation - :error-context - IErrorContext implementation - :error-filter - IErrorFilter implementation - :error-config - IErrorReportingConfig implementation
(create-sentry-error-reporting-config config)Create a Sentry error reporting configuration manager instance.
Create a Sentry error reporting configuration manager instance.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |