You can increase server monitoring capacity by applying a new license key.
You have obtained your new license key.
1. |
◦ |
If the Organization component is not enabled on the appliance, log in to the K1000 Administrator Console, http://K1000_hostname/admin, then click Settings. |
◦ |
If the Organization component is enabled on the appliance, log in to the K1000 System Administration Console, http://K1000_hostname/system, or select System in the drop-down list in the top-right corner of the page, then click Settings. |
2. |
3. |
4. |
The full features are available to you after you sign back in to the appliance following the reboot.
The available monitoring profiles are listed on the Monitoring Profiles page
TIP: To display only the log monitoring profiles, in the top-right corner, click View By > Type > Log. To display the monitoring profiles for SNMP trap devices, click View By > Type > SNMP Trap. |
As an example, the default profile for creating alerts for Mac OS X devices indicates that /var/log/system.log is the log that the monitoring function scans, looking for text that would trigger an alert. The following table describes the default search text in the Include Text field and the associated alert levels.
You can add other alerts customized to your operational needs.
The default profiles cover the following supported operating systems:
• |
• |
• |
• |
• |
• |
• |
• |
For devices with Linux operating systems, there are several different log paths for MySQL and Apache logs, depending on the version of the OS. See Profile log paths for MySQL and Apache.
For Agentless devices that are monitored using the SNMP trap mechanism, you need to provide trap message formats and expressions to capture the specific trap elements. See Configure SNMP trap messages and alerting criteria.
In the Log Enablement Packages list page, Quest publishes a base set of Windows Reliability and Performance Monitor (PerfMon) templates and non-Windows open-source Perl scripts, so that users can extend their monitoring capability and identify system and application performance issues. These templates and scripts are available so that users do not have to create them from scratch. Monitoring on the K1000 works without these additional templates and scripts, but the profiles that are created from the templates and scripts are helpful if you want to do performance threshold monitoring.
In addition, for convenience, there is a default profile that can be used if you download optional Windows Reliability and Performance Monitor (PerfMon) templates to managed Windows Server 2003 devices. See Set up a Windows Server 2003 device with an ITNinja monitoring Log Enablement Package (LEP).
You can change, add, or remove alert criteria and log paths for any existing profile.
If you want to use an existing profile as a starting point for creating a profile, see Create a new profile using a default profile as a template.
To identify events that you want raised as alerts, use strings or regular expressions in Include Text to specify the appropriate message content. For instance, if you enter the string, Physical memory, an alert is raised for every message with that exact string.
To cover multiple possibilities, you can use a regular expression. For example, if you want alerts for any drive mount point that has drive errors, in the form, “Drive /dev/[any drive mount point] has drive errors”, you can use Drive /dev/[a-z]{1,} has drive errors in Include Text. Alerts are raised for any messages that contain "Drive /dev/" followed by any word of any length containing the characters a-z, followed by "has drive errors".
You can exclude specific events from being raised as alerts if you find them unnecessary or distracting. To filter the alerts you do not want to receive, you use Exclude Text to indicate the content that identifies an unwanted alert. You can use Exclude Text to filter whole categories of alerts, or use Exclude Text in conjunction with Include Text to refine a subset of an alert category. See Examples of Include Text and Exclude Text for monitoring profiles.
1. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
2. |
Select the check box for the existing profile that you want to edit, and select Choose Action > Edit to display the Profile Detail page. |
3. |
NOTE: If you are editing one of the default profiles, you cannot make any change to the Add Automatically To field. |
4. |
◦ |
Change Include Text. |
1. |
2. |
3. |
Click Save at the right of the row. |
◦ |
Optional: Change Exclude Text. |
1. |
2. |
3. |
Click Save at the right of the row. |
◦ |
Change alert Level. |
1. |
2. |
In the Level drop-down list, select the level from among the five choices: Critical, Error, Warning, Info, and Recovered. |
3. |
Click Save at the right of the row. |
1. |
2. |
Set the level, include text, exclude text (optional), and case sensitivity, and click Save at the right of the row. |
5. |
NOTE: You can return a default profile to factory settings for its operating system by using the Reset to Factory Settings button at the bottom of the page. |
You can configure SNMP trap messages and the alerting criteria using the Profiles page.
• |
• |
You can configure SNMP trap messages and the alerting criteria using the Profile Detail page.
You can include or exclude certain events from being detected, as needed.
1. |
a. |
Log in to the K1000 Administrator Console, http://K1000_hostname/admin. Or, if the Show organization menu in admin header option is enabled in the appliance General Settings, select an organization in the drop-down list in the top-right corner of the page next to the login information. |
b. |
◦ |
◦ |
◦ |
To duplicate an existing SNMP trap profile, select it in the list, and Choose Action > Duplicate and Edit . |
3. |
NOTE: If you are editing one of the default profiles, you cannot make any change to the Add Automatically To field. |
4. |
%Vd# |
|
%Vn# |
Variable binding name (where '#' is a number representing the element's position in the sequence). |
%Vo# |
Variable binding OID (where '#' is a number representing the element's position in the sequence). |
%Vt# |
Variable binding type (where '#' is a number representing the element's position in the sequence). |
%Vv# |
Variable binding value (where '#' is a number representing the element's position in the sequence). |
Shows all variable bindings (Name: Value, Name: Value, Name: Value). If a Name is missing (due to a missing MIB file), the OID is displayed instead. |
◦ |
◦ |
TRAP_OID = “.1.3.6.1.4.1.8072.2.3.2.1”: An alert is generated when the trap OID contains ".1.3.6.1.4.1.8072.2.3.2.1". |
◦ |
TRAP_NAME = "acctngFileFull" AND VARBIND = "acctngFileName|ABC": An alert is generated when the trap name contains "acctngFileFull" and if one of the trap's variable bindings is "acctngFileName" with a value of "ABC". |
7. |
NOTE: You can return a default profile to factory settings for its operating system by using the Reset to Factory Settings button at the bottom of the page. |
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy