Kbase P133770: What does Fathom/OE Management monitor out of the box?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
7/30/2008 |
|
Status: Unverified
GOAL:
What does Fathom/OE Management monitor out of the box?
FACT(s) (Environment):
UNIX
Windows
OpenEdge Management 3.1x
FIX:
Assuming you instructed OE Man to monitor the system and OpenEdge resources, this what you can expect out of the box.
System Resources:
CPU - Each CPU is discovered and has an 80% threshold set. It polls every five minutes. An Alert is thrown if two successive polls read 80+% cpu utilizatation. Default action is taken, which send an alert to the default email receiptient
Memory - Memory is discovered and a threshold of 100% Physical and 80% Virtual memory usage is applied. It polls every five minutes. An alert is thrown when two successive polls exceed the defined threshold. Default action is taken, which send an alert to the default email receiptient
File Systems - Logical file systems are discovered. The usage threshold is set for 90%. It will throw an alert and perform the default action (send alert to default email).
Disks - Not added by default. Must be added manually
OpenEdge Resources:
All databases managed by the adminserver are automatically discovered. Those databases not managed by the AdminServer can be added as a scripted database or migrated to the control of the local AdminServer.
Databases, by default are polled every five minutes and are looking for abnormal database shutdown or dbagent terminated. Each database has a log file monitor attached to it looking for various entries in the log file that might indicate a problem. The Default "DB_LogFileMonitor_RuleSet" is attached to the log file monitor looking for the following
BI_file_threshold_percentage
BI_file_threshold_reached
BI_processing_stalled
DB_Shutdown
System_Error
Any violation results in an alert and an email to the default email receiptient
Ubrokers (appserver, nameserver, and webspeed) are also discovered and polled every five minutes for an abnormal termination. They also have server and broker log file monitors.
Appserver Broker Log file monitor
AS_Broker_LogFileMonitor_RuleSet
Broker_Error_Msg_Received
Cannot_Start_Server
Connection_Refused
Disconnecting_Client
Error_Loading_Prop_File
Fatal_Error
Invalid_Action_For_State
Invalid_Admin_Response
Invalid_State
IOException_Client_Response
IOException_Message_From_Server
MsgFormatException
No_Servers_Available
Server_Exec_Error
ServerIPCException
Unimplemented_State
NameServer_Consistency_Error
NameServer_IOException
NameServer_keepAlive_stopped
NameServer_NOT_started
Appserver Server Log files are monitored for the following errors:
AS_Server_LogFileMonitor_RuleSet --- ---
Fatal_Memory_Error
Fatal_Transport_Failure
Insufficient_Stack_Space
Network_Protocol_Mismatch
Transport_Resources_Unavailable
Unexpected_Transport_Error
Unknown_Transport_Error P>
Webspeed Broker Log files are monitored for the following errors:
WS_Broker_LogFileMonitor_RuleSet
NameServer_Consistency_Error
NameServer_IOException
NameServer_keepAlive_stopped
NameServer_NOT_started
Broker_Error_Msg_Received
Cannot_Start_Server
Connection_Refused
Disconnecting_Client
Error_Loading_Prop_File
Fatal_Error
Invalid_Action_For_State
Invalid_Admin_Response
Invalid_State Not Checked
IOException_Client_Response
IOException_Message_From_Server
MsgFormatException
No_Servers_Available
Server_Exec_Error
ServerIPCException
Unimplemented_State
Webspeed Server log files are monitored for the following errors:
WS_Server_LogFileMonitor_RuleSet --- ---
Fatal_Memory_Error
Fatal_Transport_Failure
Insufficient_Stack_Space
Transport_Resources_Unavailable
Unexpected_Transport_Error
Unknown_Transport_Error
NameServer log file is monitored for the following errors:
NS_LogFileMonitor_RuleSet --- ---
Cannot_Return_Message
Erroneous_UUID
Exceptions_Causing_NS_Shutdown
Invalid_Message_Code
Listening_Error
Message_Error
Socket_IO_Exception
Unhandled_Exception
Any single violation results in an alert and an email to the default email receiptient. there are other rulesets that can be added to the OE resources and log file monitors. You can view those under Library.
Files and Log File monitors (seperate from standard OE log files) are added manually. they can be used to monitor the exists, size, growth etc and for various text strings.
Network monitors are also added manually except one. There is a TCP monitor automatically in place monitoring port 25 for the smtp server. It throws an alert and an email if two successive failures are recorded..