AdvisorHello,
Just wondering if anyone developed DS to monitoring Exchange DAG so far? That monitoring is really important on our current tool...
If not, I guess we can develop one but, prior to that I just wanna make sure there's nothing out there already.
Thank you in advance!
AdvisorWe've ended up creating a DS to cover our monitoring necessities.
In case it's useful for you guys -> here
AdvisorHello can anyone from LM who wrote the Exchange related Data Sources chime in here?
We need the above KPI's for DAG related metrics to properly monitor Exchange. The terminology difference is not clear for which Exchange DS Data Points correlate to the above ones we need to monitor.
AdvisorWe are looking for these specific DAG metrics in LogicMonitor:
| ContentIndexState | Indicates the current state of the content index for a database copy. |
| CopyQueueLength-DAG | Shows the number of transaction log files waiting to be copied to the passive copy log file folder. A copy isn't considered complete until it has been checked for corruption. |
| DAG Network Down | One or more networks supporting the database availability group are not operating properly on this server. |
| Database copies status-DisconnectedAndHealthy | The mailbox database copy is no longer connected to the active database copy, and it was in the Healthy state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy. |
| Database copies status-DisconnectedAndResynchronizing | The mailbox database copy is no longer connected to the active database copy, and it was in the Resynchronizing state when the loss of connection occurred. This state represents the database copy with respect to connectivity to its source database copy. It may be reported during DAG network failures between the source copy and the target database copy. |
| Database copies status-Dismounted | The active copy is offline and not accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounted. |
| Database copies status-Dismounting | The active copy is going offline and terminating client connections. Only the active copy of the mailbox database copy can have a copy status of Dismounting. |
| Database copies status-Failed | The mailbox database copy is in a Failed state because it isn't suspended, and it isn't able to copy or replay log files. While in a Failed state and not suspended, the system will periodically check whether the problem that caused the copy status to change to Failed has been resolved. After the system has detected that the problem is resolved, and barring no other issues, the copy status will automatically change to Healthy. |
| Database copies status-FailedAndSuspended | The Failed and Suspended states have been set simultaneously by the system because a failure was detected, and because resolution of the failure explicitly requires administrator intervention. An example is if the system detects unrecoverable divergence between the active mailbox database and a database copy. Unlike the Failed state, the system won't periodically check whether the problem has been resolved, and automatically recover. Instead, an administrator must intervene to resolve the underlying cause of the failure before the database copy can be transitioned to a healthy state. |
| Database copies status-Healthy | The mailbox database copy is successfully copying and replaying log files, or it has successfully copied and replayed all available log files. |
| Database copies status-Mounted | The active copy is online and accepting client connections. Only the active copy of the mailbox database copy can have a copy status of Mounted. |
| Database copies status-Suspended | The mailbox database copy is in a Suspended state as a result of an administrator manually suspending the database copy by running the Suspend-MailboxDatabaseCopy cmdlet. |
| Stale security information -Cluster File Share Witness | The database availability group is experiencing problems that may cause it to eventually fail due to stale security information. |
| Stale security information -Quorum Group | The database availability group is experiencing problems that may cause it to fail due to stale security information. |
Advisor
I searched on the Exchange & the one from LM but didn't found metrics related with it (maybe I missed something 
)
