We are looking at simple up/down for some of our Databases, as I am bringing them under the Application diagram and want health rollup for critical status.
We eventually will get to Application specific synthetic transactions that can tell us more than simple up/down of a DB, but if information is being handled and processed properly and in a timely manner. However, we're a little ways away from that. I want to get our dashboards accurately representing our applications and dependencies. >From a simplistic health rollup, to know when a DB is inaccessible (and >without asking you to do my work for me) would you create a generic monitor >targeted at 'SQL Database' to run a simple up/down check? Then DBs inherit the >check and will be included in health rollups? Or would you target the specific >DBs as part of the instances of the class being created? Thanks, Geoff From: [email protected] [mailto:[email protected]] On Behalf Of Kevin Holman Sent: Wednesday, September 16, 2015 10:37 AM To: [email protected] Subject: [msmom] RE: SQL MP Question: I think the assumption is, that if a database had a critical issue, there are events that would be picked up quickly that would generate alerts. The goal of the DB status monitor is to reflect a health state in the console for online, or not online status. This is a bit heavier handed script based monitor, and on servers with a VERY large number of DB's, this could have an impact running against a large number of DB's and script based monitoring workflows have the biggest impact on the client computer. I would imagine it could be set to a more frequent setting, but I am not sure how much value you'd get from it. Highly critical databases should have synthetic transactions set up from a remote watcher node, which check their availability to an application from the perspective of connect-ability, and response time for query execution. This monitor was changed from every 120 seconds to every 3600 seconds in version 6.0.6648.0 which released around July 2009. Unfortunately - the SQL MP guide did not document that this was change nor why it was changed. I'd say - if you feel there is value in setting it more frequently - you can do this and just try to determine if it uses a lot of resources when it runs or not in your environment. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Orlebeck, Geoffrey Sent: Wednesday, September 16, 2015 12:02 PM To: '[email protected]' <[email protected]<mailto:[email protected]>> Subject: [msmom] SQL MP Question: I am adding some application SQL databases to our Distributed Application view and noticed the 'Database Status' monitor (Availability > Database Status) is set by default to run every 3600 seconds (1 hour). That seems like an awfully long time to check on a DB's availability. However, never having worked with this MP before, is there a significant impact of wanting to check on DB health every 5-10mins? Or should that be used sparingly-only check your most critical DBs every 5-10mins? Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you. Confidentiality Notice: This is a transmission from Community Hospital of the Monterey Peninsula. This message and any attached documents may be confidential and contain information protected by state and federal medical privacy statutes. They are intended only for the use of the addressee. If you are not the intended recipient, any disclosure, copying, or distribution of this information is strictly prohibited. If you received this transmission in error, please accept our apologies and notify the sender. Thank you.
