Externally hosted exclusion rules

[RobinHoutevelts]

Summary

This modules supports dropping unwanted logs through the excluded_exceptions and excluded_tags config options. However, we (Wieni, the web agency) want the possibility to consolidate some exclusions for our entire organization.

For example when we identify a new tag or exception that we want to exclude, we don't want to have to update the wmsentry config in all our projects. As a workaround we used inbound filters, but that's only available when you have a Business subscription at Sentry. We moved to a Teams subscription so are looking for a new workaround.

Proposal

A new exclusion_remote_config option where you can enter a url to fetch extra exclusion config.

exclusion_remote_config: 'https://s3.eu-central-1.amazonaws.com/org-wmsentry-config/wmsentry.config.yaml'

The content at https://s3.eu-central-1.amazonaws.com/org-wmsentry-config/wmsentry.config.yaml is:

excluded_exceptions:
  - Drupal\my_module\Exception\SomeException
excluded_tags:
  - tag: channel
    value: 'some channel'

If we want to add a new excluded exception to all our projects, we would only need to update the yaml file stored on S3. Cron will check if the yaml file on s3 has changed and will reconfigure wmsentry if needed.

[spoit]

Why S3 and not.. github?