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

Implement improved ignore list #86

Open
4 of 7 tasks
hlubek opened this issue Aug 1, 2023 · 3 comments
Open
4 of 7 tasks

Implement improved ignore list #86

hlubek opened this issue Aug 1, 2023 · 3 comments

Comments

@hlubek
Copy link

hlubek commented Aug 1, 2023

Goals:

  • Deprecate "blacklist" because of inappropriate naming (but still accept the old configuration option to keep it compatible)
  • Use "ignorelist" as the new name (configuration options and classes)
  • Extend exception ignore lists based on:
    • Message regexp
    • Class regexp -> provide examples due to escaping / backslashes
    • Exception code
  • Document example to readme

This way we could configure a common list of "client" exceptions that cause too much noise in Sentry and are due to e.g. bad route parameters, property mapping or form validation.

@baschny
Copy link

baschny commented Aug 9, 2023

In the long run it would be cool to implement black/whitelist of log entries directly in TYPO3 core instead that each client / LogWriter inventing their own settings. So we could use this also for the FileWriter and other logging services.

@christophlehmann
Copy link
Contributor

To be ignored Exception codes should go into core if possible

@christophlehmann
Copy link
Contributor

Exception classes can now be ignored with ignore_exceptions

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

No branches or pull requests

3 participants