Deployed State

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 state (e.g. 5m, 3h30m, 1d6h45m30s). (Optional)
Type	Select Connector to listen for state changes on enabled connectors. Select Channel to listen for state changes on enabled channels.

Advanced Alerting User Guide

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, the alert is triggered. For example, in the following image, the alert triggers if the Queued statistic on a particular connector is 1000 or more for longer than 1 hour. If the queued statistic stays in that condition, the alert triggers again every 15 minutes. Image of the Threshold Properties window The Re-trigger Interval determines how often you want an alert to keep triggering after the condition has been met: You can also use the Longer Than option to set an initial duration to wait before triggering the alert. This way short peaks above the threshold will not result in an alert. 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 val

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

Channel Error

The Channel Error type triggers whenever a channel encounters an error. You can decide what type of errors you want your alert to trigger on. This includes choosing among categories of error types, and optionally using a regular expression that only allows events whose error source, error message, or exception stacktrace matches. An image of the Errors section. Alert Error Categories Any: Select this option to trigger on all error categories. Source Connector: An error that originated from the source connector during deploy/start, receiving a message, or sending a response. Destination Connector: An error that originated from a destination connector during deploy/start, dispatching a message, or receiving a response. Serializer: An error that originated from the source or destination filter/transformer script, specifically when serializing the message to the internal representation (such as XML), or deserializing the message to the outbound data type format. Filter: An error that origi

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

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

Deployed State

Recommendations

No. of Messages (Threshold)

No. of Messages (Sliding Window)

Channel Error

About Trigger Types

Enabled Channels

Dashboard Table Columns

Deployed State

No. of Messages (Threshold)

No. of Messages (Sliding Window)

Channel Error

About Trigger Types

Enabled Channels

Dashboard Table Columns