Apple Footer. This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums.
Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the.
Hi Spice Boys/Girls! I'm working on setting up various monitoring/alert-settings for one of our webservers, the server is one of our customers dedicated/colocation servers, they have booth the IIS and the SQL server running on this one single machine, the webaplications are generating a lot of disk I/O and since disk errors would cause a lot of potential data loss we would like to get instant notifications via email when one of the disks are starting to experience problems. I have set up the monitoring under the Events category, is this where I specify windows error event id's? If so, does anyone have a list of the most common event id's to look out for? (event id's that might indicate an imminent disk failure) /Jimmy. Hi Jimmy, The info posted by DBeer is perfect, but I wanted to note that you want 'instant' notifications when Events are thrown indicating disk or I/O errors. Depending on your definition of 'instant' you might find this information useful: Spiceworks scans for new events on remote devices based on your scheduled scans, so events are not picked up 'real time'.
If you have Spiceworks configured to scan every 12 hours, you can see how long it might be before you are notified of an event being created. Certain alerts are more timely, as up/down state and networking device information are scanned for far more frequently.
If you need notification instantly you might need to use a more advanced monitoring system like Nagios.
Dec 3, 2016 - Recently, I had someone clean up/repair my computer because I had received a 'corrupt profile' message in mid-January. I don't normally monitor the Event. – The first step is to identify from the 'Event ID 7, Disk has a bad block' event, which logical drive letter is assigned to the problematic hard disk. In order to accomplish this task: 1. From System event viewer, note the number after the word 'HardDisk' in the Event 7 warning message.