If you are using DPA to monitor both instances (the one hosting the primary replica and the one hosting the secondary replica), yes.
You can do a report on the read-only instance just on the program in question or databases. Better yet though, you can go into trends for the secondary and drill in through the programs dimension to see all activity. This will show you who, what, where, when is being sent to the secondary read-only replica to be serviced.
Let me know if you need more detail on how to do this, but you should have the ability to definitely show/see secondary usage.
hi, yes I would definitely like to know how to do this.
currently our AG setup is within a AG Cluster so all under the
same monitor, will that need to be redone?
it would be nice not to have to do redo the clusters.
I'd need to know a little more about your monitoring setup.
If you are monitoring using the AG listener, then we'll follow the primary replica. Regardless of which instance it currently lives on. So we'll only "see" activity on the primary, nothing from the secondary.
Might be worth opening a case with support. Let them know we've discussed this a bit and it would be worth hopping on a call to run through what you can do with AGs and visibility.
ok thanks yes I was not able to see much on the secondary's at all, we have it following the listener on the AG so it is following the primary. only data I can see on secondary nodes is if it in sync, etc. nothing of what we want to see
thanks much, Susie