Access requirements
Required privileges
The Sever Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.
Note that administrators assigned a custom role must also have the administrative View all content privilege assigned to them to access the API directory as an administrator. Additonally, any custom roles that include a webhook-related privilege must also include the general Publish server-based layers content privilege.
Tokens
This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Server Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.
Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generate operation in the Portal Directory API. For security reasons, all POST requests made to the Server Administrator API must include a token in the request body.
Description
The resource for an individual usage report returns the parameters of the report.
A usage report is used to obtain ArcGIS Server usage data for specified resources during a given time period. It specifies the parameters for obtaining server usage data, time range (since from and to parameters), aggregation interval, and queries (which specify the metrics to be gathered for a collection of server resources, such as folders and services).
Request parameters
| Parameter | Description |
|---|---|
| The response format. The default response format is Values: |
Example usage
The following is a sample request URL used to access an individual usage report resource:
https://organization.example.com/<context>/admin/usagereports/1394219221008?f=pjsonJSON Response syntax
{
"reportname": [unique name or id of the report],
"since": [" LAST_DAY | LAST_WEEK | LAST_MONTH | LAST_YEAR | CUSTOM"],
"from" : [timestamp], //Optional, specified when "since" is CUSTOM
"to": [timestamp], //Optional, specified when “since” is CUSTOM
"aggregationInterval": [minutes], //Optional, aggregation interval in minutes
"queries": [
{
"resourceURIs": ["services/Map_bv_999.MapServer"], //Comma separated list of services and/or folders
"metrics": ["RequestCount"] // Comma separated list of metrics
}
],
"metadata": "This could be any String or JSON Object."
}JSON Response example
A usage report is represented in JSON format below.
{
"reportname": 1394219221008,
"since": "LAST_MONTH",
"queries": [
{
"resourceURIs": ["services/Map_bv_999.MapServer"],
"metrics": ["RequestCount"]
}
],
"metadata": "This could be any String or JSON Object. The next usage report below shows how this parameter is used be ArcGIS manager for storing report metadata."
}