Skip to content

Update ece-ech-stack-monitoring.md bubble up limitation on service provider, version, region. #2894

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Sep 15, 2025
Merged

Update ece-ech-stack-monitoring.md bubble up limitation on service provider, version, region. #2894

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
aa7cc26
Update ece-ech-stack-monitoring.md
predogma Sep 10, 2025
7d32ef9
Update deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitorin…
predogma Sep 15, 2025
dd1076c
Merge branch 'main' into predogma-patch-1
georgewallace Sep 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,10 @@ Elastic manages the installation and configuration of the monitoring agent for y
- Enabling logging and monitoring increases the resource consumption of the deployment. For production systems, we recommend sizing deployments with logging and monitoring enabled to at least 4 GB of RAM on each {{es}} instance.
- Enabling logging and monitoring can trigger a plan change on your deployment. You can monitor the plan change progress from the deployment's **Activity** page.

:::{tip}
The monitoring deployment and production deployment must be on the same major version, cloud provider, and region.
:::

To enable monitoring on your deployment:

:::{include} /deploy-manage/_snippets/find-manage-deployment-ech-and-ece.md
Expand Down Expand Up @@ -147,8 +151,8 @@ The `*` indicates that we also index the archived files of each type of log.
Check the respective product documentation for more information about the logging capabilities of each product.

## Restrictions and limitations [restrictions-monitoring]

* The monitoring deployment and production deployment must be on the same major version, cloud provider, and region.
* To avoid compatibility issues, ensure your monitoring cluster and production cluster run on the same {{stack}} version. Monitoring clusters that use 9.x do work with production clusters that use the latest release of 8.x, but this setup should only occur when upgrading clusters to the same version.
* $$$cross-region-monitor$$$ Monitoring across regions is not supported. If you need to move your existing monitoring to the same region, you can do a reindex or create a new deployment and select the snapshot from the old deployment.
* The logs shipped to a monitoring cluster use an ILM managed data stream (`elastic-cloud-logs-<version>`). If you need to delete indices due to space, do not delete the current `is_write_enabled: true` index.
* When sending metrics to a dedicated monitoring deployment, the graph for IO Operations Rate(/s) is blank. This is due to the fact that this graph actually contains metrics from of all of the virtualized resources from the provider.
* When sending metrics to a dedicated monitoring deployment, the graph for IO Operations Rate(/s) is blank. This is due to the fact that this graph actually contains metrics from of all of the virtualized resources from the provider.
Loading