|Time Stamp||The time stamp for the event message. The time stamp will be presented in the local time zone.|
|Type||The type of event—you can choose all types, or focus on events associated with proxies, virtual assets, unmatched messages, server events (such as start and stop), and other events (such as messages from custom listeners).|
|Asset||The name of event message’s source (a virtual asset or proxy). For example, if an event message comes from a proxy, the name of that proxy is displayed.|
|Category||The category of event—you can choose all event categories, or focus on messages coming to or from responders, messages to or from proxies, or error / warning / debug / informational messages (including messages from custom listeners).|
|Component||The associated EM Environment Manager component (if applicable).|
|Environment||The associated EM Environment Manager environment.|
|System||The associated EM Environment Manager system.|
|Responder||The endpoint of the virtual asset handling the message.|
|Client||The host name of the machine that sent the event message to Virtualize.|
|Client IP||The IP of the machine that sent the event message to Virtualize.|
|Server||The associated Virtualize server.|
|Iteration||The data source row used in the associated response or request.|
The Unmatched messages checkbox (at the bottom left of the page) shows/hides any incoming requests that could not be correlated to a virtual asset or message proxy. The Assets not assigned to any components checkbox shows/hides messages for proxies or virtual assets that are deployed on a connected Virtualize Serverserver, but are not attached to any Environment Manager component.
The table will them be "reset"—previously-shown messages will hiddenbe hidden, but any new messages that meet the filter criteria will be displayed.
- Mark the checkbox for each message you want to export.
- Click Create traffic file in the bottom left of the Event Messages table.
- In the dialog that opens, select the Virtualize Server server upon which you want the traffic file created, then specify as a name for the traffic file. Files will be created in the VirtualAssets folder.