Other alert commands
OpenEdge Management supports the following alert commands:
Using the -firealert command
Use the following syntax to fire an alert:
OpenEdge Management also supports generation of application-specific alerts. In your application, you can send alerts to OpenEdge Management using the
-firealert
options shown in Figure 2–17.Figure 2–17:
![]()
-
firealert command optionsExample
You want to fire an alert regarding the CPU. Enter the following on the command line:
The alert fires, as shown in Figure 2–18.
Figure 2–18: Firing an alert
![]()
You can then look at the alert details for the CPU. Enter the following on the command line:
The alert details appear, as shown in Figure 2–19.
Figure 2–19:
![]()
-
firealert command exampleUsing the -alertlist command with group selection options
You can display an alert list by specifying one of the
-alertlist
command group selection options on the command line. Table 2–6 identifies and describes each group selection option.
Use the following syntax to display an alert list:
Note: You specify
-httpport
only if OpenEdge Management is running on a port other than the default of 9090.You can also use two additional options, the
-detail
and -verbose
options, presented in Table 2–7, with the group selection options highlighted in Table 2–6.Although the command line does not limit the number of options you can type into the command line, only the last group selection option identified on the command line is processed.
Figure 2–20 identifies a command line that generates a group selection based on the
-restype
option where the resource type is identified as system. Note that the resource name, listed in the Resource column, specifies the container name and associated resource name. Although this level of detail provides more information about a resource, it does not completely eliminate the possibility of confusion among resources with similar or identical names.Figure 2–20:
![]()
-
restype group selection option resultsUsing the alertlist command with additional options
Table 2–7 identifies and describes the additional options
Note: Unlike the group selection options highlighted in Table 2–6, the-detail
and-verbose
.-detail
and-verbose
options will be processed regardless of the position in which you enter them on the command line.
Table 2–7: Alert list command options to display additional details Option syntax Purpose How to use-detail
To format the display to provide a block of information about the alert, shown in the command line.The block of information matches what you see when you display the alert in the console. See Table 2–8 for a summary of the alert list details. Provide the-detail
option along with the option whose alert information you want to see listed.-verbose
To change the resource column of the displayed alerts from the generic format container:resource name to the fully qualified resource key.See Figure 2–21 to see an example of how to use the-verbose
option. Provide the-verbose
option along with the option whose alert information you want to see listed.
Figure 2–21 identifies a command line that generates a group selection based on the
-restype
option that also includes the-verbose
option. Note that the resource name, listed in the Resource column, specifies the fully qualified resource key. A fully qualified resource key is the most complete reference to a resource. The default format for a fully qualified resource key identifies each resource by its container name, the resource category to which the resource belongs, and the specific resource type and associated resource name.In Figure 2–21, the fully qualified resource key information identifies localhost as the container, the resource category as system, and the specific cpu resource name as CPU.
Figure 2–21:
![]()
-
restype group option with verbose option results Note: The container name localhost is logically the same as the container name for the system where OpenEdge Management is installed and running.Use the fully qualified resource key to:
Note: Due to the use of the colon in the fully qualified resource key between the container name and the resource category information, this format might need to be put in quotation marks on UNIX systems.
- Ensure that you are not confusing one resource name with another one that is either identical or similar. For example, it is possible to confuse a wsbroker1 on one container with another wsbroker1 on a different container. Referencing a resource by its explicit fully qualified resource key eliminates confusion as to what resource you are working with.
- Provide easy access to the complete resource information. You can cut and paste the fully qualified resource key into the command line when you use the
-resource
group option.Table 2–8 lists the details that can appear in the alert list.
Examples
Enter the following command to see a list of existing OpenEdge Management alerts from the command line:
Information about the current alerts appears, as shown in Figure 2–22.
Figure 2–22: -alertlist in the command line
![]()
In Figure 2–22 there are three alerts. One alert exists for a CPU resource named CPU, one alert for a file monitor resource named filemon1, and one alert for a log file resource named lfm1. As identified in the Resource column, all of these resources are on the localhost container. The alert ID numbers (ID) and severity (Severity) are also provided.
Enter the following command for a list of alerts for all OpenEdge server resources:
You see any alerts that exist for any OpenEdge server resources (openedge) listed. If there are no existing alerts, you receive the message shown in Figure 2–23.
Figure 2–23: -alertlist for openedge resource type
![]()
To see specific details about the alerts that exist for system resources, use either the
-detail
option or the-verbose
option.Enter the following command to examine the results of using the
-detail
option:
The details appear, as shown in Figure 2–24.
Figure 2–24: -alertlist command used with -detail option
![]()
Enter the following command to examine the results of using the
-verbose
option:
The details appear, as shown in Figure 2–25.
Figure 2–25: -alertlist command used with -verbose option
![]()
Copyright © 2008 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |