|
Huntland Services Ltd Tel: +44 (0)1392-490518
|
Alert Statistics Portfolio |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Back | Download The Scripts | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
IntroductionOf all the Alerts being generated in my Mom environment, what proportion are coming from my Exchange box? Which is the Processing Rule that seems to be responsible for generating the most alerts? For my IIS box, how long is the delay before an alert condition is detected and that alert being written into the database and therefore being visible to the Admin Console? The following are a collection of scripts that provide information variously on the sources of Alerts in your organisation. The output will be displayed on screen and also written to a TXT file or CSV file suitable for use with Excel. The result include latency details indicating how many seconds it took (Max, Min and Average) from the condition first being detected to the point where it was committed to the Database. This reflects how well Mom is keeping up. If the Agent has been in constant contact with the CAM then these figures will be low, but if contact has been interrupted for any reason the latency figures will rise dramatically. Because of the size of the output these scripts should only be run from a Command Prompt using CSCRIPT. You will need to specify the following paramaters:
In all cases your account must have access to the MOM SQL Server and at least read access to the Onepoint database. Windows Security ('Integrated') is assumed. If your database is many gigabytes in size then you can expect a delay while the query runs. Each script has two commented timeout values controlling the maximum connection time and the maximum time to run a command. By default these are set low and may have to be increased for larger databases.
1. AlertCulprit.vbsPurpose: To list which Mom culprits have been generating alerts per machine Syntax: cscript alertCulprit .vbs myMomSqlServer C:\temp\alertCulprit.txt myServer Result:
2. AlertCulprit_Summary.vbsPurpose: To list which Mom culprits have been generating alerts in all cases Syntax: cscript alertCulprit_Summary.vbs myMomSqlServer C:\temp\alertCulprit.txt Result:
3. AlertProcessingRule.vbsPurpose: To list which Mom processing rules have been generating alerts per machine Syntax: cscript alertProcessingRule.vbs myMomSqlServer C:\temp\alertProcessingRule.txt myServer Result:
4. AlertProcessingRule_Summary.vbsPurpose: To list which Mom processing rules have been generating alerts in all cases Syntax: cscript alertProcessingRule_Summary.vbs myMomSqlServer C:\temp\alertPR_Summary.txt Result:
5. AlertProvider.vbsPurpose: To list which Mom providers have been generating alerts per machine Syntax: cscript alertProvider.vbs myMomSqlServer C:\temp\alertProvider.txt myServer Result:
6. AlertProvider_Summary.vbsPurpose: To list which Mom providers have been generating alerts in all cases Syntax: cscript alertProvider_Summary.vbs myMomSqlServer C:\temp\alertProv_Summary.txt Result:
7. AlertSummary.vbsPurpose: To summarise all Mom Alerts Syntax: cscript alertSummary.vbs myMomSqlServer C:\temp\alerts.txt Result:
Please accept these scripts as is. Any feedback will be gratefully received at Debug@Huntland.co.uk |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||