Get the list of cube caches on an specific cluster node
GET {{baseUrl}}/api/monitors/caches/cubes?clusterNode={{rd_nodeName}}&limit=5&projectIds={{projectId}}&state.loadedState=loaded
Get the list of cube caches.You obtain the authorization token needed to execute the request using POST /auth/login; you pass the authorization token in the request header. You can specify sorting criteria on fields: name, size, hitCount, lastUpdateTime, status, project, owner, you can also filter response data by projectId or status, you can set the offset and limit for pagination function, and provide the clusterNode, you will retrieve the cube caches infos
Request Params
Key | Datatype | Required | Description |
---|---|---|---|
clusterNode | string | (Required) Intelligence Server cluster node name | |
offset | number | Starting point within the collection of returned results. Used to control paging behavior. | |
limit | number | Maximum number of items returned for a single request. Used to control paging behavior. Use -1 for no limit. | |
projectIds | string | Project id collection which is used for filtering data, for example 'B19DEDCC11D4E0EFC000EB9495D0F6E2,A232EDCC11D4E0EFC000EB9495D0F6E2' | |
state.loadedState | string | Loaded state filter field which is used for filtering loaded cube cache, valid input: 'loaded' | |
sortBy | string | Specify sorting criteria, for example '+name,-size' means sorting name ascending and size descending | |
fields | string | Comma separated top-level field whitelist. This allows client to selectively retrieve part of the response model. If specified, extra filtering will be applied, and for top-level object (if root model is an array, each array element), only the listed fields will be kept in the response. e.g. "id,elements" means to keep only the "id" field and the whole "elements" array field, omitting all other fields of top-level response model. |
HEADERS
Key | Datatype | Required | Description |
---|---|---|---|
X-MSTR-AuthToken | string | (Required) Authorization token |