You can use the cluster repositories metering API to retrieve repositories metering information in a cluster Technical preview
This API exposes monotonically non-decreasing counters and it’s expected that clients would durably store the information needed to compute aggregations over a period of time. Additionally, the information exposed by this API is volatile, meaning that it won’t be present after node restarts.
Path parameters
-
Comma-separated list of node IDs or names used to limit returned information. All the nodes selective options are explained here.
GET /_nodes/{node_id}/_repositories_metering
curl \
-X GET http://api.example.com/_nodes/{node_id}/_repositories_metering
Response examples (200)
{
"_nodes": {
"failures": [
{
"type": "string",
"reason": "string",
"stack_trace": "string",
"caused_by": {},
"root_cause": [
{}
],
"suppressed": [
{}
]
}
],
"total": 42.0,
"successful": 42.0,
"failed": 42.0
},
"cluster_name": "string",
"nodes": {
"additionalProperty1": {
"repository_name": "string",
"repository_type": "string",
"repository_location": {
"base_path": "string",
"container": "string",
"bucket": "string"
},
"repository_ephemeral_id": "string",
"": 42.0,
"archived": true,
"cluster_version": 42.0,
"request_counts": {
"GetBlobProperties": 42.0,
"GetBlob": 42.0,
"ListBlobs": 42.0,
"PutBlob": 42.0,
"PutBlock": 42.0,
"PutBlockList": 42.0,
"GetObject": 42.0,
"ListObjects": 42.0,
"InsertObject": 42.0,
"PutObject": 42.0,
"PutMultipartObject": 42.0
}
},
"additionalProperty2": {
"repository_name": "string",
"repository_type": "string",
"repository_location": {
"base_path": "string",
"container": "string",
"bucket": "string"
},
"repository_ephemeral_id": "string",
"": 42.0,
"archived": true,
"cluster_version": 42.0,
"request_counts": {
"GetBlobProperties": 42.0,
"GetBlob": 42.0,
"ListBlobs": 42.0,
"PutBlob": 42.0,
"PutBlock": 42.0,
"PutBlockList": 42.0,
"GetObject": 42.0,
"ListObjects": 42.0,
"InsertObject": 42.0,
"PutObject": 42.0,
"PutMultipartObject": 42.0
}
}
}
}