Viewing the Web Server Dashboard

The name of the WebLogic domain.

The location of the domain.

The location of the web server.

The version of the web server.

Enables you to set up metric alerts.

See Configuring Metric Alerts.

The operating system make and version.

The machine architecture.

The number of available processors on the machine.

The total amount of virtual memory (in GB) available on the machine.

The total amount of swap space (in GB) available on the machine.

The amount of memory (in MB) allocated for the heap when JVM started.

The maximum amount of memory (in MB) allocated for the heap.

Memory (in MB) currently allocated for the heap.

The amount of heap memory (in MB) currently in use by JVM.

The number of collections performed by the PS Mark Sweep collector.

The total time (in milliseconds) spent across all PS Mark Sweep collections.

The number of collection performed by the PS Scavenge collector.

The total time (in milliseconds) spent across all PS Scavenge collections.

In WebLogic, the thread pool is a subsystem that maintains its own health status indicator, so the status is sourced from WebLogic Mbeans.

The number of requests rejected when no more requests can be accepted because the maximum shared capacity of work managers is utilized.

The number of completed requests in the priority queue.

The maximum number of requests that can be accepted in the priority queue.

The number of requests that should be executed to satisfy the minimum threads requirement.

The number of requests with minimum threads constraint picked up out of order for immediate execution because their minimum threads requirement was not met.

The number of pending requests in the priority queue. This is the total of internal system requests and user requests.

The number of pending user requests in the priority queue. The priority queue contains requests from internal subsystems and users. This value is the count of all user requests.

The mean number of requests completed per second.

• Total - The total number of threads in the pool.

• Idle - The number of idle threads in the pool. This count does not include standby threads and stuck threads. The count indicates threads that are ready to pick up new work when it arrives.

• Standby - The number of threads in the standby pool. Threads that are not needed to handle the present work load are designated as standby and added to the standby pool. These threads are activated when more threads are needed.

• Hogging - The threads that are being held by a request currently. These threads will either be declared as stuck after the configured timeout or will return to the pool before the timeout.

• Stuck - The number of threads stuck in the thread pool.

The "steady state" of an open TCP connection. Data can be exchanged freely when both devices in the connection enter this state. This will continue until the connection is closed for one reason or another.

The device has received a close request from the other device. It must now wait for the application on the local device to acknowledge this request and generate a matching request.

The device has received a termination request from the other device and acknowledged it, and sent its own termination request and received an acknowledgment for it.

A device in this state is waiting for an acknowledgement for a close request it has sent, or is waiting for a connection termination request from the other device.

A device in this state has received an acknowledgement for its request to terminate the connection and is now waiting for a matching request to terminate from the other device.

Displays context-based attribute options.

Health Center supports two monitoring types:

• Counter

  You use counter monitoring type to watch a value of integer type. You can set a threshold value, so when the metric exceeds the threshold value, an alert is generated by the system. You can specify an offset value. When an observed value exceeds its threshold, the threshold value is incremented by the offset, or by a multiple of the offset sufficient to make the threshold greater than the new observed value.

  A counter monitor can operate in difference mode. In this mode, the value compared against the threshold is the difference between two successive observations of an attribute. Counter monitors are used to monitor data points like PSAPPSRV request counts.

• Gauge

  You use gauge monitoring type to observe attributes of numerical type. Each observed attribute has an associated high threshold and low threshold. When an observed attribute crosses the high threshold, an alert is generated if the Notify on High Threshold field is set to Yes. In subsequent instances, when the high threshold value is exceeded, further alerts will not be generated until the gauge value becomes less than or equal to the low threshold value. When an observed attribute crosses the low threshold, an alert is generated if the Notify on Low Threshold field is set to Yes. In subsequent instances, when the low threshold value is crossed, further alerts will not be generated the gauge value exceeds the high threshold value. Typically, either the Notify on High Threshold flag or the Notify on Low Threshold flag is set.

  A gauge monitor can operate in difference mode. In this mode, the value compared against the high and low thresholds is the difference between two successive observations of an attribute. Gauge monitors are used to monitor attributes like APPQ depth.

Gauge monitor is the default.

The observed attribute is monitored at intervals specified by the granularity period.

This field is available when you select the Gauge monitor type.

When you select the Gauge monitor type, you can set a high threshold value. When the high threshold value is exceeded, an alert is generated if you set the Notify on High Threshold field to Yes. Subsequently, if the high threshold value is exceeded again, an alert is not generated until the low threshold value is crossed.

This field is available when you select the Gauge monitor type.

When you select the Gauge monitor type, you can set a low threshold value. When the low threshold value is crossed, an alert is generated if you set the Notify on Low Threshold field to Yes. Subsequently, if the low threshold value is crossed again, an alert is not generated until the high threshold value is exceeded.

This field is available when you select the Gauge monitor type.

Set to Yes if you want an alert to be generated when the high threshold value is exceeded.

This field is available when you select the Gauge monitor type.

Set to Yes if you want an alert to be generated when the low threshold value is crossed.

This field is available when you select the Counter monitor type.

Set a threshold value. When the threshold value is exceeded, an alert is generated if you select Yes for the Notify field.

This field is available when you select the Counter monitor type.

If the counter can wrap around its maximum value, the modulus needs to be specified. The modulus is the value at which the counter is reset to zero.

This field is available when you select the Counter monitor type.

Specify an offset value. The offset value works in conjunction with the threshold value. When an observed value exceeds its threshold, the threshold value is incremented by the offset, or by a multiple of the offset sufficient to make the threshold greater than the new observed value.

This field is available when you select the Counter monitor type.

Set to Yes if you want an alert to be generated when the threshold value is exceeded.