Get cluster repositories metering
- GET /_nodes/{node_id}/_repositories_metering
Get repositories metering information for a cluster. This API exposes monotonically non-decreasing counters and it is 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 will not be present after node restarts.
Required authorization
- Cluster privileges monitor manage
Response
-
nodesmap string to objectrequired -
Contains repositories metering information for the nodes selected by the request.
-
<string>object -
repository_ephemeral_idstringrequired -
An identifier that changes every time the repository is updated.
-
repository_started_atnumberrequired -
Time the repository was created or updated. Recorded in milliseconds since the Unix Epoch.
-
repository_stopped_atnumber -
Time the repository was deleted or updated. Recorded in milliseconds since the Unix Epoch.
-
archivedbooleanrequired -
A flag that tells whether or not this object has been archived. When a repository is closed or updated the repository metering information is archived and kept for a certain period of time. This allows retrieving the repository metering information of previous repository instantiations.
-
cluster_versionnumber -
The cluster state version when this object was archived, this field can be used as a logical timestamp to delete all the archived metrics up to an observed version. This field is only present for archived repository metering information objects. The main purpose of this field is to avoid possible race conditions during repository metering information deletions, i.e. deleting archived repositories metering information that we haven’t observed yet.