Get cluster metrics
GET /database/clusters/{clusterId}/metrics
Returns all metrics for the given cluster
Authorizations
Parameters
Path Parameters
A cluster ID.
Responses
200
A cluster metrics request response.
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
object
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Single vector result as defined here: https://prometheus.io/docs/prometheus/latest/querying/api/#scalars
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
object
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
object
Range of metric vectors over a specific time period.
Example
{
"uniqueData": {
"now": [
"dailyAvg": [
[
"dailyMin": [
[
"dailyMax": [
[
"storage": {
"bytesUsed": {
"now": [
"hourlyAvg": [
[
"hourlyMin": [
[
"hourlyMax": [
[
"memoryUsed": {
"now": [
"hourlyAvg": [
[
"hourlyMin": [
[
"hourlyMax": [
[
"objectsUsed": {
"now": [
"hourlyAvg": [
[
"hourlyMin": [
[
"hourlyMax": [
[
"throughput": {
"objectSizeAvg": {
"now": [
"hourlyAvg": [
[
"dailyAvg": [
[
"readTps": {
"now": [
"hourlyAvg": [
[
"hourlyMin": [
[
"hourlyMax": [
[
"dailyAvg": [
[
"dailyMin": [
[
"dailyMax": [
[
"writeTps": {
"now": [
"hourlyAvg": [
[
"hourlyMin": [
[
"hourlyMax": [
[
"dailyAvg": [
[
"dailyMin": [
[
"dailyMax": [
[
"readTpsSuccess": {
"hourlyAvg": [
[
"writeTpsSuccess": {
"hourlyAvg": [
[
"batchReadTpsSuccess": {
"hourlyAvg": [
[
"batchWriteTpsSuccess": {
"hourlyAvg": [
[
"queryTpsSuccess": {
"hourlyAvg": [
[
"latency": {
"read": {
"quantile95": {
"minutely": [
[
"quantile99": {
"minutely": [
[
"quantile999": {
"minutely": [
[
"write": {
"quantile95": {
"minutely": [
[
"quantile99": {
"minutely": [
[
"quantile999": {
"minutely": [
[
"transactions": {
"readCount": {
"daily": [
[
"writeCount": {
"daily": [
[
"errors": {
"keyBusy": {
"hourly": [
[
"generationFail": {
"hourly": [
[
"timeout": {
"hourly": [
[
"recordSize": {
"hourly": [
[
400
Invalid input
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:401
Access token is missing or invalid
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:403
Permission denied
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:404
Resource not found
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.
Example
Example:500
Internal Server Error
Response Headers
ID uniquely identifying the request/response cycle.
Response Schema
RFC 9457 Problem Details for HTTP APIs. Provides a standardized format for conveying error details in HTTP responses.
object
URN-based error type identifiers following the pattern: urn:aerospike:errors:{category}:{specific}
Resource information (cluster, database, organization, etc.) is provided in the ProblemDetails context field, not in the URN.
A short, human-readable summary of the problem type
The HTTP status code
A human-readable explanation specific to this occurrence
A URI reference that identifies the specific occurrence
Context for resource-related errors (not-found, already-exists)
object
Type of resource (e.g., cluster, database, organization)
Identifier of the resource
Structured context for validation errors
object
JSON Pointer paths to missing required fields
Details about invalid field values
object
JSON Pointer path to the invalid field
URN identifying the specific validation error type
An optional human-readable description of the validation error
object
Developer-friendly message explaining the error. Deprecated: Use ‘detail’ field instead.