The Watcher Node uses End-User Performance Simulation data files to store the results of a simulation. Here, the filename convention and the syntax of the data files are described.
The End-User Performance Simulation data file should be stored in the root of the EUP Collector Path. There are no restrictions regarding the name of the file, except that the file needs to contain the extension .eum.
Note: To create End-User Performance Simulation data files with a unique name,
it is advised to use a GUID or a detailed date and timestamp in the filename.
Note: The Backbone End-User Performance Management Pack imports all files if the file extension starts with .eum.
This means that a file with file extension .eumm_simulation1 is imported as well.
The End-User Performance Simulation data file is a text file in Unicode format. Each file starts with <Start> data” and ends with <End data>, both on a single line. The <Start data> and <End data> lines are used by the EUP Collector to verify whether a file is ready to process. Without these lines, the EUP Collector will ignore the file.
The simulation data is written between <Start data> and <End data>. Each line contains information about as single simulation instance or step. There is no specific order in which the data should be written to the file.
The data elements of the simulation instance and steps are delimited with a pipe character (|). Each line containing simulation data should have the syntax described below:
<Date and Time>|<Watcher Node>|<Instance ID>|<Step ID>|<Measured time>|<Status>|<Context>
The table below describes each element within a single line:
Name | Type | Mandatory | Explanation |
---|---|---|---|
Date and Time | Datetime | Yes | The date and time the simulation or step is executed. The used date and time format should be according to the regional settings of the EUP Collector and the Default Action Account used by the Microsoft Monitoring Agent. |
Watcher Node | String | Yes | The FQDN or Hostname of the Watcher Node that corresponds to the FQDN or Hostname that is specified in the EUP Configuration file (see Watchers). |
Instance ID | String | Yes | The ID of the simulation instance corresponding to the ID’s specified in the EUP Configuration file (see Simulation instance). |
Step ID | String | Yes | The ID of the step corresponding to the ID’s specified in the EUP Configuration file (see Steps). The step ID is left empty when the measured time represents the simulation instance time. |
Measured time | Integer | Yes | The measured time in milliseconds. When the status is false, the value should be negative (-1). Negative values are excluded from statistics to avoid that the given (invalid) time negatively biases the presented information. |
Status | Boolean | Yes | The status of the measured step or simulation instance indicates whether the measured step is valid or invalid. Valid steps and simulation instances are indicated with a true or a 1. Invalid steps and simulation instances are indicated with a false or a 0. |
Context | String | No | The context value is an optional string that can be used to add additional information to the alert or health state of the target. An example of additional information is the error message that is received by the simulation script. |
Name | Type | Mandatory | Explanation |
---|---|---|---|
Date and Time | Datetime | Yes | The date and time the simulation or step is executed. The used date and time format should be according to the regional settings of the EUP Collector and the Default Action Account used by the Microsoft Monitoring Agent. |
Watcher Node | String | Yes | The FQDN or Hostname of the Watcher Node that corresponds to the FQDN or Hostname that is specified in the EUP Configuration file (see Watchers). |
Instance ID | String | Yes | The ID of the simulation instance corresponding to the ID’s specified in the EUP Configuration file (see Simulation instance). |
Step ID | String | Yes | The ID of the step corresponding to the ID’s specified in the EUP Configuration file (see Steps). The step ID is left empty when the measured time represents the simulation instance time. |
Measured time | Integer | Yes | The measured time in milliseconds. When the status is false, the value should be negative (-1). Negative values are excluded from statistics to avoid that the given (invalid) time negatively biases the presented information. |
Status | Boolean | Yes | The status of the measured step or simulation instance indicates whether the measured step is valid or invalid. Valid steps and simulation instances are indicated with a true or a 1. Invalid steps and simulation instances are indicated with a false or a 0. |
Context | String | No | The context value is an optional string that can be used to add additional information to the alert or health state of the target. An example of additional information is the error message that is received by the simulation script. |
Note: The Microsoft Monitoring Agent reads the data and performs a cast to the specified type
(datetime, string or boolean). The format of the End-User Performance Simulation data in
the text file should match the type that is specified for the element.
Note: Strings do not have to be placed between quotes.
Note: End-User Performance Simulation data may be delivered in multiple files. This can be used
when a simulation instance consists of multiple simulation scripts which are nested.
An example of such a construction is simulating an application which running in a remote session.