Handle edge cases in filtering

**Feature request**
It would be great to have analytics for parsers.

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

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

The issue does not identify files, tests, parser entry points, or which analytics are required. Start by locating the parser and configuration entry points, then clarify the analytics scope and how production data should be handled; done means the option defaults to false and the agreed parser analytics behavior is covered by tests.

Written by the indexing model from the issue text.