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 names no files, tests, or entry points. Start by locating the parser configuration and analytics-related code, then determine what analytics should report and where the output belongs. Done requires a documented `enable_analytics` option defaulting to `false`, with agreed behavior for parser analytics and coverage by tests.

Written by the indexing model from the issue text.