Writing to Kentico log in an Active/Active (geo-replicated) database scenario

I'm not exactly sure what you are trying to achieve.

Configure the logger with a separate connection string

When you write "logger", what do you mean exactly? The Event Log (CMS_EventLog table) or a change/event log (which would probably be the CMS_WebFarmServerTask table)?

There's nothing, that I know of, in Kentico Xperience that lets you do a CQRS separation of data persistence.

You can specify separate connection strings per application, or even per custom module class, but not reads vs writes.

Is the geo-replication to improve performance of reads at distance locations?

Maybe there's a way to do this natively at a lower level with SQL Server replication, but I'm not experienced in that area.

Thanks for the answer @Sean. In an active/active scenario you have the MVC site deployed in multiple regions, in order to minimize latency in that region. In order for the optimization to be effective, all assets need to reside in the same region or as close as possble: Web app, database, cache, etc. The database needs to be part of a active/active failover group. That means that only one database is read/write and the replications are read only. That means that the MVC site cannot write to the log. A solution I am thinking about involves writing log entries to an in-memory queue and have a background process read that queue and send REST API calls to the admin site in order to write to the database.