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 per user for a feature
Anchor
obtain
obtain

You can easily fetch metrics about usage per user for a single feature by sending one of the following HTTP requestrequests.

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


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

where $ indicates a variable value that you can replace with a value that best suits your needs. The possible parameters are described below.

feature-specific parameters
ParameterRequiredTypeDescription
${featureId}Yesinteger
Specifies

Internal License Statistics identification of the feature for which you want to view usage history.

${
returnType
licenseServerId}Yesinteger/string
Specifies the format in which license usage data will be returned. The format can be one of the following: JSON, CSV, XLSX, or PDF.  

Internal License Statistics identification of the license server for which you want to view usage history, or "all" if information about all license servers is requested.

${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
. The date is in YYYY-MM-DD format; for example, 2017-05-20
.
edYes
string
date
Specifies the end
End date for which the report will be generated
. The date is in YYYY-MM-DD format; for example, 2017-05-27
.
gratYes
integer

Specifies granularity of the returned data, which can be one of the following:

  • Quarter - 2
  • Month - 3
  • Week - 4
  • Day - 5
  • Hour - 6
    enumeration

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

    agrtNointeger
    Specifies type

    Type of aggregation of the returned data. Aggregation type can be one of the following:

    Username
    • User - 1
    Hostname
    • Host - 2
    Username
    • User and
    hostname
    • host - 3
    • Usergroup - 4
    • Hostgroup - 5

    By default, data is aggregated by

    username and hostname

    user and host (3).

    rn
    standard report optionsNo
    string

    Specifies the name of the report that will be displayed once the report has been exported to PDF or XLSX. For CSV and JSON formats this parameter will be ignored.

    Note: If you don't pass this parameter, it will be generated automatically for PDF and XLSX types. If provided, it cannot be left empty.

    filter Anchorformat defformat defNojson/string

    Applies filtering license usage data on all fields.

    To filter by a string column, use the following format. 

    Code Block
    languagejs
    linenumberstrue
    [
    	{ 
    		"type": "string",
    		"field": ""${fud | un | ugn | hn | hgn | lsn | fns | fv | ftype}",
    		"value": "${value}"
    	}
    ]

    To filter by a numeric column, use the following format.

    Code Block
    languagejs
    linenumberstrue
    [
    	{ 
    		"type": "numeric", 
    		"comparison": "${gt | lt | eq}", 
    		"field": "${musage | hu | mu | hb | mb}",
    		"value": "${value}" 
    	}
    ]
    fieldsVisibility Anchorvisibility defvisibility defNojson/string

    Specifies field visibility settings, like this:

    Code Block
    languagejs
    linenumberstrue
    { 
    	"fud": "1", 
    	"un": "1", 
    	"ugn": "1",
    	"hn": "1", 
    	"hgn": "1",
    	"lsn": "1", 
    	"fns": "1", 
    	"fv": "1", 
    	"ftype": "1", 
    	"musage": "1", 
    	"hu": "1", 
    	"mu": "1", 
    	"hb": "1", 
    	"mb": "1"
    }

    where "1" indicates that a specific field is visible and ''0" indicates that it is not.

    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.orderByNostring

    Specifies the field by which you want to order your data records. The field name can be one of the following:

    fud | un | ugn | hn | hgn | lsn | fns | fv | ftype | musage | hu | mu | hb | mb

    (See this section for more field-specific information.)

    If orderBy is provided, orderDirection is mandatory.

    orderDirectionNostringDetermines whether the sorting results will be displayed in ascending (ASC) or descending (DESC) order. If orderDirection is provided, orderBy is mandatory.

    Response

    ...

    Code Block
    languagejs
    linenumberstrue
    {
    	"success": ${success},
      	"msg": ${message},
      	"data": [
        	{      		
    			"fid": ${featureId},      		
    			"lsid": ${licenseServerId},	
    			"uid": ${userId},
    			"uil": ${userIsLdap},
          		"fud": ${date},      					
    			"un": ${username},      			
    			"ugn": ${userGroupName},      		
    			"hn": ${hostname},
    			"hgn": ${hostGroupName},
    			"lsn": ${licenseServerName},
          		"fns": ${featureName},
          		"fv": ${featureVersion},
          		"ftype": ${featureType},
          		"musage": ${maxUsage},
          		"hu": ${hoursUsed},
          		"mu": ${maxUsed},
          		"hb": ${hoursBorrowed},
          		"mb": ${maxBorrowed}
        	}
      	],
      	"code": ${code},
      	"totalCount": ${count}
    }

    ...

    various

    See Making an API request for details.

    Response

    On success, this report will contain one row for each feature for each aggregator for each period. Each row consists of the following columns.


    ColumnFull nameTypeDescriptionVisible by default in export
    fudDatestring

    The time period. Format depends on granularity.

    (tick)Yes
    uidUser IDstring

    Internal License Statistics identification of the user for aggregations User(1) and User and Host(3).

    Otherwise, a semicolon-separated list of user IDs.

    (error) Unavailable
    unUserstring

    Name of the user for aggregations User(1) and User and host(3).

    Otherwise, a semicolon-separated list of usernames.

    (tick)Yes
    uilUser is from LDAP

    ...

    boolean.. This field is returned only when the requested aggregation type was usergroup.Hostname or hostnames, depending on aggregation type.hgn. This field is returned only when requested aggregation type was hostgroup.
    FieldTypeDescription
    successbooleanIndicates whether your API request was successfully processed.
    msgstringError message returned on failure.
    fidintegerFeature ID.
    lsidintegerLicense server ID.
    uidintegerUser ID.
    uilstring

    Information about whether the user is managed by LDAP

    fudstring

    Indicates period of time for which usage information is generated, i.e. date and time for hourly usage and dates for the remaining granularity options.

    unstringUsername or semicolon-separated list of usernames, depending on the aggregation type.

    for aggregations User(1) and User and host(3).

    Otherwise, a null value.

    (error) Unavailable
    ugnUser Groupugnstring

    Name of user group

    for aggregations Usergroup(4).

    Otherwise, an empty string.

    (warning) Only for aggregation Usergroup(4)
    hnHoststring

    Hostname for aggregations Host(2) and User and host(3).

    Otherwise, a

    hnstring

    semicolon-separated list of

    hostnames.

    (tick)Yes
    hgnHost GroupstringName of host group
    lsnstringLicense server name.
    for aggregations Hostgroup(5).

    Otherwise, an empty string.

    (warning) Only for aggregation Hostgroup(4)
    lsidLicense Server IDintegerInternal License Statistics identification of the license server hosting the feature.
    (error) Unavailable
    lsnLicense ServerstringName of the license server hosting the feature.(tick)Yes
    fidFeature IDintegerInternal License Statistics identification of the feature.
    (error) Unavailable
    fnsFeature NamefnsstringFeature name.
    (tick)Yes
    fvFeature VersionstringFeature version.(tick)Yes
    ftypestringFeature type.Feature TypeenumerationSee feature type descriptions for details.(tick)Yes
    musageMax UsagemusagefloatMaximum usage of licenses in relation to total license number of licenses in the period, expressed in percentages.(tick)Yes
    huHours UsedfloatHours used.
    muintegerMaximum licenses used count for given date.
    hbfloatHours borrowed.
    mbintegerMaximum licenses borrowed count for a given date.
    codeinteger

    Error code if success equals false, null otherwise.

    totalCountintegerTotal number of rows returned.

    Obtaining information about usage per user for a license server

    You can easily fetch metrics about usage per user for a single license server by sending the following HTTP request.

    Code Block
    languagejs
    firstline1
     GET /api/v1/report/license-server/${licenseServerId}/usage-per-user/${returnType}?sd=${startDate}&ed=${endDate}&grat=${granularity}$(additional parameters, as needed)

    where $ indicates a variable value that you can replace with a value that best suits your needs. The possible parameters are described below.

    ...

    ID of a single license server or "all" if information about all license servers is requested.

    ...

    Specifies granularity of the returned data, which can be one of the following:

    • Quarter - 2
    • Month - 3
    • Week - 4
    • Day - 5
    • Hour - 6

    ...

    Specifies aggregation type of the returned data. Aggregation type can be one of the following:

    • Username - 1
    • Hostname - 2
    • Username and hostname - 3
    • Usergroup - 4
    • Hostgroup - 5

    By default data is aggregated by username and hostname.

    ...

    No

    ...

    Specifies the name of the report that will be displayed once the report has been exported to PDF or XLSX. For CSV and JSON formats this parameter will be ignored.
    Note: If you don't pass this parameter, it will be generated automatically for PDF and XLSX types. If provided, it cannot be left empty.

    ...

    Applies filtering license usage data on all fields. (See this section for more format-specific information.)

    ...

    Specifies field visibility settings. (See the this section for more information.)

    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.

    ...

    Specifies the field by which you want to order your data records. The field name can be one of the following:

    fud | un | ugn | hn | hgn | lsn | fns | fv | ftype | musage | hu | mu | hb | mb

    (See this section for more field-specific information.)

    If orderBy is provided, orderDirection is mandatory.

    ...

    Cumulative time used by all licenses of the feature in the period, in hours.(tick)Yes
    muMax UsedintegerMaximum number of licenses of the feature used in the period.
    (tick)Yes
    hbHours BorrowedfloatCumulative time of all license borrows of the feature in the period, in hours.
    (tick)Yes
    mbMax BorrowedintegerMaximum number of licenses of the feature borrowed in the period.
    (tick)Yes

    Note that the order in the table is the default order of the columns in the exported file.