flownative/sentry

Last activity on 5 May 2020
  • 3
  • 1008
composer require flownative/sentry

A Sentry integration for Neos Flow

0.3.0

A Sentry integration for Neos Flow

Version
0.3.0
Type
neos-package
Release Date
08.05.2020 08:25:18
Source
git
Distribution
zip
Requires
Requires (dev)
None
Suggest
None
Provides
None
Conflicts
None
Replaces
None
MIT fe27127708b5c4ac2d89e9fb2101a9c4d38ca528

MIT license Packagist Maintenance level: Love

Sentry integration for Flow 5.x and Flow 6.x

This Flow package allows you to automate reporting of errors to Sentry

Key Features

Installation

The Sentry integration is installed as a regular Flow package via Composer. For your existing project, simply include flownative/sentry into the dependencies of your Flow or Neos distribution:

$ composer require flownative/sentry

Configuration

You need to at least specify a DSN to be used as a logging target. Apart from that, you can configure the Sentry environment and release. All options can either be set in the Flow settings or, more conveniently, by setting the respective environment variables.

Flownative:
  Sentry:
    dsn: "%env:SENTRY_DSN%"
    environment: "%env:SENTRY_ENVIRONMENT%"
    release: "%env:SENTRY_RELEASE%"

Throwables (that includes exceptions and runtime errors) are logged as Sentry events. You may specify a list of exceptions which should not be recorded. If such an exception is thrown, it will only be logged as a "notice".

Flownative:
  Sentry:
    capture:
      excludeExceptionTypes:
        - 'Neos\Flow\Mvc\Controller\Exception\InvalidControllerException'

If an ignore exception is handled by this Sentry client, it is logged similar to the following message:

… NOTICE Exception 12345: The exception message (Ref: 202004161706040c28ae | Sentry: ignored)
The content of the readme is provided by Github
The same vendor provides 39 package(s).