Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning
This page refers to functionality that has been removed from License Statistics. This information no longer applies to License Statistics v6.3 and newer.

Obtaining information about usage history
Anchor
obtain
obtain

You can easily fetch metrics about usage history by sending one of the the following HTTP requests.

Code Block
languagejs
firstline1
titleUsage history for a single feature
GET /api/v1/report/feature/${featureId}/usage-history/${returnType}?sd=${YYYY-MM-DD}&ed=${YYYY-MM-DD}&granularity=${granularity}$(additional parameters, as needed)

 

Usage History for Feature

...


Code Block
languagejs
firstline1
titleUsage history for a composite feature on license server group
GET /api/v1/report/feature-composite/${fcid}/usage-history/${returnType}?sd=${YYYY-MM-DD}&ed=${YYYY-MM-DD}&granularity=${granularity}$(additional parameters, as needed)

Anchor
comparison
comparison

Code Block
languagejs
firstline1
titleUsage history comparison for features
GET /api/v1/report/feature-comparison/${ucompi}/report/${returnType}?sd=${YYYY-MM-DD}&ed=${YYYY-MM-DD}&granularity=${granularity}


Code Block
languagejs
firstline1
titleUsage history for a license server
GET /api/v1/report/license-server/${featureIdlsid}/usage-history/${returnType}?sd=${startDateYYYY-MM-DD}&ed={endDateYYYY-MM-DD}&granularity=${granularity}$(additional parameters, as needed)

 where:


Code Block
titleUsage history for a license server group
GET /api/v1/report/license-server-group/${lsgid}/usage-history/${returnType}?sd=${YYYY-MM-DD}&ed={YYYY-MM-DD}&granularity=${granularity}$(additional parameters, as needed)

where $  - $ indicates a variable value that you can replace with an appropriate value, as needed - the possible parameters are as follows:a value that best suits your needs. The possible parameters are described below.

ParameterRequiredTypeDescription
${featureId}YesintegerInternal License Statistics identification of the feature to show usage history for.
${fcid}Yesinteger
Specifies feature-specific parameters
Internal License Statistics identification of the feature composite to show usage history for.
${ucompi}YesintegerInternal License Statistics identification of feature history comparison.
${lsid}YesintegerInternal License Statistics identification of the license server to show usage history for.
${
returnType
lsgid}Yes
stringSpecifies the format in which license usage data should be returned. The format can be one of the following: json, csv, xls or pdf
integerInternal License Statistics identification of the license server group to show usage history for.
${returnType}YesstringStandard format option. See Making an API request for details.
sdYes
string
date
Specifies the start
Start date for which the report will be generated
in YYYY-MM-DD format; for example, 2016-01-20
.
edYes
string
date
Specifies the end
End date for which the report will be generated
in YYYY-MM-DD format; for example, 2016-01-27
.
granularityYes
integer

Specifies granularity of the returned data; Can be one of the following:

  • quarter - 2
  • month - 3
  • week - 4
  • day - 5
  • hour - 6
rnNostringSpecifies the name of the report that will be displayed once the report has been exported to PDF or Excel.filterNojson/string

Applies filtering license usage data on all fields. To filter your data, use the following format:

Code Block
languagejs
[{"value": intOrString, "field": "${lud | lumin | lua | lumax | lbmin | lbmax | ldtc | hu | ft}"}]
fieldsVisibilityNojson/string

Specifies field visibility settings, for example:

Code Block
languagejs
{"lud": "1", "lumin": "1", "lua": "1", "lumax": "1", "lbmin": "1", "lbmax": "1", "ldtc": "1", "hu": "1", "ft": "1"}

where number "1" indicates that a specific field is visible.

Note that the order of the settings you make is important – when exported, the fields will be visible in exactly the same order you specify here.

limitNointegerDetermines the maximum number of data records that can be returned. The value must be greater than zero.offsetNointegerSpecifies the offset of the first row to return.orderByNostringSpecifies the field by which you want to order your data records. The field name can be one of the following:
enumeration

Period type the result is aggregated for. See granularity descriptions for further details.

standard report optionsNovarious

See Making an API request for details.

Response

On success, this report will contain one row for every feature and every period in which the feature was monitored. Each row consists of the following columns.

ColumnFull nameTypeDescriptionVisible by default in export
ludDatestring

The time period. Format depends on granularity.

(tick) Yes
fidFeature IdintegerInternal License Statistics identification of the feature(minus) No
fnsFeature NamestringFeature name.(warning) Visible for all, but feature
fvFeature VersionstringFeature version.(warning) Visible for all, but feature
ftypeFeature TypeenumerationSee feature type descriptions for details.(warning) Visible for all, but feature
luminMin UsedintegerMinimal number of licenses of the feature used in the period.(tick) Yes
luaAvg UsedfloatAverage number of licenses of the feature used in the period.(tick) Yes
lumaxMax UsedintegerMaximum number of licenses of the feature used in the period. (tick) Yes
lbminMin BorrowedintegerMinimal number of licenses of the feature borrowed in the period.(tick) Yes
lbmaxMax BorrowedintegerMaximum number of licenses of the feature borrowed in the period. (tick) Yes
ftTotalintegerTotal number of licenses of the feature available in period.(tick) Yes
huHours UsedfloatCumulative time used by all licenses of the feature in the period, in hours.(tick) Yes

ldtc

DenialsintegerNumber of denials of check out of a license of the feature in the period.(tick) Yes

Note that the order in the table is the default order of the columns in the exported file for the license server and license server group reports. For feature, feature composite and comparison default order is: fn, fns, fv, lud, lumin, lua, lumax, lbmin, lbmax,

...

ft, hu,

...

ldtc.