In this case it has less than 10 users running it. That is fine and just means that particular application doesn’t match the filter applied. Note: In the Preview Pane we have dropped the application with a workload ranking of 2. If additional filters were needed they can be added by checking the ‘green plus sign’ icon. This is done easily on the Filters tab where we have selected the column ‘User Count’ and added a condition of greater then (>) 10. Since there are lot of process and applications running in our environment we want to only look at those where 10 or more users are running the specific application. In this example we are going to add one Filter to our query. The Stratusphere API supports an extensive Filtering ability. In our case we also want the sort to be ‘ascending’ so the top workload rankings are listed first. The Sort column is selected on the Format tab. The application with the highest load is ranked # 1 and so on. As mentioned, Workload Ranking is a great metric to determine overall desktop load so we are going to choose that column as our sort. With our focused set of columns selected we can now set the Sort Order for the API query being built. It provides an excellent overall metric to sort by where you are looking to see what applications are causing the most consumption load on the desktops versus sorting by versus sorting by specific metrics like CPU, Memory or IO. Workload is a Stratusphere UX composite metric that looks at a combination of metrics from the desktop’s OS perspective. In addition the Workload Ranking was added to show overall resource consumption of an application. This gives us not only the user counts we were looking for per application, but also a Memory, a CPU and IO based metrics. These columns will show in the API query following your Basis (grouping) column or columns. On the Columns tab you can select and order the specific columns required. In our example this is more data then we require so we are going to select a focused set of columns that we want to have as part of the API query. It contains the default columns for the Inspector chosen. This will provide application related data summarized and grouped by the Basis, in this case by Application Name.Īt the bottom of the API Builder interface in a Preview Pane it shows the first 10 rows of data for the API query we are building. We want to select the ‘Application Inspector’ from the Main Tab and use the default Basis ‘Application Name’. In this use case we are looking for application related metrics. This focuses the API query on exactly what type of data we want to extract. The first thing we want to do is set our inspector. Now let’s look at a specific use case as an example, to show the flexibility and ease of use the API Builder.Īudit how many users are using a particular application for yesterday. You can access the API builder directly with the following URL. In this post I’ll showcase the power of the Stratusphere API, and the ease at which you can use employ Stratusphere metrics and information to perform tasks such as performing ad hoc application audits. With this new tool you can quickly build API URL calls with simple graphical point and click selections. Now included is a graphical tool, called the Stratusphere API Builder. Now with the release of Stratusphere 5.7 using the API has gotten even easier. This gives the ability to integrate the Stratusphere UX/FIT data into any tool you may use without having to understand all the intricacies of the underlying Stratusphere database. ![]() This data can be extracted into various formats including JSON (JavaScript Object Notation) and CSV files. This API provides a fast and easy to understand method of extracting the various metrics and data captured from Stratusphere UX/FIT directly through a URL call. A few months ago the Stratusphere API was introduced.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |