Monitoring System Performance
The Monitor Tree is part of the Monitoring section in the navigation bar. The Monitor Tree allows you to get a quick overview over systems connected to Redwood Server and their current status. You can get a graphical representation of the status of a subset of monitors by creating dashboard dials for built-in leaf nodes of process servers, queues, and database monitor leaf nodes. By default, only the database tables are monitored.
The Monitor Tree displays an hierarchical overview of all monitors, and their current status, expressed by a severity value. The severity is propagated upwards through the hierarchy so a parent monitor shows the highest severity of its children.
The Monitor Tree consists of two panes:
- The monitor pane displays a hierarchy of all monitors.
- The detail pane displays run-time data of the currently selected monitor.
Three types of monitors are shown:
- Nodes - A monitor that can contain sub-monitors.
- Checks - A monitor that defines conditions upon which events are to be raised.
- Links - A monitor that links to another monitor (node or check).
The following
System.Database- contains all the Redwood Server-specific database tables with default Monitor Checks that check the size of the individual tables, System_MonitorTables tracks tables that have exceeded their recommended sizes, stored in process fileTableGrowth.csv.System.Queue- contains all queues created in Redwood ServerSystem.ProcessServer- contains all process servers created in Redwood Server, this includes platform agent and module-related process server like SAP or JDBC process serversSystem.cluster- contains nodes describing the current application server setup; regardless of whether there are more than one nodes, the name will becluster
Severity
The severity gives you information about the extent of the issue and is indicated by a number ranging from 0 to 100. A severity of less than 25 will not result in a green severity, a severity above 50 will be yellow and above 75 it will be red. This means that severities comprised of -1 to 24 are not taken into account, merely displayed.
The primary function of the Monitor Tree is to check no monitors have a severity above 24.
Events
You can configure monitor nodes to trigger events, when certain severities are reached. These events can then schedule processes to alert operators or even restart applications. The Rising flag is used to only trigger an event when a monitor is getting worse, that is, the severity is rising. If you leave the check-box unchecked, configure an event to be raised as soon as the monitor reaches a severity of 50 and the monitor reaches 75, the event will be raised again when the severity falls below 50.
Database Monitors
You monitor the database tables used by Redwood Server using the Database node in the Monitor Tree. Update the Database monitoring tree by submitting System_MonitorTables.
Some tables will grow quickly depending on your use of Redwood Server. SAP jobs (SAP_AbapRun) usually have many parameters and this causes the JobParameter table to grow quickly, one row for each job/parameter combination. On production systems with many processes and long keep strategies, you may increase the CheckRows monitor condition expression, the default being =NumberOfRows > 5000000.
Job History
History is usually kept for 365 days, you change the default by specifying the following registry entry and submitting the System_Aggregate_History process definition:
/configuration/history/jobhistory
This affects HistoryJob and HistoryJobParameter tables.
Available Monitors:
NumberOfRows- the number of rows the table has in the databaseTableSize- an estimate of the table size, based on the number of rows the table hasTimeDelta- time since the previous time the monitor was updatedTimeDeltaMillis- same as TimeDelta, in millisecondsRowsDelta- number of rows added/removed since last update
Enabling Process Server and Queue Monitoring
Process server and queue monitoring is disabled by default for performance reasons. You set the /configuration/jcs/monitoring/enabled configuration entry to true to enable monitoring and for each process server you wish to monitor, you set the MonitorInterval process server parameters.
Process Server Monitor Checks
You specify checks on platform agent process servers to monitor services, event logs (Windows) or processes and log files (UNIX, HP OpenVMS) as well as sockets (all platform agent platforms). These can the be monitored with Events or Monitor Alert Sources to send operator messages/emails when a monitor has reached a severity; the latter functionality requires the Active Monitoring Module.
note
The Active Monitoring Module requires the Module.Alerting license key
SAP System Monitors (Deprecated)
If you have connected Redwood Server to SAP Systems, then the default monitor-tree contains monitors for the SAP Application Servers. To import the bare monitor tree from transaction RZ20, you need to fill in the XAL tab on the SAP System object and import the monitors. To import individual CCMS monitors, that you access via transaction RZ20 in SAPGui, you need to submit the SAP_ImportCcmsMonitors process definition.
Context-Menu
Monitor Nodes support the following context-menu actions:
| Action | Description |
|---|---|
| Show permalinks | Show links that can be used from third party applications to link to the object |
| Add to navigation bar | Add the current object to the navigation bar |
| Edit Security | Edit the security of the monitor node |
| New Monitor Alert Source | Create a new monitor alert source for this monitor node |
| Delete | Delete this monitor node |
| Edit | Edit this monitor node |
| Export > Export | Export this monitor node into a CAR file |
| Export > Export with related objects | Export this monitor node into a CAR file including referenced objects |
| Promote > Promote to system | Promote the object to a remote system |
| Promote > Edit further then promote | Edit the export rule set prior to promoting |
| Promote | Promote the monitor node to another Redwood Server instance |
| Expand All | Expand all monitor nodes below the current node |
Monitor leaf nodes support the following actions:
| Action | Description |
|---|---|
| Edit | Edit this monitor [leaf] node |
| Edit Security | Edit the grants to the monitor [leaf] node |
| New Monitor Alert Source | Create a monitor alert source for this monitor node. |
| Export > Export | Export this monitor leaf node into a CAR file |
| Export > Export with related objects | Export this monitor leaf node into a CAR file including referenced objects |
| Promote > Promote to system | Promote the object to a remote system |
| Promote > Edit further then promote | Edit the export rule set prior to promoting |
| Promote | Promote the monitor leaf node to another Redwood Server instance |
| Show permalinks | Show links that can be used from third party applications to link to the object |
Procedure
To monitor components perform the following tasks:
- Navigate to "Monitoring > Monitors" to get an overview of all monitors.
- Choose the Refresh button to update the monitor.
- Choose the [+] icon to expand the monitor nodes and links and show the child monitors. Choose the [-] icon to collapse and hide the child monitors.
- Choose a monitor to show the monitor details in the lower detail pane.
Values
| Field | Description |
|---|---|
| Parent Monitor Node | The parent monitor node this monitor belongs to. |
| Name | The unique name of this monitor. |
| Description | The description of the monitor. |
| Documentation | A comment about the monitor. |
| Actual Severity (Node and Check monitors only) | The current severity of the monitor, or -1 if it has not been set before. |
| Remote ID (Node and Check monitors only) | Unique identification of the monitor in the remote system. |
| Linked Monitor (Link monitors only) | The linked monitor (Node or Check monitors). |
| Monitor Events (Node and Check monitors only) | Event to be raised when a monitor reaches a particular severity. |
| Monitor Conditions (Check monitors only) | A monitor condition defines when a problem is raised. |
| Monitor Values (Check monitors only) | A monitor value is a numeric, string or timestamp value used to define monitor conditions. |
| Creation Time | The creation time of this monitor. |
| Last Modification Time | The last modification time of this monitor. |
See Also
- Monitoring Servers with Platform Process Servers
- Monitoring External Systems with Platform Agents
- Creating a Monitoring Platform Agent
- Creating a Monitor Check
- Creating Custom Monitor Checks
- Documenting Objects using the Documentation Tab
MonitorNode