Monitoring steps
The following steps are used for monitoring the state and operating systems of the managed devices. If any of the conditions specified for monitoring passes its threshold an event is raised.
Advanced Installed Software Check
This step allows you to verify if a specific software is installed on a device, and if not, to assign it directly to a device group via which the respective software will be installed. The existence of the software may be verified via the execution status of an operational rule, the existence of the software in the software inventory and via the existence of an executable file.
Parameter | Description |
---|---|
Check for File | Check this box, if the agent is also to search for the software via its executable file. If checked you also need to fill in the following parameter. |
Check in Software Inventory | Defines if the agent is to check for the software in the generated software inventory. |
Check for Operational Rule | Check this box, if it is possible that the software in question has been installed via an operational rule. In this case you must also fill in the following field. The software is regarded as existing, if the operational rule specified below was assigned to the device and has the final status Executed . |
File Path | The complete or relative path to the file. If you enter the path as a relative path it is relative to the <InstallDir>/Master/config directory . The file path may use wildcard characters, such as the asterisks (*), for example, ../log/mtxagent* to search in all stored log files of the agent for a specific expression. |
Full Name Match | Check this option if the operation is only to be run if the software application and version number provide a complete match to the above listed parameters. |
Device Group to Assign | If the software could not be found on the target device via either of the above defined methods, the device may be directly assigned to a device group which is assigned to the operational rule installing the software. For this you need to enter the respective device group in the field below by clicking the Add button. Find the device group assigned to the operational rule and click the OK button. |
Operational Rule | If you checked the box above, enter the operational rule, that installs the software in question. To enter the rule, click the Add button. Find the operational rule that installs the software application in the window and click the OK button. |
Software Name | Enter into this field the name of the software for which the target device is to be checked, for example, Microsoft Word 2003 . |
Version | Enter the version number of the application if it is relevant. This parameter is optional. |
Check Version | Defines the operator to be used with the above listed version number:
|
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check Disk Space
This step raises an event if the free disk space is less than the given threshold.
Parameter | Description |
---|---|
Free Space (MB) | Defines the amount of disk space that is to remain free and available on the managed devices in MB. |
Target Partition | Defines the partition which is to be checked for the disk space. |
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check File Date
This step checks if file creation or modification date match the given parameters. Year, month and day parameters are mandatory.
Parameter | Description |
---|---|
Operator | Select the verification operator for the date provided in the following fields. |
Check Type | Select from this dropdown list if the creation ( Creation Date ) or the modification ( Modification Date ) date is to be verified. |
Day | The day of the month. |
File Name | The name and full directory path of the file. |
Hour | Check the box to not only verify the date but also the hour of the file. Enter the hour value in the field that becomes available now with its 24-hour value, for example, 13 for 1 pm. |
Minute | Check the box to not only verify the date but also the minutes of the file. Enter the minute value in the field that becomes available now. If no minute value is indicated with the hour value all files created between for example, 13:00 and 13:59 are verified as OK with the equal operator. |
Month | The month value in its two digit form, for example, 03 for march. |
Second | Check the box to not only verify the date but also the second of the file. Enter the second value in the field that becomes available now. |
Year (YYYY) | Enter the year value with its four digits, for example, 2009 . |
Check Installed RAM
This step checks the size of the physical RAM on the managed devices and raises an event if the required amount if RAM is not available.
Parameter | Description |
---|---|
Generate Event If Failed | Check this box if an event is to be sent if the step fails. |
RAM (MB) | Specifies the minimum size of the physical RAM to be installed on the managed devices in MB. |
Check Installed Software
This step checks if a certain software application is installed on a target device and if yes, which version of it. It is particularly useful for software distribution, for example, for executing upgrades to a specific application. If the application is not installed an event is generated.
Parameter | Description |
---|---|
Full Name Match | Check this option if the operation is only to be run if the software application and version number provide a complete match to the above listed parameters. |
Software Name | Enter the name of the software for which the target devices are to be checked, for example, Microsoft Word 2003 . |
Version | Enter the version number of the application if it is relevant. |
Version Equal to | Check this box, if you need to know if the installed version is equal to the one specified in the Version field above. |
Version higher than | Check this box, if you need to know if the installed version is higher than the one specified in the Version field above. |
Version lower than | Check this box, if you need to know if the installed version is lower than the one specified in the Version field above. |
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check Operating System Version
This step checks for the operating system installed on target machines. It is particularly useful for software distribution; for example, when an application is only to be installed on a certain type of operating system. If the name of the operating system and the revision number do not match, an event is generated.
Parameter | Description |
---|---|
Operating System | Enter the name of the operating system for which the target devices are to be checked, for example, Window 2000 Professional . |
System Revision | Enter the revision number of the operating system, for example, Service Pack 3 . |
Full Name Match | Check this option if the operation is only to be run if the operating system and revision number provide a complete match to the above listed parameters. |
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check Service Execution
This steps checks if the specified service is currently running. An event can be generated if the specified service is not running.
Parameter | Description |
---|---|
Service Name | Enter the name of the service as it is known by the respective system. |
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check URL Availability
This step checks if the specified URL is responding or not. If not, an alert can be sent and the step returns an error.
Parameter | Description |
---|---|
URL | Enter into this field the URL to verify in the format of http(s)://<server>/ or http(s)://<user>:<password>@<server>:<port>/<subdir>/<file>. |
Send an alert if not responding | Check this box to generate an alert if the specified URL cannot be reached. |
Alert Description | Enter into this field the descriptive text for the alert to be displayed. |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Check Windows Events
This step checks for a specified string in the Windows event log files. If an event matching the string is found, the step returns an error and an alert can be sent. The first time this step is executed, no alert is generated.
Parameter | Description |
---|---|
String | Enter the string to find in the Windows event log file(s). It may be entered as a regular expression using the * and ? characters. |
Match Case | Check this box if the string entered in the field above is to be case sensitive, that is, if the searched string is error , it finds error, Error and ERROR . |
Event ID | Defines if only events of a specific ID are to be monitored. In this case you need to enter the ID exactly as it is known in Windows. |
Event Log | The log file in which to check for the event. You can either search in all or in one of the event logs. |
Event Severity | The event severity to verify. |
Send Alert if Found | Check this box to activate the sending of an alert if an event is found since the last check that matches all the criteria defined below. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
IP Address Verification
This step verifies if the IP address of a host has changed. The first time this step is run, no comparison can be effected, as the IP address is not yet referenced. During this execution, the reference address will be entered into the respective configuration file for further verifications.
No parameters need to be defined for this step.
Low Disk Space
This step creates an event if the disk space is less than the given threshold.
Parameter | Description |
---|---|
Insufficient Disk Space | Check this box if events are to be included in the mail that indicate that there is insufficient disk space available on a device. |
Drive | Defines the drive which is to be checked for its remaining available disk space. It is specified through its letter. |
Threshold (%) | Defines the threshold as a percentage value of 100%. Once the available disk space falls below this percentage, an event is raised. |
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
New Event Monitoring
This step sends an email to specific recipients with a list of newly generated events of a specific type that were registered since the last verification.
Parameter | Description |
---|---|
A monitored Windows event occurred | Check this box if generated Windows events are to be included in the mail. |
From | Enter the email address of the sender. This does not have to be a personal email, this may be any address which exists in your systems, such as support@starfleet.com . Also the email address does not have to be defined for an administrator account within the Console. |
Insufficient Disk Space | Check this box if events are to be included in the mail that indicate that there is insufficient disk space available on a device. |
Message Text | Specify the introductory text of the mail body. |
Port Number | Enter into this field the port number of the mail server, as defined in the Mail tab in the System Variables of the Global Settings . |
Server Name | Enter into this field the name of the mail server, as defined in the Mail tab in the System Variables of the Global Settings . The name may either be entered as the full or short network name such as mail or mail.enterprise.starfleet.com or as its IP address in dotted notation, for example, 213.2.146.1 or 2001:db8:85a3::8a2e:370:7334 . |
Subject | Contains the subject line of the mail. |
A monitored performance counter passed its threshold | Check this box if events are to be included in the mail, which were generated when the threshold of a monitored performance counter was exceeded. |
Memory Size | Check this box if events regarding changed memory size are to be included in the mail. |
To | Enter the email address of the recipient. This does not have to be a personal email, this may be any address which exists in your systems, such as support@starfleet.com . Also the email address does not have to be defined for an administrator account within the Console. You may specify more than one target address by separating them with a comma (,). |
Total Memory Changed
This step generates an event if the RAM of a device has changed.
Parameter | Description |
---|---|
Send an alert | Check this box to send an alert. |
Alert Description | Description of the alert to be sent. The values within the parenthesis are data that is replaced during execution. The description can contain environment variables (${}). |
Alert Severity | Select the severity to be assigned to the alert. |
Alert Sub-category | Enter the sub-category to which the alert is to be added. Be aware that this sub-category name may not have more that 64 characters. |
Comments
Log in or register to comment.