Get Deployment APM Resource Info
Get info about an APM Resource belonging to a given Deployment.
Path parameters
-
Identifier for the Deployment
-
User-specified RefId for the Resource (or '_main' if there is only one).
Query parameters
-
Whether to include the full cluster metadata in the response - can be large per cluster and also include credentials.
Default value is
false
. -
Whether to include the full current and pending plan information in the response - can be large per cluster.
Default value is
true
. -
Whether to include with the current and pending plan information the attempt log - can be very large per cluster.
Default value is
false
. -
Whether to include with the current and pending plan information the plan history- can be very large per cluster.
Default value is
false
. -
If showing plans, whether to show values that are left at their default value (less readable but more informative).
Default value is
false
. -
Whether to show cluster settings in the response.
Default value is
false
. -
If set (defaults to false) then removes the transient section from all child resources, making it safe to reapply via an update
Default value is
false
.
Responses
-
Standard response.
Hide response attributes Show response attributes object
-
The locally-unique user-specified id of a Resource
-
The Elasticsearch cluster that this resource depends on.
-
The randomly-generated id of a Resource
-
The region where this resource exists
-
Info for the resource.
Hide info attributes Show info attributes object
-
The id of the APM
-
The name of the APM
-
Information about the specified Elasticsearch cluster.
Hide elasticsearch_cluster attributes Show elasticsearch_cluster attributes object
-
The Elasticsearch cluster Id
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
-
The id of the deployment that this APM Server belongs to.
-
Whether the APM is healthy or not (one or more of the info subsections will have healthy: false)
-
APM status
Values are
initializing
,stopping
,stopped
,rebooting
,restarting
,reconfiguring
, orstarted
. -
Information about current, pending, and past APM Server plans.
Hide plan_info attributes Show plan_info attributes object
-
Whether the plan situation is healthy (if unhealthy, means the last plan attempt failed)
-
Information about the APM Server plan.
Hide current attributes Show current attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the APM) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for the APM Server.
Hide plan attributes Show plan attributes object
-
Defines the topology of the APM Server nodes. For example, the number or capacity of the nodes, and where you can allocate the nodes.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
number of zones in which nodes will be placed
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and APM Server settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The plan control configuration options for the APM Server.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB)
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan
Value is
forced
.
-
-
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
Information about the APM Server plan.
Hide pending attributes Show pending attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the APM) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for the APM Server.
Hide plan attributes Show plan attributes object
-
Defines the topology of the APM Server nodes. For example, the number or capacity of the nodes, and where you can allocate the nodes.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
number of zones in which nodes will be placed
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and APM Server settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The plan control configuration options for the APM Server.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB)
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan
Value is
forced
.
-
-
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
Information about the APM Server plan.
Hide history attributes Show history attributes object
-
A UUID for each plan attempt
-
A human readable name for each plan attempt, only populated when retrieving plan histories
-
Either the plan ended successfully, or is not yet completed (and no errors have occurred)
-
When this plan attempt (ie to apply the plan to the APM) started (ISO format in UTC)
-
If this plan completed or failed (ie is not pending), when the attempt ended (ISO format in UTC)
-
If this plan is not current or pending, when the plan was no longer active (ISO format in UTC)
-
The plan for the APM Server.
Hide plan attributes Show plan attributes object
-
Defines the topology of the APM Server nodes. For example, the number or capacity of the nodes, and where you can allocate the nodes.
Hide cluster_topology attributes Show cluster_topology attributes object
-
Controls the allocation of this topology element as well as allowed sizes and node_types. It needs to match the id of an existing instance configuration.
-
The version of the Instance Configuration Id. If it is unset, the meaning depends on read vs writes. For deployment reads, it is equivalent to version 0 (or the IC is unversioned); for deployment creates and deployment template use, it is equivalent to 'the latest version'; and for deployment updates, it is equivalent to 'retain the current version'.
-
Measured by the amount of a resource. The final cluster size is calculated using multipliers from the topology instance configuration.
-
number of zones in which nodes will be placed
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
-
The configuration options for the APM Server.
Hide apm attributes Show apm attributes object
-
The version of the Apm cluster (must be one of the ECE supported versions, and won't work unless it matches the APM version. Leave blank to auto-detect version.)
-
A docker URI that allows overriding of the default docker image specified for this version
-
A structure that defines a curated subset of the APM Server settings. TIP: To define the complete set of APM Server setting, use
ApmSystemSettings
withuser_settings_override_
anduser_settings_
.Hide system_settings attributes Show system_settings attributes object
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the password must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the account within APM - defaults to a system account that always exists (if specified, the username must also be specified). Note that this field is never returned from the API, it is write only.
-
Optionally override the secret token within APM - defaults to the previously existing secretToken
-
Optionally enable debug mode for APM servers - defaults false
-
-
An arbitrary JSON object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_yaml' is allowed), provided the parameters are on the allowlist and not on the denylist. (This field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary YAML object allowing (non-admin) cluster owners to set their parameters (only one of this and 'user_settings_json' is allowed), provided the parameters are on the allowlist and not on the denylist. (These field together with 'user_settings_override*' and 'system_settings' defines the total set of Apm settings)
-
An arbitrary JSON object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_yaml' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
An arbitrary YAML object allowing ECE admins owners to set clusters' parameters (only one of this and 'user_settings_override_json' is allowed), ie in addition to the documented 'system_settings'. (This field together with 'system_settings' and 'user_settings*' defines the total set of Apm settings)
-
-
Defines the configuration parameters that control how the plan is applied. For example, the Elasticsearch cluster topology and APM Server settings.
Hide transient attributes Show transient attributes object
-
The options for performing a plan change. Specify only one property each time. The default is
grow_and_shrink
.Hide strategy attributes Show strategy attributes object
-
Performs inline, rolling configuration changes that mutate existing containers. TIP: This is the fastest way to update a plan, but can fail for complex plan changes, such as topology changes. Also, this is less safe for configuration changes that leave a cluster in a non running state. NOTE: When you perform a major version upgrade, and 'group_by' is set to 'pass:macros[all]';, rolling is required.
Hide rolling attributes Show rolling attributes object
-
Specifies the grouping attribute to use when rolling several instances. Instances that share the same value for the provided attribute key are rolled together as a unit. Examples that make sense to use are '__all__' (roll all instances as a single unit), 'logical_zone_name' (roll instances by zone), '__name__' (roll one instance at a time, the default if not specified). Note that '__all__' is required when performing a major version upgrade
-
Whether we allow changing the capacity of instances (default false). This is currently implemented by stopping, re-creating then starting the affected instance on its associated allocator when performing the changes. NOTES: This requires a round-trip through the allocation infrastructure of the active constructor, as it has to reserve the target capacity without over-committing
-
Whether to skip attempting to do a synced flush on the filesystem of the container (default: false), which is less safe but may be required if the container is unhealthy
-
The time, in seconds, to wait for shards that show no progress of initializing before rolling the next group (default: 10 minutes)
-
-
A strategy that creates instances with the new plan, migrates data from the old instances, then shuts down the old instances.
GrowShrinkStrategyConfig
is safer than 'rolling' and ensures single node availability during a plan change, but can be a lot slower on larger clusters. -
A strategy that creates new Elasticsearch instances, Kibana instances, and APM Servers with the new plan, then migrates the node data to minimize the amount of spare capacity.
-
A strategy that lets constructor choose the most optimal way to execute the plan.
-
-
The plan control configuration options for the APM Server.
Hide plan_configuration attributes Show plan_configuration attributes object
-
The total timeout in seconds after which the plan is cancelled even if it is not complete. Defaults to 4x the max memory capacity per node (in MB)
-
This timeout determines how long to give a cluster after it responds to API calls before performing actual operations on it. It defaults to 5s
-
If true (default false), does not clear the maintenance flag (which prevents its API from being accessed except by the constructor) on new instances added until after a snapshot has been restored, otherwise, the maintenance flag is cleared once the new instances successfully join the new cluster
-
Set to 'forced' to force a reboot as part of the upgrade plan
Value is
forced
.
-
-
-
-
Information about a step in a plan.
Hide plan_attempt_log attributes Show plan_attempt_log attributes object
-
ID of current step
-
When the step started (ISO format in UTC)
-
When the step completed (ISO format in UTC)
-
The duration of the step in MS
-
The status of the step (success, warning, error - warning means something didn't go as expected but it was not serious enough to abort the plan)
Values are
success
,warning
,error
, orpending
. -
Current stage that the step is in
Values are
starting
,completed
, orin_progress
. -
Human readable summaries of the step, including messages for each stage of the step
The log message from a specified stage of an executed step in a plan.
Hide info_log attributes Show info_log attributes object
-
Timestamp marking on info log of step
-
Time in milliseconds since previous log message
-
Stage that info log message takes place in
Values are
starting
,completed
, orin_progress
. -
Human readable log message
-
A map with details for the log about what happened during the step execution. Keys and values for are always both strings, representing the name of the detail and its value, respectively.
-
The failure type, in case the step failed
-
-
-
Information describing the source that facilitated the plans current state
Hide source attributes Show source attributes object
-
The service where the change originated from
-
The type of plan change that was initiated
-
The time the change was initiated
-
The user that requested the change
-
The admin user that requested the change
-
The host addresses of the user that originated the change
-
-
Information about a warning from a plan.
-
Information about an error during a plan attempt.
Hide error attributes Show error attributes object
-
Timestamp marking on info log of step
-
Human readable error message
-
A map with details regarding the error. Both the keys and values are always strings, representing the name of the detail and its value, respectively.
-
The failure type
-
-
-
-
Information about the public and internal state, and the configuration settings of an Elasticsearch cluster.
Hide metadata attributes Show metadata attributes object
-
The resource version number of the cluster metadata
-
The most recent time the cluster metadata was changed (ISO format in UTC)
-
The DNS name of the cluster endpoint, if available
-
The full URL to access this deployment resource
-
The DNS name of the cluster endpoint derived from the deployment alias, if available
-
The full aliased URL to access this deployment resource
-
The cloud ID, an encoded string that provides other Elastic services with the necessary information to connect to this Elasticsearch and Kibana (only present if both exist)
-
An unstructured JSON representation of the public and internal state (can be filtered out via URL parameter). The contents and structure of the
raw
field can change at any time. -
The ports that allow communication with the cluster using various protocols.
Hide ports attributes Show ports attributes object
-
A list of the URLs to access services that the resource provides at this time. Note that if the service is not running or has not started yet, the URL to access it won't be available
A URL to access the service of a resource
-
-
The topology for Elasticsearch clusters, multiple Kibana instances, or multiple APM Servers. The
ClusterTopologyInfo
also includes the instances and containers, and where they are located.Hide topology attributes Show topology attributes object
-
Whether the cluster topology is healthy (ie all instances are started and the services they run - ie elasticsearch - are available
-
Information about each Kibana instance and APM Server in the Elasticsearch cluster.
Hide instances attributes Show instances attributes object
-
The name of the instance in Elastic Cloud
-
Information about a configuration that creates a Kibana instance or APM Server.
Hide instance_configuration attributes Show instance_configuration attributes object
-
The id of the configuration used to create the instance
-
The name of the configuration used to create the instance
-
If the IC is configuration controlled, this field is the version either being read back (reads return the latest IC unless specified by the 'config_version' URL param), or the version to update. Cannot be used in creates. For unversioned IC reads it is left empty.
-
The resource type of the instance configuration
Values are
memory
orstorage
.
-
-
The version of the service that the instance is running (eg Elasticsearch or Kibana), if available
-
Whether the instance is healthy (ie started and running)
-
Whether the container has started (does not tell you anything about the service -ie Elasticsearch- running inside the container)
-
Whether the service launched inside the container -ie Elasticsearch- is actually running
-
Whether the service is is maintenance mode (meaning that the proxy is not routing external traffic to it)
-
The zone in which this instance is being allocated
-
The id of the allocator on which this instance is running (if the container is started or starting)
-
Information about the specific instances memory capacity and its usage
Hide memory attributes Show memory attributes object
-
The memory capacity in MB of the instance
-
The planned memory capacity in MB of the instance (only shown when an override is present)
-
The % memory pressure of Elasticsearch JVM heap space if available (60-75% consider increasing capacity, >75% can incur significant performance and stability issues)
-
The % memory pressure of the instance Docker container (if available)
-
-
Information about the use and storage capacity of a Kibana instance or APM Server.
Hide disk attributes Show disk attributes object
-
If known, the amount of total disk space available to the container in MB
-
The amount of disk space being used by the service in MB
-
The storage multiplier originally defined to calculate disk space.
-
-
List of roles assigned to the service running in the instance. Currently only populated for Elasticsearch, with possible values: master,data,ingest,ml
-
A list of the node roles assigned to the service running in the instance. Currently populated only for Elasticsearch.
Values are
master
,ingest
,ml
,data_hot
,data_content
,data_warm
,data_cold
,data_frozen
,remote_cluster_client
,transform
, orvoting_only
. -
Instance overrides
-
-
-
External resources related to the APM
-
A map of application-specific operations (which map to 'operationId's in the Swagger API) to metadata about that operation
-
The settings for building this APM cluster
-
The region that this APM belongs to. Only populated in SaaS or federated ECE.
-
The mode APM is operating in.
Values are
standalone
ormanaged
.
-
-
-
The Deployment specified by {deployment_id} cannot be found. (code:
deployments.deployment_not_found
)Hide headers attribute Show headers attribute
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
-
We have failed you. (code:
deployments.deployment_resource_no_longer_exists
)Hide headers attribute Show headers attribute
Hide response attribute Show response attribute object
-
A list of errors that occurred in the failing request
Hide errors attributes Show errors attributes object
-
curl \
--request GET 'https://api.elastic-cloud.com/api/v1/deployments/{deployment_id}/apm/{ref_id}'