PHPackages                             honsa/typo3-sentry - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Logging & Monitoring](/categories/logging)
4. /
5. honsa/typo3-sentry

ActiveTypo3-cms-extension[Logging & Monitoring](/categories/logging)

honsa/typo3-sentry
==================

Sentry Logger for TYPO3 CMS

1.0.9(3mo ago)020MITPHPPHP >=8.2

Since Mar 12Pushed 3mo agoCompare

[ Source](https://github.com/honsa/typo3-sentry)[ Packagist](https://packagist.org/packages/honsa/typo3-sentry)[ Docs](https://github.com/honsa)[ RSS](/packages/honsa-typo3-sentry/feed)WikiDiscussions main Synced 3w ago

READMEChangelogDependencies (16)Versions (12)Used By (0)

Sentry Logger for TYPO3 CMS
===========================

[](#sentry-logger-for-typo3-cms)

A TYPO3 13 extension that forwards TYPO3 logs to Sentry via a configurable custom LogWriter.

- TYPO3: 13.4+
- PHP: 8.2+
- Library: sentry/sentry ^4.3

Installation
------------

[](#installation)

Require the package via Composer and activate the extension in TYPO3:

```
composer require honsa/typo3-sentry
```

TYPO3 extension key: `sentry_logger`

Configuration (extension settings)
----------------------------------

[](#configuration-extension-settings)

The extension reads its configuration from the Extension Configuration (Install Tool / Extension Manager). The `ext_conf_template.txt` shipped with the extension exposes the supported public keys, and the table below mirrors that contract.

KeyTypeDefaultDescriptionfeatures.enableboolean1Enable Sentry log forwarding. Set to 0 to disable processing.connection.dsnstring(empty)Sentry DSN. If empty, the writer will try env `SENTRY_DSN` and will be effectively disabled without a DSN.connection.environmentstring`SENTRY_ENVIRONMENT`, then `APP_ENV`, then `production`Environment attached to Sentry events.connection.releasestring`SENTRY_RELEASE`, otherwise emptyRelease identifier attached to Sentry events.sampling.tracesSampleRatefloat0.0Trace sampling rate passed to the Sentry SDK.sampling.profilesSampleRatefloat0.0Profile sampling rate passed to the Sentry SDK.filter.enabledLogLevelsstring`warning,error,critical,alert,emergency`Comma-separated PSR-3 levels that are forwarded.filter.captureExceptionsOnlyboolean0If enabled, only records that contain an `exception` in the log context are forwarded.context.staticTagsstring(empty)Semicolon-separated `key:value` tags added to every Sentry event. Avoid secrets.context.staticExtrasstring(empty)Semicolon-separated `key:value` extras added to every Sentry event. Secret-like keys are redacted automatically.Notes:

If `features.enable = 0` or no DSN is available, the writer short-circuits and does nothing.

By default the writer forwards `warning` and above. To include `debug`, `info`, or `notice`, expand `filter.enabledLogLevels` in the extension configuration.

Security behavior:

- Log context is sanitized before being sent to Sentry. Keys such as `password`, `token`, `authorization`, `cookie`, `session`, `csrf`, `api_key`, and similar secret-like names are replaced with `[REDACTED]`, including in nested arrays and `JsonSerializable` payloads.
- Internal writer failures are reported via PHP's error log to avoid silently losing telemetry while also avoiding TYPO3 log-recursion.

Enable the writer
-----------------

[](#enable-the-writer)

Adjust your global logging config if needed (example in `config/system/additional.php`):

```