When promoting a replica set to a sharded cluster (with a dedicated config server) we do not copy docs from config.queryAnalyzers on the replica set to the config server as we do with cluster parameters. This means that query analysis will stop if a replica set is promoted to a sharded cluster. There is a docs ticket to document this behavior, but we should consider whether we want to update the promotion to sharded/addShard to preserve this documents instead.