Converse agora com nosso suporte
Chat com o suporte

Foglight for IBM WebSphere MQ 5.5.5.9 - User and Reference Guide

Using Foglight for IBM WebSphere MQ Server Reference
Views Rules Data

Queue Status View

How to Get Here
From the Queue Managers Group View, drill down on a queue manager and click either the Queues or Channels tab. Select an entry in the table.
Purpose
This view shows the data flow to and from the selected queue, and its depth. The appearance of this view depends on the selected queue type. For example, selecting a concrete queue shows the information about that queue. Selecting a reference queue shows the data about the associated transmission queue. The flow fields and disk object in this view display color-coded real-time behavior, indicating the severity.
 
Description of the View
Data displayed
•
Oldest Message Age. The age of the oldest message in the queue, in seconds.
 
•
Open Output. The number of open output handles. This indicates the number of applications that are currently connected to the queue and placing messages onto the queue.
 
•
Enqueue Rate. The rate of messages placed in the queue, expressed as count per second, since the queue statistics were last reset. This value reflects the frequency of the resetting of queue statistics.
 
•
Queue Depth. Shows the number of messages in the queue.
 
•
Open Input. Shows the number of open input handles. This indicates the number of applications that are currently connected to the queue and removing messages from the queue.
 
•
Dequeue Rate. Shows the rate of messages removed from the queue, expressed as count per second, since the queue statistics were last reset. This value reflects the frequency of the resetting of queue statistics.

Queues Tab View

How to Get Here
From the Queue Managers Group View, drill down on a queue manager and click the Queues tab.
Purpose
This tab lists the queues associated with the selected queue manager, filtered by Clustered, Non-Clustered, or All Queues.
Queues are managed by queue managers. Each queue manager can have one or more queues, and each queue can be managed by one queue manager. Concrete queues contain messages, while reference queues contain references to other queues. There are different types of queues. For example:
•
Local queues are concrete queues. They contain messages and are managed by the local queue manager.
•
Transmission queues are also concrete queues. They store messages that are to be transmitted to a remote queue manager.
•
Reference queues do not store message, but rather forward them to another pre-defined queue.
•
Remote queues are reference queues. They reference queues managed by a remote queue manager.
Applications can retrieve messages only from their local queues, and write messages to either local or remote queues.
 
Description of the View
Data displayed
Queues
 
•
Health. The queue health, based on the highest severity alarm. Hovering over this field opens a dwell listing the most recent alarms for this queue.
 
•
Name. The queue name.
 
•
Type. The queue type:
Local. A queue that is owned by the queue manager to which the program is connected.
Remote. A queue that is owned by a different queue manager than the one to which the program is connected.
Transmission. A special type of local queue used to store messages before they are transmitted to a remote queue manager.
 
Queue Depth
 
•
Current. The current number of messages in the queue.
 
•
History. A graphic representation of the number of messages in the queue.
 
•
Period Max. The maximum number of messages in a queue for the selected interval.
 
•
High Limit (%). Contains the maximum number of messages that can be in the queue at any one time, as a percentage. This value determines when high depth warnings are issued, based on the following formula: high_limit * max_depth / 100
 
•
Max Depth. Contains the maximum number of messages that can ever be put in the queue; that is, the queue is full at this number.
 
Oldest Message Age
 
•
Current. The current age of the oldest message in the queue.
 
•
History. A graphic representation of the age of messages in the queue.
 
•
Clusters Name. The names of any clusters to which this queue manager belongs.
 

Remote Queue Status View

How to Get Here
From the MQ Server Application View, select a Remote queue manager in the Application Queues Table.
Purpose
This view shows the data flow for a selected remote queue, including the status of the channels. The flow fields and disk object in this view display color-coded real-time behavior, indicating the severity.
 
Description of the View
Data displayed
Buffers Received/Sent. The number of buffers received or sent on the channel during the data sampling period.
 
Bytes Received/Sent. The number of bytes received or sent on the channel during the data sampling period.
 
Queue Depth. Shows the number of messages in the queue.
 

Rules

Foglight allows you to create flexible rules that can be applied to complex, interrelated data from multiple sources within your distributed system. You can associate several different actions with a rule, configure a rule so that it does not fire repeatedly, and associate a rule with schedules to define when it should and should not be evaluated.
Different types of data can be used in rules, including registry variables, raw metrics, derived metrics, and topology object properties.
There are two types of rules in Foglight for IBM WebSphere MQ Server: simple rules and multiple-severity rules. A simple rule has a single condition, and can be in one of three states: Fire, Undefined, or Normal. A multiple-severity rule can have up to five severity levels: Undefined, Fatal, Critical, Warning, and Normal.
Rule conditions are regularly evaluated against monitoring data (metrics and topology object properties collected from your monitored environment and transformed into a standard format). Therefore, the state of the rule can change if the data changes. For example, if a set of monitoring data matches a simple rule’s condition, the rule enters the Fire state. If the next set does not match the condition, the rule exits the Fire state and enters the Normal state.
A rule condition is a type of expression that can be true or false. When it evaluates to true, the rule is said to fire, causing any actions that are associated with the rule or severity level to be performed. You can configure a rule to perform one or more actions upon entering or exiting each state. When a multiple-severity rule fires, an alarm also appears in Foglight for IBM WebSphere MQ Server.
For more information see the Foglight Administration and Configuration Guide.
FoglightFoglight for IBM WebSphere MQ Server provides an effective monitoring solution for the distributed IBM WebSphere MQ infrastructure. The rules included in this cartridge alert you to messaging infrastructure problems. Foglight for IBM WebSphere MQ Server monitors the current health of the entire distributed messaging environment.
When service degradations are detected, Foglight for IBM WebSphere MQ Server sends alerts to the event console. Optionally, Foglight for IBM WebSphere MQ Server can be configured to send emails, pager messages, or perform other actions you define. Performance data can be viewed, analyzed and reported using Foglight for IBM WebSphere MQ Server.
This cartridge includes the following rules:
•
Channel Startup Error Rule
•
Channel Stopped Rule
•
Channel Transmission Problem Rule
•
Channel TransmissionQ Error Rule
•
Check Authority Events Rule
•
Check Channel Auto-Def Events Rule
•
Check Inhibit Events Rule
•
Check Local Events Rule
•
Check Performance Events Rule
•
Check Remote Events Rule
•
Check Start Stop Events Rule
•
Cluster Command Queue Error Rule
•
Cluster Repository Queue Error Rule
•
Cluster Transmission Queue Error Rule
•
Command Queue Error Rule
•
Dead Letter Queue Not Empty Rule
•
Dequeue Rate Rule
•
Enqueue Rate Rule
•
Init Queue Error Rule
•
Listener Not Running Rule
•
MQ Agents Observe Same Queue Manager Rule
•
MQ DeadLetterQueue Exists Rule
•
MQ Statistics Interval Rule
•
Queue Depth Warning Rule
•
Queue Filling Rule
•
Queue is Disabled Rule
•
Queue Manager Not Available Rule
•
Queue Monitoring Rule
•
Queue Not Being Read Rule
•
Queue Triggering Rule
•
Receiver Channel Stopped Rule
•
Shared Monitoring Configuration Rule
•
Slow Message Rule
These rules monitor the channels, queue managers, and queues in your system. There are different types of queues that are monitored. Concrete queues include the queues that are associated with a local queue manager, such as local queues, that are managed by the local queue manager, and transmission queues, that store messages before transmitting them to a remote queue manager. Remote queues, managed by remote queue managers, do not fall into the category of concrete queues.
Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação