Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Features Monitoring Replication #1007

Open
aachaemenes opened this issue Sep 17, 2024 · 1 comment
Open

Add Features Monitoring Replication #1007

aachaemenes opened this issue Sep 17, 2024 · 1 comment

Comments

@aachaemenes
Copy link

Please add a feature to monitor transactional replications.

@DavidWiseman
Copy link
Collaborator

Hi,

Thanks for the suggestion. This isn't a feature I currently use and it's not something I have any experience with outside of a lab environment. I'm unlikely to add any replication monitoring features unless it gets adopted somewhere within Trimble.

Depending on what you want to track, I think there are some replication metrics available in sys.dm_os_performance_counters. You can add any counters from here into DBA Dash by editing an XML file to include it. The process is documented here. The link also explains how to add custom metrics from a SQL query - providing flexibility to add any custom metric.

Another option is a custom collection and custom report which provides more flexibility on how to store and process the data. I use this feature now to prototype new collections. e.g. Server Services & Table Size.

If you build something with this, consider scripting out the custom collection and associated report to share with other DBA Dash users. There would be a bit more work to convert it to a system collection/report but this might also be an option. DBA Dash is open source - pull requests would be considered to add replication monitoring.

Hope this helps,

David

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants