Health and Activity monitoring
Service Instances and Message Views in HAT
Use the Service Instances view to see what state suspended orchestrations or pipelines are in. The Service Instances view shows you metadata about the orchestration or pipeline.
When you see a suspended service or message in the event log, start your analysis with one of the Operations views. After you locate the service, you can investigate it further by using the Service Details, Message Flow, or Orchestration Debugger option on the shortcut menu.
In many cases, you cannot resume a suspended message—for example, if it is corrupt. However, you can choose to save a message to disk before removing it from the Suspended queue.
If a message does get suspended, an error is sent to the transport component, which might trigger a fix. If this does not happen, you can retrieve that message body, modify it, and resubmit it through another port.
Depending on the cause of the suspension, you might be able to resume suspended services. For example, if an orchestration hits a Suspend shape, or if a transport was unable to deliver a message, you can resume the instance by using the shortcut menu Resume command.
If you cannot resume the services, and you finish investigating the cause, you can terminate the instance. This removes the service from the message box. Terminating also removes any messages associated with this instance, if no other instance references them.
The following table describes the filters you can set.
When you need to troubleshoot transport-level problems, use the Message view to see undelivered messages. The Message view shows you metadata for each message as well as for the associated service instance.Note Suspend Service suspends orchestrations and pipelines even when the action is performed on a message instance.
When you see a suspended service or message in the event log, start your analysis with one of the Operations views. After you locate the service, you can investigate it further by using the Service Details, Message Flow, or Orchestration Debugger option on the shortcut menu.
In many cases, you cannot resume a suspended message—for example, if it is corrupt. However, you can choose to save a message to disk before removing it from the Suspended queue.
If a message does get suspended, an error is sent to the transport component, which might trigger a fix. If this does not happen, you can retrieve that message body, modify it, and resubmit it through another port.
Use the Resume option to resend a failed outbound message.Note HAT might not track suspended messages.
Depending on the cause of the suspension, you might be able to resume suspended services. For example, if an orchestration hits a Suspend shape, or if a transport was unable to deliver a message, you can resume the instance by using the shortcut menu Resume command.
If you cannot resume the services, and you finish investigating the cause, you can terminate the instance. This removes the service from the message box. Terminating also removes any messages associated with this instance, if no other instance references them.
SERVICE INSTANCES AND MESSAGES FILTER OPTIONS
The Service Instances and Messages views both provide the same filtering capability. Selecting a filter or filters restricts the size of the Results list. If the Results list is too large, the query will time out and no longer access the MessageBox database.The following table describes the filters you can set.
| Filter | Description |
|---|---|
| Host | Filters records for service instances that are enlisted in the selected Host or All. |
| Class | Filters records for service instances that match the service class, which can be Orchestration or Messaging or All. |
| Name | Filters records for the specified service name or All. |
| Status | Filters records where the service instance has a specified status of Suspended or Active or All. |
| Select Query Limit | Filters by a range of dates, to a specified number of matches. |
