Capture diagnostics for an Elasticsearch or Kibana resource
Retrieves a diagnostic bundle from an active cluster. To successfully retrieve a diagnostic bundle, the cluster must be responsive.
Path parameters
-
Identifier for the Deployment
-
The kind of resource (one of elasticsearch or kibana).
-
User-specified RefId for the Resource (or '_main' if there is only one).
Query parameters
-
mode string
Capture mode - whether to obtain all the diagnostics data or the lightweight, essential-only subset of it. Applicable only to Elasticsearch, ignored for any other components which have just one capture mode implemented.
Values are
full
orlight
. Default value isFull
.
Responses
-
The diagnostic bundle as a zip file
-
- The Deployment specified by {deployment_id} cannot be found. (code:
deployments.deployment_not_found
) - The Resource specified by {ref_id} cannot be found. (code:
deployments.deployment_resource_not_found
)
- The Deployment specified by {deployment_id} cannot be found. (code:
-
The diagnostics cannot be generated because the cluster is either stopped or initializing. (code:
clusters.cluster_plan_state_error
)
POST /deployments/{deployment_id}/{resource_kind}/{ref_id}/diagnostics/_capture
curl \
-X POST https://{{hostname}}/api/v1/deployments/{deployment_id}/{resource_kind}/{ref_id}/diagnostics/_capture
Response examples (200)
string
Response examples (404)
# Headers
x-cloud-error-codes: deployments.deployment_not_found
# Payload
{
"errors": [
{
"code": "string",
"message": "string",
"fields": [
"string"
]
}
]
}
Response examples (412)
# Headers
x-cloud-error-codes: clusters.cluster_plan_state_error
# Payload
{
"errors": [
{
"code": "string",
"message": "string",
"fields": [
"string"
]
}
]
}