Open iT Queries
The Open iT queries allow users to generate Analysis Server-like reports without Analysis Server installation. It also connects directly to the Core Server flat data files for report creation to avoid loading a massive amount of data in the SQL server, which may cause delays.
Make sure that there is sufficient data on the Core Server before generating queries.
These queries can be used to create reports using the following data types:
ID | Data Type Name | Columns |
---|---|---|
2 | LSF (Batch Jobs) | |
4 | PSM-Shell | |
5 | LSF (LSF Acct) | |
29 | Filespace | |
31 | Windows Periodic Summary App Usage | |
32 | Unix Application Usage | |
46 | Individual License Use v2.0 | |
48 | Grid Engine | |
49 | Host User License Use | |
50 | Host User License Use Logfile | |
52 | Denied License use Logfile | |
53 | Windows Module Usage | |
54 | Extended Pacct | |
56 | UsageAnalyzer Break | |
57 | UsageAnalyzer Work | |
58 | UsageAnalyzer Events | |
61 | Individual License Queued | |
62 | License Optimizer Use | |
64 | License Optimizer Events | |
75 | License Logfile Events | |
77 | Individual Queued Logfile | |
78 | LSF Pending Reason | |
79 | Internet Explorer URL Use | |
80 | PBS Accounting | |
84 | Individual License Use Logfile | |
87 | Process Accounting | |
89 | Total License Use Licenseevents | |
92 | License Optimizer Action | |
93 | Olap Raw Hourly | |
94 | Olap User Concurrency | |
95 | Usergroup License Use v3.0 | |
98 | License Optimizer Individual Usage | |
102 | Olap Total Use | |
104 | License Logfile Events v2.0 | |
105 | Individual Module Usage | |
107 | Denied License Use Licenseevents | |
110 | License Application Version | |
112 | user License Use Appversion | |
114 | Total PPU License Use | |
116 | Total PPU License Use Logfile | |
117 | Dongle Data Inventory | |
118 | Product Inventory | |
119 | Dongle License Use | |
120 | Web App browser Log | |
124 | License Model User Concurrency | |
127 | License Host User Usage Distinct Host | |
129 | FlexNet Log Events | |
130 | Windows Application Usage | |
132 | V-Ray License User Concurrency | |
135 | License Product Assignment | |
136 | License Product Assignment | |
137 | License Token Individual Usage | |
138 | License Token Total Usage | |
139 | License Subscription Inventory v2 | |
140 | License Product Assignment v2 |
Queries
There are three available queries that can be used to generate custom Analysis Server-like reports.
select
The select query is used to get one or more data types. It concatenates two tables to show two data types.
Parameters
Name | Description |
---|---|
output | The output directory where the report will be saved. |
date | The date of the report. The default value is last month. |
start | The start date of the report. |
end | The end date of the report. The default value is the current time. |
months | The number of months to include in the report. Default is one. |
tz | The timezone of the report. Default is the Core Server's local timezone. |
freq | Frequency of the report: M (monthly), D (daily), Y (yearly). Default is M. |
datatype | The data type(s) to include in the report. |
Example
http://desktop123win:8080/api/queries/select?datatype=102,75&freq=D&date=2020-10-01
This example generates a report showing data from data types 102 and 75 for October 1, 2020.
join
The join query is used to combine data types based on their common column. This query uses left join
by default.
Parameters
Name | Description |
---|---|
output | The output directory where the report will be saved. |
date | The date of the report. Default is last month. |
start | The start date of the report. |
end | The end date of the report. Default is current time. |
months | The number of months to include. Default is one. |
tz | Timezone. Default is Core Server's local timezone. |
freq | Frequency of report: M, D, Y. Default is M. |
datatype | Data types to include. |
on | Common column(s) between data types. |
how | Join method. Default is left join. Refer to this link for values. |
Example
http://desktop123win:8080/api/queries/join?datatype=94,75&on=datetime,product,package&date=2021-06-21&freq=D
This example joins data from data types 94 and 75 using datetime
, product
, and package
for June 21, 2021.
sql
The sql query is used to create reports that include data that aren't stored in the database.
Parameters
Name | Description |
---|---|
output | Output directory of the report. |
date | Date of the report. Default is last month. |
start | Start date. |
end | End date. Default is current time. |
months | Number of months. Default is one. |
tz | Timezone. Default is Core Server's local timezone. |
freq | Frequency (M, D, Y). Default is M. |
datatype | Data type(s) to include. |
custom | Comma-separated list of custom tables (CSV files in $DATA/custom ). Filename only. |
id | Columns to use as index for each data type. |
name | Name for each SQL query. Use this to reference tables in --query . Must match --query count. |
query | SQL query to run (can be used multiple times). Last one is returned. |
body | Alternative to query , accepts multi-line SQL query. |
Example
http://desktop123win:8080/api/queries/sql?datatype=139&date=2021-06-21&freq=D&custom=cost
This combines data type 139 for June 21, 2021, with a custom table named cost.
Please ensure that the custom table name is accurate and located in the $DATA_DIR/custom
directory of the Core Server.