Event Attributes Table

Mirth® Connect by NextGen Healthcare User Guide

Events Table

This table shows metadata (ID, timestamp, operation name) about each event that has been stored by the server. The Page Size option dictates the number of events shown in the table simultaneously (for additional information, see Searching Events) . When you first enter the Event Browser, by default the latest 100 events appear. For general information about working with tables in Mirth® Connect, see Working With Tables. Metadata Table Columns PHI Events Parent topic: Events View

Mirth® Connect by NextGen Healthcare User Guide

Searching Events

The Event Browser search capabilities are very similar to the Message Browser. For information on many of these shared components, see Search Messages. The following search options are unique to the Event Browser: Item Name Description A Name The operation name or a short description of the event's warning / error. All events that contain this string somewhere in the name (case-insensitive) will be returned. B Level Check these boxes to search for events with the INFORMATION, WARNING, and/or ERROR levels. Advanced Search Filter Parent topic: Events View

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 Advanced Clustering User Guide

Server Events

When the channel synchronization process takes an action, it will also send an event to the Event Log. This is viewable and searchable in the Event Browser: Image of the Events browser. The level will be "Information" if the task was successful. If the task failed, the level will be "Error", and you will also be able to view the full exception stacktrace in the event attributes: Image of a full exception stacktrace in the event attributes. Parent topic: Strict Channel Synchronization

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

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

Event Attributes Table

Recommendations

Events Table

Searching Events

Events View

Server Events

Metadata Table Columns

Advanced Alerting

Events Table

Searching Events

Events View

Server Events

Metadata Table Columns

Advanced Alerting