From 4d5f9ec9d58f36a1eb9b86cca6b84873d121753b Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 19 Dec 2025 16:12:41 -0500 Subject: [PATCH 1/3] changes for 684 --- .../monitor/autoops/cc-connect-self-managed-to-autoops.md | 4 +++- deploy-manage/monitor/autoops/ec-autoops-faq.md | 4 ++++ 2 files changed, 7 insertions(+), 1 deletion(-) diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index 8206fe4232..dcc1603434 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -107,7 +107,9 @@ macOS is not a supported platform for installing {{agent}} to connect to AutoOps ::: :::{important} -Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install an agent even if you already have an existing one for other purposes. +Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes. + +You only need to install the agent once per cluster. ::: To learn more about how AutoOps securely gathers data from your cluster, refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#data-gathering). diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index f4884c73f0..6947d0b93e 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -41,6 +41,7 @@ Whether you are using AutoOps in your [{{ech}} deployment](/deploy-manage/monito * [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech) * [Can I use macOS to set up AutoOps for my self-managed clusters?](#macos-install) * [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) +* [Do I have to install {{agent}} separately for each node in my cluster?](#agent-nodes) **Collected metrics and data in AutoOps for self-managed clusters** * [Where are metrics stored in AutoOps for self-managed clusters?](#sm-autoops-metrics-storage) @@ -116,6 +117,9 @@ $$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable t : For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). +$$$agent-nodes$$$ **Do I have to install {{agent}} separately for each node in my cluster?** +: No, to run AutoOps in your self-managed environment, you only have to install the agent once per cluster. + ### Collected metrics and data in AutoOps for self-managed clusters $$$sm-autoops-metrics-storage$$$ **Where are metrics stored in AutoOps for self-managed clusters?** From 570eef69ddb5602d42432fc268317043512df39e Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 19 Dec 2025 16:21:34 -0500 Subject: [PATCH 2/3] update phrasing --- .../monitor/autoops/cc-connect-self-managed-to-autoops.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index dcc1603434..8500a76c30 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -107,7 +107,7 @@ macOS is not a supported platform for installing {{agent}} to connect to AutoOps ::: :::{important} -Using AutoOps for your ECE, ECK, and self-managed clusters requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes. +Every cluster that you want to connect requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes. You only need to install the agent once per cluster. ::: @@ -305,7 +305,7 @@ By default, each cluster has a name made up of a string of characters, but you c To connect more clusters, repeat the steps to [connect to AutoOps](#connect-to-autoops). -You can use the same installation command to connect multiple clusters, but each cluster needs a separate, dedicated {{agent}}. +You can use the same installation command to connect multiple clusters, but each cluster needs a separate, dedicated {{agent}}. You only need to install the agent once per cluster. ### Disconnect a cluster From 6c60a093d1199b0c8bbe5346dd1205ec12c789dd Mon Sep 17 00:00:00 2001 From: wajihaparvez Date: Fri, 19 Dec 2025 17:47:21 -0500 Subject: [PATCH 3/3] changes for 3008 --- .../autoops/cc-connect-self-managed-to-autoops.md | 10 +++++----- deploy-manage/monitor/autoops/ec-autoops-faq.md | 4 ++++ 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md index 8500a76c30..a47a98d0c0 100644 --- a/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md +++ b/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md @@ -107,7 +107,7 @@ macOS is not a supported platform for installing {{agent}} to connect to AutoOps ::: :::{important} -Every cluster that you want to connect requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes. +Each cluster that you want to connect requires a new, dedicated {{agent}}. You must install the agent even if you already have an existing one for other purposes. You only need to install the agent once per cluster. ::: @@ -267,9 +267,7 @@ Complete the following steps to run the command: It might take a few minutes for your cluster details to be validated and the first metrics to be shipped to AutoOps. -If the connection is unsuccessful, an error message is displayed with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors). - -Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). +If the connection is unsuccessful, an error message is displayed with a possible reason for the failure and recommended next steps. For a list of these errors, refer to [Potential errors](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md#potential-errors). Sometimes, an exact reason for the failure cannot be determined. In this case, explore [additional resources](/troubleshoot/index.md#troubleshoot-additional-resources) or [contact us](/troubleshoot/index.md#contact-us). To uninstall the agent, refer to [](/solutions/security/configure-elastic-defend/uninstall-elastic-agent.md). @@ -305,7 +303,9 @@ By default, each cluster has a name made up of a string of characters, but you c To connect more clusters, repeat the steps to [connect to AutoOps](#connect-to-autoops). -You can use the same installation command to connect multiple clusters, but each cluster needs a separate, dedicated {{agent}}. You only need to install the agent once per cluster. +Or, if you don't need to change any of your [configuration settings](#configure-agent) for the additional clusters, you can skip ahead and reuse the same installation command to connect them. + +Remember that you must run the command to install a separate, dedicated {{agent}} for each cluster. You only need to install the agent once per cluster. ### Disconnect a cluster diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 6947d0b93e..5f918994fd 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -42,6 +42,7 @@ Whether you are using AutoOps in your [{{ech}} deployment](/deploy-manage/monito * [Can I use macOS to set up AutoOps for my self-managed clusters?](#macos-install) * [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) * [Do I have to install {{agent}} separately for each node in my cluster?](#agent-nodes) +* [Do I have to go through the whole installation wizard to connect more clusters?](#connect-more-clusters) **Collected metrics and data in AutoOps for self-managed clusters** * [Where are metrics stored in AutoOps for self-managed clusters?](#sm-autoops-metrics-storage) @@ -120,6 +121,9 @@ $$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable t $$$agent-nodes$$$ **Do I have to install {{agent}} separately for each node in my cluster?** : No, to run AutoOps in your self-managed environment, you only have to install the agent once per cluster. +$$$connect-more-clusters$$$Do I have to go through the whole installation wizard to connect more clusters? +: Not necessarily. Refer to [Connect additional clusters](../autoops/cc-connect-self-managed-to-autoops.md#connect-additional-clusters) for more information. + ### Collected metrics and data in AutoOps for self-managed clusters $$$sm-autoops-metrics-storage$$$ **Where are metrics stored in AutoOps for self-managed clusters?**