Add rate limiting for monitoring

**Feature request**
It would be great to have filtering for types.

**Use case**
Many users need this functionality for production deployments.

**Implementation idea**
Add a new config option `enable_filtering` with default `false`.

No files, tests, or entry points are named. Start by locating the monitoring configuration and filtering paths, then clarify which types should be filtered and how that relates to rate limiting; done means the new enable_filtering option defaults to false and the agreed filtering behavior is covered.

Written by the indexing model from the issue text.