Posted by beakersoft | Posted in spiceworks | Posted on 19-02-2008
One of the new features in version 2.0 of spiceworks is the ability to monitor for certain events in machines event logs, or to check for certain machine software configs, such as 2 different anti-virus products installed. There are other products out that will do a similar job but this article is about what the new Spiceworks brings to the party.
All the options can be configured from the Settings tab in the main Spiceworks window, and we are interested in 3 of these sections:
- Monitors and Alerts
- Email Notifications
- Event Logging
Email and user Settings
Start in Email Notifications, from here you setup all your email information such as SMTP server info, what outgoing email address and POP3 server details(i cant really see why you would use one?)
Once you have entered the settings and hit save, it will test the settings and send a test email to the user you are logged in as.
Once the email settings are correct, you need to make sure that the relevant users are setup to receive them. From the Settings page go into user accounts, and click the Notify Me option against all the Spiceworks users you want to receive notification emails.
Once that is done, its time to create some events you want to monitor. This is done via Monitors and Alerts section in Settings. When you open the page there are already some example alerts setup, but just start by creating one of your own by hitting the Add button that the bottom of the list.
There are a 8 types you can choose from to monitor (antivirus, device, disk, software, service, hotfix, user account and printer supply level) , and each one of them has different conditions, and you can limit the type of device you want to monitor (it would be even better if you could just make it monitor a specific device, version 3 anyone?).
As an example will create a new monitor to let us know when the print spooler service is stopped on a server, as this might gives you a heads up to printing issues.
Assuming you have already hit Add, change the type to service, then type in spooler in the name text box, change the condition to is stopped, apply to All servers, tick the email option and then hit save to create your new monitor.
Next time a scan is done of your network, you should be notified of any server where the print spooler service has been stopped. Please not this is not a dynamic feature, and it will only tell you the next time a scan is carried out, and the condition is met.
When a device is scanned, Spiceworks will attempt to gather the event logs of it. This can be very useful in tracking trends across your servers if you are having (for instance) active directory replication, or security issues.
By default Spiceworks will gather all Error and warning logs, but ignores information ones. If you open up the Event logging section of settings you can tell it what other specific events you are interested in (like print jobs, this would be event id 10, see eventid.net for more event id’s).
Once you have added (or excluded) events, the next time a scan runs they should be picked up. To see events, on your inventory tab, click on a device you are interested in, then select the Events section at the bottom and you will be presented with the info, like below
The only thing that is missing is the ability to compare graphs across devices, that would be very handy. You could do this if Spiceworks opened up access into there data source, but thats not happened yet (and I don’t know if it will, thats my only major complaint)
So now you know how to setup the monitoring, if you dont already do something similar you can now get a head up about whats going on in your environment!