Server Events

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Advanced Alerting

With the Advanced Alerting plugin installed, there will also be a new trigger type available, Clustering Channel Synchronization: When the channel synchronization process detects that an action should be taken, it will first send a Submitted event that can be triggered on. When that action finishes, it will send one of these two triggerable events: Succeeded: The task finished without any errors. Failed: The task finished with errors. This usually means that the channel was not able to be deployed/started/etc. With this event, the "exception" variable containing the full error stacktrace will be available in the template context. In addition to all of the regular template variables that are available in alert template contexts, this trigger also adds the following variables: Variable Description action The channel or connector action being taken. Will be one of: Deploy, Undeploy, Start, Stop, Pause, Resume event The stage of the current task. Will be one of: Submitted, Succeeded, Faile

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Strict Mode Disabled

When this option is disabled, this strict synchronization is loosened, and other nodes are able to freely join the cluster without waiting for channel-specific tasks to finish. In addition, channel tasks will not block each other either. The startupDeploy and channelOperation cluster-wide locks are not acquired on startup in this case. This means that it is possible that channels could get out-of-sync, at least temporarily. For example: Channel A is currently deployed and Started across the cluster. A new server joins the cluster and sees that Channel A is currently deployed and started across the cluster, so it prepares to deploy and start that channel as well. Meanwhile, a user stops Channel A. The newly joined server deploys and starts Channel A. Now Channel A is Started on one server but Stopped on another. To address this, a separate channel synchronization process will be used to detect whether channels ever get out of sync and then deploy/undeploy/start/stop/etc them as necessar

Mirth® Connect by NextGen Healthcare User Guide

Event Attributes Table

The attributes table at the bottom of the Event Browser shows more detailed information about a particular event. This will typically include the channel ID / name, if the event is a channel operation like start/stop/deploy. If the event is an error, the attributes table will typically show any exception associated with the event. If an attribute value is too long and is truncated in the table, you can double-click the table row to display the value in a separate dialog: Parent topic: Events View

Mirth® Connect by NextGen Healthcare Advanced Clustering User Guide

Strict Channel Synchronization

As of Mirth® Connect version 3.12, there is a new Strict Channel Synchronization feature available in the Clustering settings: Strict Mode Enabled Strict Mode Disabled Server Events Advanced Alerting Advanced Configuration Strict Mode Enabled Strict Mode Disabled Server Events Advanced Alerting Advanced Configuration

Mirth® Connect by NextGen Healthcare User Guide

Events View

System events (such as logons, errors, and channel updates) log to an internal database that you can view using the Events view. The Events browser enables you to view and search all user and system events that have occurred on your server. This includes any user actions like logging on and modifying or deploying channels. It also includes system events like startup and shutdown, and the Data Pruner. Image of the Events view Navigation Events Table Event Attributes Table Searching Events Event Tasks Parent topic: Monitor Views Related concepts Data Pruner

Mirth® Connect by NextGen Healthcare User Guide

Metadata Table Columns

Column Description ID The unique ID of the event in the database. This column is hidden by default. For additional information, see Working With Tables. Level An icon indicating the event's severity level ( Information, Warning, or Error) . Date & Time The date and time the event was logged. Name The name of the logged operation, or a description of the warning/error. Server ID The unique ID of the server from which the event was logged. User If the event originated from a user action, this will be both the user ID and user name. If no user is associated with the event, it will show 0 (System). Outcome For user requests and server tasks, this icon indicates whether the action was successful or not. For example a failed user login attempt will show a failure icon. IP Address For user requests, the IP address of the originating client. Channel ID - Message ID If the event occurs in a specific channel, the channel ID will be logged. If the event occurs due to a specific message, a dash wi

Server Events

Recommendations

Advanced Alerting

Strict Mode Disabled

Event Attributes Table

Strict Channel Synchronization

Events View

Metadata Table Columns

Advanced Alerting

Strict Mode Disabled

Event Attributes Table

Strict Channel Synchronization

Events View

Metadata Table Columns