Handle edge cases in import

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

**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 file, test, or entry point. Start by locating how configuration options are parsed and where production analytics would be emitted; clarify what data analytics should collect and how it is enabled. Done means a disabled-by-default enable_analytics option is supported with documented behavior and coverage for both default and enabled states.

Written by the indexing model from the issue text.