You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 30 Next »

The Current Feature Usage API delivers metrics that License Statistics collects from the monitored license server. This endpoint is used to fetch license usage metrics specific to the Current Feature Usage, allowing you to monitor statistics for the currently selected feature on the license server of your choosing.

Obtaining information about current feature usage

If you want to fetch metrics about current feature usage for a given feature, use the following URL request template.

GET /api/v1/report/feature/${featureId}/current-usage/${returnType}

where $ indicates a variable value that you can replace with a value that best suits your needs and the possible parameters are as follows:

Parameter
Required
Type
Description
${featureId}Yesinteger/stringSpecifies ID of the feature for which you want to view current usage.
${returnType}YesstringSpecifies the format in which the data should be returned. The format can be one of the following: json, csv, xls or pdf.
fieldsVisibility Nojson/string

Specifies field visibility settings, for example:

{ "uid": "1", "un": "1", "hn": "1", "lus": "1", "lco": "1", "tu": "1", "lbe": "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.

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

Applies filtering license usage data on all fields.

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

[
    {
        "type": "string",
        "field": "${un | hn | lco | lbe}",
        "value": "${value}"
    }
]

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

[
    {
        "type": "numeric",
        "comparison": "${gt | lt | eq}",
        "field": "${uid, lus}",
        "value": "${value}"
    }
]


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:

uid, un, hn, lus, lco, tu, lbe

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

orderDirectionNostringDetermines whether the sorting results will be displayed in an ascending (ASC) or a descending (DESC) order.

 The following code block shows an example result of a successful request:

{
    success: ${success},
    msg: ${message},
    data: [{
        "uid": ${userId},
        "un": ${userName},
        "hn": ${hostName},
        "lus": ${licensesUsed},
        "lco": ${checkoutTime},
        "tu": ${licensesUsed},
        "lbe": ${borrowExpire},
        "uil": ${ldapUser}
    }],
    "code": ${errorCode},
    "totalCount": ${totalCount}
}

where the response fields can be explained as follows: 

Field
Type
Description

uid

integer

User ID.

un

string

Username.

hn

string

Hostname.

lus

integer

Total number of licenses used by user on host.

lco

string

Date when license was checked out. The date format is 'YYYY-MM-DD HH:MM'; for example, 2017-05-20 10:20.

lbe

string

Borrow expiration date. The date format is 'YYYY-MM-DD HH:MM'; for example, 2017-05-20 10:20.

Returns an empty string if does not apply.

uil

boolean

Indicates whether user details have been imported from an LDAP directory. Note that you cannot filter and order data by this field.

msg

string

Error message returned on failure.

success

boolean

Indicates whether the API request was successfully processed. 

codeinteger

Error code for an unsuccessful request.

totalCountinteger

Total number of all matching results.

 Example

Say you want to obtain information about current feature usage for feature 1 in CSV format. To fetch such metrics, enter a command similar to this one: 

curl -H "X-Auth-token: token" "http://yourdomain/api/v1/report/feature/1/current-usage/csv"

Obtaining information about feature usage during given day

If you want to fetch metrics about feature usage during any selected day, use the following URL template:

GET /api/v1/report/feature/${featureId}/usage/chart/json?day=${day}

where $ indicates a variable value that you can replace with a value that best suits your needs and the possible parameters are as follows:

Parameter
Required
Type
Description
${featureId}YesintegerID of the feature for which you want to get data.
${day} NostringDate in format 'YYYY-MM-DD'. Indicates day for which you want to gather data. If not provided, defaults to today.

The following code block shows an example result of a successful request:

 

{
    success: ${success},
    msg: ${message},
    data: [{
        "fid": ${featureId},
        "lud": ${dateAndTime},
        "ltc": ${totalCount},
        "lumax": ${licenseUsageMax},
        "lbmax": ${licensesBorrowedMax}
    }],
    "code": ${errorCode},
    "totalCount": ${totalCount}
}

where the response fields can be explained as follows:

Field
Type
Description
fidintegerFeature ID.
ludstringDate and time (adjusted to 5 minute intervals).
ltcintegerLicense total count.
lumaxintegerMaximum amount of used licenses.
lbmaxintegerMaximum amount of borrowed licenses.

msg

string

Error message returned on failure.

success

boolean

Indicates whether the API request was successfully processed. 

codeinteger

Error code for unsuccessful request.

totalCountinteger

Total number of all matching results.

  • No labels