You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deploy-manage/autoscaling/trained-model-autoscaling.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,8 +133,8 @@ In case of ingest-optimized deployments, we maximize the number of model allocat
133
133
| Level | Allocations | Threads | VCUs |
134
134
| --- | --- | --- | --- |
135
135
| Low | 0 to 2 dynamically | 1 | 0 to 16 dynamically |
136
-
| Medium |1 to 32 dynamically | 1 | 8 to 256 dynamically |
137
-
| High |1 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
136
+
| Medium |0 to 32 dynamically | 1 | 8 to 256 dynamically |
137
+
| High |0 to 512 for Search<br> 1 to 128 for Security and Observability<br> | 1 | 8 to 4096 for Search<br> 8 to 1024 for Security and Observability<br> |
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/add-plugins.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
-
navigation_title: Configure plugins and extensions
2
+
navigation_title: Add plugins and extensions
3
3
applies_to:
4
4
deployment:
5
5
ece:
6
6
---
7
7
8
-
# Add plugins and extensions [ece-adding-plugins]
8
+
# Add plugins and extensions in {{ece}} [ece-adding-plugins]
9
9
10
10
Plugins extend the core functionality of {{es}}. {{ece}} makes it easy to add plugins to your deployment by providing a number of plugins that work with your version of {{es}}. One advantage of these plugins is that you generally don’t have to worry about upgrading plugins when upgrading to a new {{es}} version, unless there are breaking changes. The plugins are upgraded along with the rest of your deployment.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/deploy-an-orchestrator.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,8 +2,9 @@
2
2
applies_to:
3
3
deployment:
4
4
ece: all
5
+
navigation_title: Deploy an orchestrator
5
6
---
6
-
# Deploy an orchestrator
7
+
# Deploy an {{ece}} orchestrator
7
8
8
9
{{ece}} (ECE) provides a centralized platform that allows organizations to run {{es}}, {{kib}}, and other {{stack}} components across multiple machines, whether in a private or public cloud, virtual machines, or your own premises.
Copy file name to clipboardExpand all lines: deploy-manage/deploy/cloud-enterprise/ece-configure-templates-index-management.md
+33-27Lines changed: 33 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,54 +13,60 @@ products:
13
13
14
14
If you create a deployment template that includes more than one data configuration, you must also specify how {{ece}} should manage indices for your users when they create their deployments. For time-series use cases such as logging, metrics, and APM, providing a template that enables index management ensures that data is being stored in the most cost-effective way possible as it ages.
15
15
16
-
In a template that creates a hot-warm architecture, you can use index curation to specify where new indices are created initially and where they are moved to later on. However, index curation has been deprecated in favor of index lifecycle management, which offers additional features and more fine-grained control over indices. For instance, using ILM you can enable automatic roll-over of index aliases to new indices when existing indices become too large or too old, and you can set indices to be deleted when they are no longer useful.
16
+
Configuring index management is part of the larger task of [creating deployment templates](ece-configuring-ece-create-templates.md) or editing them. The choices you make here determine which index management methods are available to your users when they create deployments.
17
17
18
+
You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both.
18
19
19
-
## Before you begin [ece_before_you_begin_4]
20
20
21
-
Configuring index management is part of the larger task of [creating deployment templates](ece-configuring-ece-create-templates.md) or editing them. The choices you make here determine which index management methods are available to your users when they create deployments.
21
+
## Available index management strategies
22
22
23
-
You should configure all index management methods that you want your users to be able to choose from when they create their deployments from your template. You can configure index curation, index lifecycle management, or both.
23
+
Index lifecycle management
24
+
: Uses the [{{ilm}}](/manage-data/lifecycle/index-lifecycle-management.md) feature of the {{stack}} that provides an integrated and streamlined way to manage time-based data, making it easier to follow best practices for managing your indices. Compared to index curation, ILM gives you more fine-grained control over the lifecycle of each index.
24
25
25
-
::::{note}
26
-
Index curation has been deprecated in favor of [index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md). For {{stack}} version 6.7 and later, any deployments using index curation will be prompted to [migrate to ILM](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md).
27
-
::::
26
+
Index curation (Curator) {applies_to}`stack: deprecated 6.7`
27
+
: Creates new indices on hot nodes first and moves them to warm nodes later on, based on the data views (formerly *index patterns*) you specify. Also manages replica counts for you, so that all shards of an index can fit on the right data nodes. Compared to index lifecycle management, index curation for time-based indices supports only one action, to move indices from nodes on one data configuration to another, but it is more straightforward to set up initially and all setup can be done directly from the Cloud UI.
28
+
29
+
If your users need to delete indices once they are no longer useful to them, they can run [Curator](curator://reference/index.md) on-premise to manage indices for {{es}} clusters hosted on {{ece}}.
28
30
29
-
## Steps [ece_steps_2]
31
+
::::{note}
32
+
Index curation has been deprecated in favor of [index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md). For {{stack}} version 6.7 and later, any deployments using index curation will be prompted to [migrate to ILM](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md).
33
+
::::
30
34
31
-
To configure index management when you create a deployment template:
32
35
33
-
1. On the **Index Management** page, configure the index curation methods that you want to be available when your users create deployments:
36
+
## Configure {{ilm}}
34
37
35
-
Index lifecycle management
36
-
: Uses the ILM feature of the {{stack}} that provides an integrated and streamlined way to manage time-based data, making it easier to follow best practices for managing your indices. Compared to index curation, ILM gives you more fine-grained control over the lifecycle of each index.
38
+
To configure {{ilm}} as part of your deployment template:
37
39
38
-
To configure index lifecycle management:
40
+
On the **Index Management** page, under **{{ilm}} ({{ilm-init}})**, specify the node attributes for your data configurations.
39
41
40
-
1. Specify the node attributes foryour data configurations.
42
+
Node attributes are simple key-value pairs, such as `node_type: hot`, `node_type: warm`, and `node_type: cold`. These node attributes add defining metadata attributes to each data configuration in your template that tell your users what they can be used for. What you define here should help guide your users when they set up their index lifecycle management policy in {{kib}}, such as a hot-warm policy.
41
43
42
-
Node attributes are simple key-value pairs, such as `node_type: hot`, `node_type: warm`, and `node_type: cold`. These node attributes add defining metadata attributes to each data configuration in your template that tell your users what they can be used for. What you define here should help guide your users when they set up their index lifecycle management policy in {{kib}}, such as a hot-warm policy.
44
+
For each data tier, specify an attribute key-value pair in the **Node attributes** field, with the key and value separated by a colon. Repeat this process until you have added all the node attributes that you want to be available to your users when they create an index lifecycle policy later on.
43
45
44
-
1. Specify an attribute key-value pair in the **Node attributes** field, with the key and value separated by a colon.
45
-
2. Repeat the previous step until you have added all the node attributes that you want to be available to your users when they create an index lifecycle policy later on.
46
+
## Configure index curation
47
+
```{applies_to}
48
+
stack: deprecated 6.7
49
+
```
46
50
51
+
::::{note}
52
+
Index curation has been deprecated in favor of [index lifecycle management](/manage-data/lifecycle/index-lifecycle-management.md). For {{stack}} version 6.7 and later, any deployments using index curation will be prompted to [migrate to ILM](/manage-data/lifecycle/index-lifecycle-management/migrate-index-management.md).
53
+
::::
47
54
48
-
Index curation
49
-
: Creates new indices on hot nodes first and moves them to warm nodes later on, based on the data views (formerly *index patterns*) you specify. Also manages replica counts for you, so that all shards of an index can fit on the right data nodes. Compared to index lifecycle management, index curation for time-based indices supports only one action, to move indices from nodes on one data configuration to another, but it is more straightforward to set up initially and all setup can be done directly from the Cloud UI.
55
+
To configure index curation as part of your deployment template:
50
56
51
-
If your user need to delete indices once they are no longer useful to them, they can run [Curator](curator://reference/index.md) on-premise to manage indices for {{es}} clusters hosted on {{ece}}.
57
+
1. On the **Index Management** page, under **Index curation**, click **Configure**.
52
58
53
-
To configure index curation:
59
+
2. Configure index curation by adding an index pattern:
54
60
55
-
1. Select the hot data configuration where new indices get created initially.
56
-
2. Select the warm nodes where older indices get moved to later on when they get curated.
57
-
3. Specify which indices get curated by including at least one data view.
61
+
1. Select the hot data configuration where new indices get created initially.
62
+
2. Select the warm nodes where older indices get moved to later on when they get curated.
63
+
3. Specify which indices get curated by including at least one index pattern.
58
64
59
-
By default, the pattern is `*`, which means that all indices get curated. For logging use cases, you could specify to curate only the `logstash-*`, `metricbeat-*`, or `filebeat-*` data views, for example.
65
+
By default, the pattern is `*`, which means that all indices get curated. For logging use cases, you could specify to curate only the `logstash-*`, `metricbeat-*`, or `filebeat-*` data views, for example.
60
66
61
-
4. Specify the time interval after which indices get curated.
67
+
4. Specify the time interval after which indices get curated.
62
68
63
-
2. Select **Next**.
69
+
## Next steps
64
70
65
71
After you have completed these steps, continue with [creating your deployment template](ece-configuring-ece-create-templates.md#ece-configuring-ece-create-templates-ui).
0 commit comments