Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Managing Ensemble Productions - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
7<br />
Event Log<br />
The [<strong>Ensemble</strong>] > [Event Log] page displays the event log entries for the currently running production. You can display this<br />
page from the <strong>Ensemble</strong> Management Portal as follows:<br />
• From the <strong>Ensemble</strong> Menu — Click Event Log<br />
• From the [<strong>Ensemble</strong>] > [Maintenance] > [Purge] page — Click Show Event Log<br />
There is a Purge command to purge outdated entries from the event log. at the top of the Event Log page.<br />
The <strong>Ensemble</strong> Event Log page has two display areas, one above the other. The top display lists the event log entries recorded<br />
since the production was last started. The bottom display permits you to enter search criteria to filter the list of events. If<br />
the top display is empty when you first open it, click the Search command in the bottom display.<br />
7.1 Event Log Entries<br />
The Event Log top display contains a table. Each row in the table provides the following columns of information about an<br />
event:<br />
• # — An incremental count of the number of entries in the table.<br />
• ID — The unique identifier for the message that comprises this event log entry.<br />
• Time Logged — The date and time when this entry was logged.<br />
• Type — Indicates the type of entry: Alert, Assert, Error, Info, Status, Trace, or Warning.<br />
• Job — The system job that hosted the event.<br />
• Session — The unique identifier for the session that is (or was) associated with this message. A session marks the<br />
beginning and end of all the activities prompted by a primary request message from outside <strong>Ensemble</strong>. The primary<br />
request message has an ID value that is identical to the Session. Several additional messages may be instantiated within<br />
<strong>Ensemble</strong> during the session, in order to fulfill the primary request. All of these messages share the same Session, but<br />
each has a different ID value.<br />
The Session number is a link; click on it to view a visual trace of the session.<br />
• Source — The configuration item (service, process, or operation) that sent the message.<br />
• Method — The host class method that was in progress when the event was logged.<br />
• Text — The text string associated with the event log entry.<br />
<strong>Managing</strong> <strong>Ensemble</strong> <strong>Productions</strong> 67