Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add log entries as breadcrumbs for Sentry events #38

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

kdambekalns
Copy link
Member

@kdambekalns kdambekalns commented Nov 18, 2024

Resolves #31

This now has three different modes:

- for testing message capturing
- for testing exception handling
- for testing error handling
Instead of setting up the Sentry client when something needs to be
sent to Sentry in the `SentryStorage` this initializes the Sentry
client as soon as Flow's object management is usable.

This allows to use Sentry to capture exceptions and errors as early
as possible.
This activates the default integrations shipped with Sentry again.

This adds information about installed Composer packages, the request,
frame context and environment.

Through this, some "custom" tags can be dropped, as the information is
included by the default integrations.

Since Sentry registers an error handler, errors not handled by the
exception handler will also be recorded in Sentry.
There may have been changes after Sentry was initialised first, so
re-run `setTags()` when sending events to Sentry.
@kdambekalns kdambekalns self-assigned this Nov 18, 2024
@kdambekalns
Copy link
Member Author

This should probably be configured for the security logger, too…

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Logger for Sentry no longer active since PSR-3 introduction
1 participant