Can the Sybase_RS agent separate the latency from one primary database to another? (4265161)

The route serves as the one bridge connecting all the transactions coming from the primary database in that replication server to a target replication server. Can the Sybase_RS agent separate the latency from one primary database to another? For example, if 3 primary databases send all their transactions to one routes will Foglight be able to identify the latency individually and how each primary database's transactions go through that route?

No, the Foglight Sybase_RS agent won't be able to separate the latency from one primary database to another. This is currently not supported.