No. of Messages (Threshold)

Option	Description
Status	The message status being observed, either Queued or Error.
Threshold	The alert triggers when the specified statistic is greater than or equal to this value.
Longer Than	The alert does not trigger until the specific statistic is greater than or equal to the threshold for longer than this duration. If this value is left blank, the alert triggers immediately. (e.g. 5m, 3h30m, 1d6h45m30s) .(Optional)
Re-trigger Interval	After the first trigger, the alert triggers again periodically at this interval until the status count drops below the threshold (e.g. 5m, 3h30m, 1d6h45m30s).
Aggregate By	Select Connector to apply this trigger condition individually to each enabled connector. Select Channel to apply this trigger condition to the sum of each channel's enabled connectors. Select Global to apply this trigger condition to the sum of all enabled connectors across all channels.

Advanced Alerting User Guide

No. of Messages (Sliding Window)

The No. of Messages (Sliding Window) trigger type listens for incrementing statistics on your channel or connector. If a certain amount of increment events occur for a particular statistic in a certain window of elapsed time, the alert triggers. For example, in the following image, the alert triggers if there are 0 Received statistic events within the window of 1 hour. If your channel is usually very busy, this might indicate that there is a problem with the source system being able to send to your channel. Image of the Sliding Window Properties pane As another example, you can set up your alert to trigger when a connector filters 50 messages or more within a 10-minute time window: Another example displayed in the Sliding Window Properties window. The following graphic shows when the actual alert trigger would occur: Image depicting the triggering of an alert. The following table describes the available options in the Sliding WIndow Properties pane. Option Description Status The messag

Advanced Alerting User Guide

Deployed State

The Deployed State trigger type observes the state of the currently deployed channels. You can use this to alert when a channel has stopped or started for a certain amount of time. For example, in the following image, the alert triggers if the channel is in the Starting, Stopping, or Stopped states for longer than 10 minutes. Image showing an alert that triggers if the channel is in the Starting, Stopping, or Stopped states for longer than 10 minutes. As another example, you can set up an alert to trigger if someone has attempted to stop a channel, but it remains in the Stopping state for some period of time: Image that shows an alert that triggers if someone has attempted to stop a channel, but it remains in the Stopping state for some period of time. Option Description Longer Than This alert triggers after a channel/connector has been in a selected state for longer than this amount of time. If left blank, this alert triggers immediately when a channel/connector enters a selected stat

Advanced Alerting User Guide

About Trigger Types

Trigger types are pre-defined actions that initiate alerts. The following sections describe the different trigger types supported by the Advanced Alerting extension. Channel Error The Channel Error type triggers whenever a channel encounters an error. No. of Messages (Sliding Window) The No. of Messages (Sliding Window) trigger type listens for incrementing statistics on your channel or connector. If a certain amount of increment events occur for a particular statistic in a certain window of elapsed time, the alert triggers. No. of Messages (Threshold) The No. of Messages (Threshold) trigger type observes the current queued or error statistics for a particular channel or connector. If the statistic is greater than equal to the specified threshold for a certain amount of time, this alert will trigger. Deployed State The Deployed State trigger type observes the state of the currently deployed channels. SSL Certificate Validation The SSL Certificate Validation trigger type listens for err

Advanced Alerting User Guide

Enabled Channels

The Enabled Channels section enables you to decide which channels and connectors may trigger an alert. You can choose to, for example, only listen for error events coming from source connectors, and ignore those coming from destination connectors. Image of the Enabled Channels sections where you can select which channels and connectors can trigger an alert. The [New Channels] option indicates that you want an alert to listen for error events on any new channels that are created after the alert was initially created. Similarly, the [New Destinations] option indicates that you want an alert to listen for error events on any new destinations that are created for a channel after the alert was initially created. Image of the [New Channels] option. Parent topic: Overview of the Edit Alert View

Mirth® Connect by NextGen Healthcare User Guide

Advanced Queue Settings

Item Name Description A Retry Count Before Queue/Error The maximum number of times the connector attempts to send the message before queuing or erroring. B Retry Interval (ms) The amount of time (in milliseconds) that should elapse between retry attempts to send messages. This interval applies to both the queue and initial retry attempts. C Rotate Queue If enabled, when any message fails to be sent from the queue, the connector will place the message at the end of the queue and attempt to send the next message. This will prevent a single message from holding up the entire queue. If the order of messages processed is important, this should be disabled. D Regenerate Template Regenerate the template and other connector properties by replacing variables each time the connector attempts to send the message from the queue. If this is disabled, the original variable replacement is used for each attempt. E Include Filter/Transformer If enabled, the filter and transformer is re-executed before

Mirth® Connect by NextGen Healthcare User Guide

Dashboard Table Columns

Column Description Status The status of the deployed channel. Common statuses include: Deploying: The channel is in the middle of being deployed. If the channel appears to be stuck in this state, it may mean a deploy script is taking a long time. Undeploying: The channel is in the middle of being undeployed. If the channel appears to be stuck in this state, it may mean a shutdown script is taking a long time. Starting: The channel is in the middle of starting up. If the channel appears to be stuck in this state, it may be in the middle of recovering unfinished messages. Started: The channel is currently started. If the node color is orange instead of green, it means that not all connectors underneath the channel are started. Pausing: The channel is in the middle of pausing. The source connector is in the middle of stopping, and will wait until all currently processing messages have finished before doing so. Paused: The channel is currently paused. The source connector is currently stop

No. of Messages (Threshold)

Recommendations

No. of Messages (Sliding Window)

Deployed State

About Trigger Types

Enabled Channels

Advanced Queue Settings

Dashboard Table Columns

No. of Messages (Threshold)

No. of Messages (Sliding Window)

Deployed State

About Trigger Types

Enabled Channels

Advanced Queue Settings

Dashboard Table Columns