Importing a Workload Data File

Once you have a supported workload data file in hand, you can start importing it using Workload Data Importer (WDI). In most cases, you will import one single CSV file, and it is recommended that you import one single CSV file. However, you can import up to five CSV files at a time either directly or compressed with a ZIP file. When importing multiple files, they are processed and analyzed together – as if it is a single data set. A single Analysis Policy is used for each instance of the Workload Data Importer run, so the type and order of columns, as well as the formatting of individual values, must be consistent across all CSV files in the same instance.

For example, attempting to import two CSV files at the same time, one in EMC® VMAX® format and one in Hitachi® Tuning Manager format is not allowed, as there is not a single analysis policy that can be applied to both formats. In this scenario, you need to do two separate imports. Also, importing two different CSV files from the same storage array, for example, one CSV file for command statistics and one CSV file for file system layout, is also not allowed, as these are still two different CSV file structures.

Additionally, when importing multiple CSV files, make sure that the data in the files does not overlap in time. Explained another way – you cannot have the same timestamp present in multiple files.You can select the files to import in two ways. You can drag up to five files into the Drag and drop section on the Log File screen. You can also click the select a file to upload link, which takes you into a standard file system dialog box, and then select the files there.

Custom Parser

If imported data cannot be recognized there is an option to use the custom parser. Custom parser uses a custom script produced by Virtana Professional Services team. The script prepares input data and converts it to the format that can be recognized by WorkloadWisdom.

The list of available custom parsers expands as more custom scripts are produced. Currently, Dell EMC Unity data is supported.

Imported data must be in the form of a zip archive. The top level of this archive should contain files that are used as input data for the custom parser. As soon as the zip file is uploaded the parsing process begins.

Parsing time depends on the size of input data. If any errors are produced by the parsing script, the errors are shown on the screen and the selected archive cannot be used.

When the custom parsing stage finishes successfully the output of the parser is used as imported data on the Workload Data Import page. The next steps are identical to the import process without using the custom parser.

Import Process

The importer uploads the file and then filters the list of analysis policies to those that match the file. It then automatically shows a list of analysis policies that can be applied to the imported CSV file.

The default analysis policies that ship with WorkloadWisdom appear in green, and if you have any modified and customized versions of the analysis policy that is applicable to the imported CSV file, then they will appear in black.

Analysis policies parse and analyze the production workload data, and allow you to select the workload type you want to create from the workload data. Typically, there is a set of policies for each supported workload data source, where each policy in the set supports creating a different type of workload. Often, for each supported CSV file structure, there can be multiple analysis policies for it. For example, you can have an analysis policy for HDS data that creates constant workloads, and you can have an analysis policy for the same HDS data that creates temporal workloads. The analysis policy is labeled accordingly so you know 1) what data source it can analyze, and 2) what type of workload it creates.

Workloads are labeled Constant or Temporal. A temporal workload varies the IOPs over time, according to the patterns observed in the data, and can only be created through workload acquisition. A constant workload uses a set level of IOPs, based on observed values of IOPs, latency, or throughput. Constant or temporal workloads can be averaged into one summary workload, or clustered into multiple workloads that run together and make up a composite workload.

Select the analysis policy that creates the type of workloads in which you are interested. If you click the button next to the drop-down list it opens a new window or tab and takes you to the Workload Analysis Policy Library.

You can edit certain aspects of the policy that you selected for this workload by clicking on the button.

Items that are not visible in the edit page, such as what workload is created or how the data is analyzed, require Virtana Support to change them. If there is not an Analysis Policy that meets your needs, contact Virtana Support.