- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
Why monitor from ServiceNow?
A handful of vendors have built SQL Server and Exchange performance products that can be deployed to collect performance metrics. So Why do the Monitor from your ServiceNow Instance? The short answer is "why not"? Monitoring from ServiceNow will allow you to integrate processes like change, CMDB, incident with your SQL and Exchange monitoring. Since MSSQL and Exchange supports critical business services, why not take advantage of all the benefits of running the monitoring side to side with your discovery, incident, event management and other applications?
With the latest release of Evanios Monitoring, You can now monitor your MS-SQL databases and MS-Exchange directly from ServiceNow. An out of the box Module was created to help you monitor your databases and Exchange instances in no time. The monitoring provisioning, thresholds settings, metric graphs, incident creation … all happens directly from your ServiceNow instance. The Evanios Agents that gets installed on premise will collect MS-SQL and MS-Exchange availability, performance and capacity metrics and forward the data to ServiceNow for analysis. Database Status, deadlocks, cache hit ratio, space utilization, critical services and counters will be collected immediately.
Some of the benefits are:
- Automatic provisioning: Once a SQL database is discovered, it can be provisioned automatically based on the business service it's supporting.
- Automatically adjust the provisioning: When a SQL database or Exchange instance move from staging to production, the monitoring setting will be adjusted automatically.
- Unified Dashboard: See metrics data for your instance, critical tickets and other related information on the same dashboard.
- Time Sensitive Operations: Configure separate set of alerting thresholds for your MSSQL and Exchange metrics during a scheduled change window.
BSM Maps: Shows the MS-SQL database in major state.
Event details that generated this failure:
Historical graph of the metric:
There are many other reasons as to why you would want to collocate your monitoring with your ITSM and other modules on the same platform. You can try it for yourself and let me know your findings.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.