A description of status events for containers, including their message codes and frequencies.
The status events currently implemented for containers are:
|
Message Code |
Frequency |
Description |
|---|---|---|
|
ServiceStarted |
On event |
Event: service is started (value = 1) |
|
ServiceStopped |
On event |
Event: service is stopped (value = 1) |
|
ServiceKilled |
On event |
Event: service is killed via soap (value = 1) |
|
ContainerTotalMemory |
1/sec |
Total memory available to Sybase CEP Server in bytes) |
|
ContainerUsedMemory |
1/sec |
Total memory used by the Sybase CEP Server in bytes |
|
ContainerCPUUtilization |
1/sec |
Percentage of CPU utilized by the Sybase CEP Server process (1 = 100%) |
|
ContainerCPUTime |
1/sec |
CPU Time used by the Sybase CEP Server process since start in microseconds |
|
ModuleSentMessages |
1/sec |
Count of sent messages (value = count) |
|
ModuleReceivedMessages |
1/sec |
Count of received messages (value = count) |
|
ModulePendingMessages |
1/sec |
Count of pending messages (value = count) |
|
ModulePersistentDbPendingMessagesNum |
1/sec |
Count of persistent db pending messages (value = count) |
|
ModuleError |
On event |
Event: module generated an error message (value = error ModuleRunState xml or text) |
|
ModuleRunState |
On event |
Event: module is started (value = 1) or stopped (value = 0) |
Pending messages are messages that have been received but not yet processed.