Chatee ahora con Soporte
Chat con el soporte

Foglight for Siebel 5.2.1 - User and Reference Guide

Introducing Foglight for Siebel Systems Foglight for Siebel Systems Summary Dashboard About the Foglight SiebelServer Agent Foglight for Siebel Systems Reference

Sieb_Srvr_Proc_Memory rule

Purpose
The Sieb_Srvr_Proc_Memory (process memory) rule determines when an individual process associated with the Siebel Server is consuming too many of the available memory resources on the monitored host.
Scope
SiebelServer_SiebelProcessInfo
Rule definition
Table 38. Sieb_Srvr_Proc_Memory rule definition
Condition
State
Action
SiebelServer.SiebelProcessInfo.PercentMemory > #WORLD::PercentMemoryWarning#
Warning
Log message
SiebelServer.SiebelProcessInfo.PercentMemory > #WORLD::PercentMemoryCritical#
Critical
Log message, email Siebel administrator
Interpreting the rule
The Sieb_Srvr_Proc_Memory alert indicates excessively high memory utilization by an individual Siebel operating system process. This can cause the Siebel server to crash or limit the number of users who can be serviced by the object managers assigned to the Siebel server.
If a Siebel object manager component is consuming a large amount of memory resources and the number of running tasks is high, the Siebel administrator should investigate whether the object manager’s Max Tasks, Max MTServers, and RecycleFactor parameters are correctly set. Siebel Support Web provides many resources detailing how to optimally set these parameters. Another option is to include distributing the object manager across multiple Siebel servers. This is accomplished by assigning the Siebel component to other Siebel servers and using Resonate to perform load balancing between the servers.
If the Siebel component that is consuming a large amount of the memory resources is a batch or background component, such as the Assignment Manager, the Siebel administrator could consider reassigning this Siebel component to a Siebel server with more available resources. You can do this using the Siebel Server Manager.
If the Siebel component is a member of the Siebel Remote component group, the Siebel administrator should investigate whether Siebel Remote can be tuned on this Siebel server or if additional Siebel servers should be dedicated to the Siebel Remote component group.
* 
NOTE: #WORLD::PercentMemoryWarning# is a Foglight_Registry entry with a default value of 30.00 and #WORLD::PercentMemoryCritical# has a default value of 60.00. Use the Foglight Registry to change thresholds for rules by modifying registry entries.
Views that render data that this rule is based on:
•
Sieb_Proc_Utilization graph view .

Sieb_Task_Status rule

Purpose
The Sieb_Task_Status rule determines if a Siebel Component completes with a condition other than a normal completion such as Exited with Error or Killed.
Scope
SiebelServer_SiebelTasks
Rule definition
Table 39. Sieb_Task_Status rule definition
Condition
State
Action
SiebelServer.SiebelTasks.TaskStatus != "Running"
Critical
Log message, email Siebel administrator
Interpreting the rule
A server component task may be in one of four fundamental states: Running, Paused, Stopping, or Completed. The Siebel task state definitions are:
•
Running—indicates that the task is executing normally. While the task is running, it periodically updates its task status, and sends a component-generated message that indicates the task progress or phase of operation.
•
Background mode component tasks run until stopped manually, or until the Siebel Server or the component shuts down.
•
Batch mode component tasks run to completion when their assigned unit of work is done.
•
Interactive mode component tasks run until the client signs off from the connection or until the task, component, or server is shut down. The Siebel administrator may explicitly pause or stop any currently running component task.
•
Paused—indicates that the task is temporarily placed in a suspended state. A paused task does not exclusively hold any shared system resources (such as file locks or database locks), or expend any processor or I/O cycles. You may choose to pause a running task to temporarily free up the system in order to process other critical tasks without having to restart the entire task. You may then resume or stop the paused task.
•
Stopping—indicates that the component task is instructed to stop, or the component or server is being shut down. Occasionally, the shutdown process may take a while, in which case you may issue another Stop command, and the shutdown is forced (this state may appear as Forcing Shutdown). After a task is instructed to stop, it may not be resumed.
•
Completed—indicates that the component process is no longer running. After a process is completed, it may not be restarted, though you may start a new task for the same component. Several variations exist for the Completed state, depending on the manner in which the task finished processing:
•
Completed indicates that the task ran to completion and exited normally (batch mode and interactive mode tasks only).
•
Exited with Error indicates that the task encountered an error during its processing, such as bad input values or database errors. In this case, the Task Status field displays the error identifier for the error that occurred.
•
Killed indicates that the process was not able to shut down cleanly, and you forced the task to shut down.
A Sieb_Task_Status alert is generated when a Siebel task status is not equal to ‘Running’. When the Siebel administrator receives a Sieb_Task_Status alert stating a Siebel task has ‘Exited with Error’, the Siebel administrator should check the corresponding task log to determine the cause.
The SiebelServer Agent can monitor each Siebel component task log for errors that lead a Siebel task to exit. This enables the Siebel administrator to be alerted of the exact error that occurred. Use the 'Component Logs Message Trap List’ agent property to enable this functionality for each Siebel component.
Views that render data that this rule is based on:
•
Sieb_Task_Detail Table view .

SiebelServer Agent data tables

Foglight for Siebel collects data and stores it in specific tables. In this guide, the description of the tables are organized by agent.
The SiebelServer Agent tables collect and store error messages about the agent and the Siebel Server, as well as basic server level information, such as the start time and current status of a server.
The SiebelServer Agent contains the following tables. Select the table name to view the field definitions.
•
Siebel Component Groups data table
•
Siebel Component Statistics data table
•
Siebel Components data table
•
Siebel Log Message data table
•
Siebel Process Information data table
•
Siebel Server Health data table
•
Siebel Server Statistics data table
•
Siebel Server Summary data table
•
Siebel Tasks data table

Siebel Component Groups data table

The fields in this table are as follows:
Table 40. Table description for Siebel Component Groups
Field
Description
ComponentCount
The number of Siebel components included in the component group.
ComponentGroup
The full name of the component group.
ComponentGroupAlias
A short name or alias for the component group.
ComponentGroupAvailability
A numeric value (100 = online or running and zero = all other values) that represents the component group run state.
ComponentRunState
The current run state for the Siebel component group (Online, Offline, Shutdown, etc.).
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación