Chatee ahora con Soporte
Chat con el soporte

Foglight for IBM WebSphere MQ 5.5.5.9 - User and Reference Guide

Using Foglight for IBM WebSphere MQ Server Reference
Views Rules Data

Alarms Tab View

How to Get Here
From the Queue Managers Group View, drill down on a queue manager and click the Alarms tab.
Purpose
The alarm information allows for quick diagnostics.
 
Description of the View
Data displayed
•
Long Name. Contains the name and type of the object instance against which the alarms is raised. Hovering over this field shows a dwell with additional information about this object instance.
 
•
Health. Indicates the object health, based one the highest severity alarm. Hovering over this field shows a dwell listing the most recent alarms for this queue.
 
•
Alarms. Indicates the numbers of fatal, critical, and warning alarms for each object instance. Hovering over a severity column opens a dwell containing a list of the alarms of that severity, raised against this queue manager. For more information about alarms, see the Foglight User Guide.
 
•
Health History. Indicates the object health, based on the highest severity alarm. Hovering over this field opens a dwell containing information about the most recent alarm for this object instance.
Where to go next
•
Drill down on any Long Name to opens a dwell with detailed views about the selected object instance, links to those views, and any additional information about the selected object instance. For example, clicking an MQQueueManager object opens a dwell containing a link that drills down to the Queues Tab View, the event status for the queue manager, and a graph view showing the depths of the DLQ and connection count for the selected queue manager.
 
•
Drill down on any Health icon to open a dwell listing the alarm sources for the selected object instance, and links to views that show all alarm sources, the alarms raised against that object, and all outstanding alarms.
 
•
Drill down on any Alarms count to open the Outstanding Alarms dialog box, containing a list of outstanding alarms associated with this queue manager.

Channel Details View

How to Get Here
On the MQ Queue Manager dashboard, click the Channels tab, then select a channel entry in the table.
Alternatively, on the MQ Cluster dashboard, click the MQ Server Application tab, then click the Application Channels tab and select a channel.
Purpose
This view shows the message count for the selected queue over time, along with the data flow to and from the transmission channel. The flow fields in this view provide color-coded real-time health status.
 
Description of the View
Data displayed
•
Count Per Second. Contains the number of messages per second, sent and received on the WebSphere MQ client link over the connection to a specific client.
 
•
Buffers Received. Contains the number of buffers received on the channel per second.
 
•
Buffers Sent. Contains the number of buffers sent on the channel per second.
 
•
Bytes Received. Contains the number of bytes received on the channel per second.
 
•
Bytes Sent. Contains the number of bytes sent on the channel per second.
 
NOTE: For channels with more than one instance, these metrics are summed in this view.

Channels Tab View

How to Get Here
On the MQ Queue Manager dashboard, click the Channels tab.
Purpose
This tab lists the channels that the selected queue manager uses for communication with other queue managers. A channel can have one of the following states: Initializing, Binding, Starting, Running, Stopping, Stopped, Retrying, or Requesting.
By default, the Channels tab lists all channels. To list only the active channels, click Active Channels. To return to the default list, click All Channels.
 
Description of the View
Data displayed
Channels
 
•
Health. The channel health, based on the highest severity alarm. Hover over the icon to open a dwell listing the most recent alarms for this queue.
 
•
Name. The channel name.
 
•
Type. The channel type. A channel can be of one of the following types:
Cluster-receiver. Receives information about the cluster.
Cluster-sender. Sends cluster information to a queue manager.
Receiver. Places the messages into the destination queue.
Requester. Starts the channel.
Sender. Starts the channel so that it can send messages to the other system. The sender requests the receiver at the other end of the channel to start, and sends messages from its transmission queue to the receiver.
Server. Sends messages to the requester from the transmission queue defined in its channel definition.
Server-connection. A bidirectional channel that connects an MQ client to a server, on the server-side.
 
•
Status. The status of the channel associated with this queue. It can have one of the following values:
Binding. Channel is performing channel negotiation and is not yet ready to transfer messages.
Initializing. The channel initiator is attempting to start a channel.
Indoubt (Yes). The sending MCA is waiting for a confirmation that a batch of messages that it has sent has been successfully received.
Paused. The channel is paused.
Starting. A request has been made to start the channel but the channel has not yet begun processing. A channel is in this state if it is waiting to become active.
Stopped. The channel is stopped manually.
Stopping. Channel is stopping or a close request has been received.
Requesting. A local requester channel is requesting services from a remote message channel agent (MCA).
Retrying. A previous attempt to establish a connection has failed. The connection is attempted after the specified time interval.
Running. The channel is either transferring messages at this moment, or is waiting for messages to arrive on the transmission queue so that they can be transferred.
Unavailable. No status is available for this channel. The channel is not operating.
 
Messages
 
•
Current. The number of messages on the channel in the current batch.
 
•
Count/Sec.The rate (count per second) of messages travelling on this channel during the sample period.
 
•
Session Total. The number of messages on the channel during the channel active period.
 
NOTE: For channels with more than one instance, these metrics are summed in this view.
 
Sent
 
•
Buffers. The number of buffers sent on the channel.
 
•
Bytes. The number of bytes sent on the channel.
 
NOTE: For channels with more than one instance, these metrics are summed in this view.
 
Received
 
•
Buffers. The number of buffers received on the channel.
 
•
Bytes. The number of bytes received on the channel.
 
NOTE: For channels with more than one instance, these metrics are summed in this view.
 
•
Clusters Name. The names of any clusters that this channel is a part of.

Detail Properties View

How to Get Here
You can find this view in the bottom portion of the MQ Group Browser. To navigate to this dashboard, from the navigation panel, under Homes, click MQ Queue Manager. In the navigation tree that appears at the bottom of the navigation panel, select an MQGroup.
Purpose
This composite view contains additional details about the selected queue manager.
This view contains the following embedded views:
•
Events Status View
•
Queue Manager More Info View
•
Dead Letter Queue Depth View
•
Connection Count View
 
 
Events Status View
Description
This view indicates which important event types are enabled from the monitored queue manager. For optimal monitoring, all of these event types should be enabled.
Data displayed
•
Performance. The availability of performance events (Enabled or Disabled). Performance events are generated when the queue manager detects a change that is likely to impact the performance of an application. For example, when a queue depth limit is reached, the queue manager generates a performance event message.
 
•
Start/Stop. The availability of start and stop events (Enabled or Disabled). Start and stop events are generated when a queue manager is started or is requested to stop.
 
•
Inhibit. The availability of inhibit type of events (Enabled or Disabled). These types of events are generated when a read or write operation has been attempted against a queue that is inhibited for those types of operations.
 
•
Local. The availability of local events (Enabled or Disabled). Local events are generated when a local queue or object is not accessible.
 
•
Authority. The availability of authority events (Enabled or Disabled). Authority events are generated to report an authorization related to queue-related activities, for example, when an application attempts to open a queue.
 
•
Remote. The availability of remote events (Enabled or Disabled). Remote events are generated when an application or the queue manager cannot access a remote queue on another queue manager.
 
•
Auto-Definition. The availability of auto-definition events (Enabled or Disabled). Auto-definition events are generated when a channel is automatically generated for a queue manager.
 
 
 
 
 
 
 
Queue Manager More Info View
Description
This view lists the names of the command and dead-letter queues (DLQ) associated with the selected queue manager.
Data displayed
•
Command Queue. The name of the system command queue. This queue receives system commands that are executed by the queue manager.
 
•
Dead Letter Queue. The name of the dead-letter queue. This queue contains undeliverable messages.
 
Dead Letter Queue Depth View
Description
This graph shows the depth of the dead-letter queue (DLQ). This queue contains undeliverable messages.
Data displayed
Dead Letter Queue Depth. The number of messages in the DLQ, plotted over time.
 
Connection Count View
Description
This graph shows the number of connections for the queue manager.
Data displayed
Connection Count. The number of connections to the queue manager, plotted over time.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación