Fill out the template below. Any pull request that does not include enough information to be reviewed in a timely manner may be closed at the maintainers' discretion.
The pull request must only fix one issue at the time.
The pull request must update the test suite to demonstrate the changed functionality.
After you create the pull request, all status checks must be pass before a maintainer reviews your contribution. For more details, please see CONTRIBUTING.
What does this PR do?
Currently, the filtering of events was limited to a toggle which turned on/off categories of events with no granular control of specific events to be sent.
Filtering is done by adding names for all the events and having users manually write include/exclude lists of specific events that they do/don't want. The higher level control of the toggles are still available but more specific include/excludes can be done with these lists. The config changed event was also removed completely as this event was blocked by the events team.
Requirements for Contributing to this repository
What does this PR do?
Currently, the filtering of events was limited to a toggle which turned on/off categories of events with no granular control of specific events to be sent.
Link to Issue
Description of the Change
Filtering is done by adding names for all the events and having users manually write include/exclude lists of specific events that they do/don't want. The higher level control of the toggles are still available but more specific include/excludes can be done with these lists. The config changed event was also removed completely as this event was blocked by the events team.
Alternate Designs & Possible Drawbacks
Link to RFC discussing this
Verification Process
Link to testing plan for unit and manual testing
Additional Notes
Release Notes
Review checklist (to be filled by reviewers)
changelog/label attached. If applicable it should have thebackward-incompatiblelabel attached.do-not-merge/label attached.kind/andseverity/labels attached at least.