Handle edge cases in serialization

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

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

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

No files, tests, or entry points are named. Start by locating configuration parsing, serialization, and any existing service-related analytics code, then determine what analytics the new option controls. Done should include a documented `enable_analytics` option defaulting to `false` and clearly defined production behavior.

Written by the indexing model from the issue text.