Invocation sequences often contain important information of an application in a structured way that allows to easily convey findings in the application to the different stakeholders. Prior to the disk storage, the analyst was forced to create screenshots or copy/paste invocation sequences to files. With the disk storage, the analyst is able to save invocation sequences to a storage and later on forward the storage in question to the relevant stakeholders. These people can then use the user interface of inspectIT to import the storage and analyze the invocation as if it where stored within a CMR.
Save to Server
From version 1.5 is possible to save all data types to Storage. Please relate to the Saving data to Storage page for more information on how to save Timer, SQL, Exception or HTTP data.
Saving of invocations
Select wanted invocations
The invocations to be saved to the storage can be selected in the Invocation Sequence View. One or more invocations can be selected:
After selecting the Save on Server option the wizard will start helping you define where you want to save the data with possibility to specify some additional options.
Select storage to save invocations
On the first wizard page the user can select the storage to save data to. New storage can be created for this purpose or an already existing storage can be selected.
If the new storage should be created, the user is prompted to enter the storage name and optionally storage description.
On the other hand if Use existing storage is selected, one of the Storage that is currently in the Writable state has to be selected.
If the Auto-Finalize option is selected, then the chosen Storage will be finalized upon the Save operation and will be readable immediately.
Define data saving options
The next wizard page enables user to define additional saving options in terms of data types to be saved. As the invocations sequences are selected, by default the wizard will offer to save only invocation. However, since every invocation holds additional data about the SQL statements, exceptions and method invocations it is possible to also separately save this data. If so, the selected data types will be extracted from the invocations and will be available for analyzing separately from invocations.
On the last page the user can optionally add one or more labels to the storage that will be used for storing the data.