diff --git a/deploy-manage/_snippets/autoops-cc-payment-faq.md b/deploy-manage/_snippets/autoops-cc-payment-faq.md index 056f7650ee..7cd6cf68c7 100644 --- a/deploy-manage/_snippets/autoops-cc-payment-faq.md +++ b/deploy-manage/_snippets/autoops-cc-payment-faq.md @@ -1 +1 @@ -Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions) and self-managed free trials. \ No newline at end of file +Using AutoOps for self-managed clusters (ECE, ECK, or standalone) on-premise or in private cloud environments through Cloud Connect is included with [self-managed Enterprise licenses](https://www.elastic.co/subscriptions) and self-managed free trials. This does not consume ECU. \ No newline at end of file diff --git a/deploy-manage/cloud-organization/billing/billing-faq.md b/deploy-manage/cloud-organization/billing/billing-faq.md index 54491c9896..2f2906c62e 100644 --- a/deploy-manage/cloud-organization/billing/billing-faq.md +++ b/deploy-manage/cloud-organization/billing/billing-faq.md @@ -101,6 +101,9 @@ $$$faq-refund$$$Can I get a refund? $$$billing-cc-additional-payment$$$Does Cloud Connect require additional payment? : Each [cloud connected service](/deploy-manage/cloud-connect.md) has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page. + :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +::: + $$$faq-included$$$What is included in my paid {{ech}} deployment? : All subscription tiers for {{ech}} include the following free allowance: diff --git a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md index f2ab1b6897..eb43be2f13 100644 --- a/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md +++ b/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md @@ -23,5 +23,7 @@ In this section, you'll find the following information: * How to [connect your self-managed cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) * How to [connect your local development cluster to AutoOps](/deploy-manage/monitor/autoops/cc-connect-local-dev-to-autoops.md) * How to [manage users of your connected clusters](/deploy-manage/monitor/autoops/cc-manage-users.md) -* [FAQs](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md) about AutoOps for your clusters -* A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter \ No newline at end of file +* A [troubleshooting guide](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md) to help you with any issues you may encounter + +:::{tip} +Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md#questions-about-autoops-for-self-managed-clusters) for answers to commonly asked questions about AutoOps for self-managed clusters. \ No newline at end of file diff --git a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md b/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md deleted file mode 100644 index d1e1929e2e..0000000000 --- a/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md +++ /dev/null @@ -1,105 +0,0 @@ ---- -applies_to: - deployment: - self: - ece: - eck: -navigation_title: FAQ -products: - - id: cloud-kubernetes - - id: cloud-enterprise ---- - -# AutoOps for self-managed clusters FAQ - -Find answers to your questions about AutoOps for ECE, ECK, and self-managed clusters. - -**General questions** -* [Why should I use AutoOps for my clusters?](#why-autoops) -* [Does this feature require additional payment?](#additional-payment) -* [Is there an added cost for shipping metrics data to {{ecloud}}?](#autoops-metrics-cost) -* [Which versions of {{es}} does AutoOps support?](#es-versions) -* [Which deployment types can be connected to AutoOps through Cloud Connect?](#deployment-types) - -**Questions about setting up** -* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech) -* [Can I use AutoOps for my clusters if my environment is air-gapped?](#autoops-air-gapped) -* [Can I use macOS to install {{agent}} for this feature?](#macos-install) -* [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) - -**Questions about collected metrics and data** -* [Where are AutoOps metrics stored?](#autoops-metrics-storage) -* [What information does {{agent}} extract from my cluster?](#extracted-info) -* [How does AutoOps gather data from my cluster and ensure its security?](#data-gathering) - -## General questions -$$$why-autoops$$$ **Why should I use AutoOps for my clusters?** -: AutoOps simplifies the operation of your {{es}} clusters by providing real-time monitoring, performance insights, and issue detection. It helps you identify and resolve problems like ingestion bottlenecks and unbalanced shards, reducing manual effort and preventing performance issues. - -$$$additional-payment$$$ **Does this feature require additional payment?** -: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md -::: - -$$$autoops-metrics-cost$$$ **Is there an added cost for shipping metrics data to {{ecloud}}?** -: Elastic does not charge extra for this service, but your cloud service provider (CSP) might. When sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs will be determined by your agreement with that CSP. - - You can [choose the CSP region where your data is stored](#autoops-metrics-storage). - -$$$es-versions$$$ **Which versions of {{es}} does AutoOps support?** -: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). - -$$$deployment-types$$$ **Which deployment types can be connected to AutoOps through Cloud Connect?** -: You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment. - -## Questions about setting up -$$$cc-autoops-ech$$$ **Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?** -: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md -::: - -$$$autoops-air-gapped$$$ **Can I use AutoOps for my clusters if my environment is air-gapped?** -: Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. - -$$$macos-install$$$ **Can I use macOS to install {{agent}} for this feature?** -: macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. - -$$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?** -: You may need to define an IP address if your organization’s settings will block the agent from sending out data. - - To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. - -: For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). - -## Questions about collected metrics and data -$$$autoops-metrics-storage$$$ **Where are AutoOps metrics stored?** -: You can choose where to store your metrics from the following AWS regions: - - :::{include} ../_snippets/autoops-cc-regions.md - ::: - -$$$extracted-info$$$ **What information does {{agent}} extract from my cluster?** -: {{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: - - | API | Description | Collected data | - | --- | --- | --- | - | [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information | - | [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats | - | [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations | - | [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards | - | [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings | - | [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases | - | [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings | - | [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | - | [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | - | [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | - -$$$data-gathering$$$ **How does AutoOps gather data from my cluster and ensure its security?** -: AutoOps gathers data from your cluster using two protocols: - * **HTTP request**: Made to our Cloud Connected API to register your cluster with {{ecloud}} and gather registration-related data. - * **OpenTelemetry Protocol (OTLP)**: Used to gather all other operational data. - - Each channel is authenticated through an API key or token to ensure your data's security. The following table offers more details: - - | Protocol | Data extracted | Port | Authentication method | - | --- | --- | --- | --- | - | HTTP | Basic cluster information from the `/` endpoint

License information from the `/_license` endpoint | **443**: standard HTTPS port | Uses an {{ecloud}} API key which is limited for use with Cloud Connect only. | - | OTLP over HTTP | Operational information | **443**: standard HTTPS port | Uses an AutoOps token which is functionally equivalent to an API key. | 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 748ed7710d..a2ed401f7d 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 @@ -105,7 +105,7 @@ Select one of the following methods to install {{agent}}: 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. ::: -To learn more about how AutoOps securely gathers data from your cluster, refer to our [FAQ](/deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md#data-gathering). +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). ### Configure agent diff --git a/deploy-manage/monitor/autoops/ec-autoops-faq.md b/deploy-manage/monitor/autoops/ec-autoops-faq.md index 5415513754..91802c2a6b 100644 --- a/deploy-manage/monitor/autoops/ec-autoops-faq.md +++ b/deploy-manage/monitor/autoops/ec-autoops-faq.md @@ -17,37 +17,139 @@ navigation_title: FAQ # AutoOps FAQ [ec-autoops-faq] -Here are answers to some common questions about AutoOps. +Whether you are using AutoOps in your [{{ech}} deployment](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), [{{serverless-short}} project](/deploy-manage/monitor/autoops/autoops-for-serverless.md), or [self-managed cluster](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md), find answers to some common questions about it on this page. -$$$faq-what-is-autoops$$$What does AutoOps do? -: AutoOps for {{es}} significantly simplifies cluster management with performance recommendations, resource utilization and cost insights, real-time issue detection and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps recommends operational and monitoring insights that deliver savings in administration time and hardware costs. +**General AutoOps questions** +* [What does AutoOps do?](#what-is-autoops) +* [Where is AutoOps available?](#autoops-deployment-types) +* [Why can't I see AutoOps in some deployments and projects?](#cant-see-autoops) +* [How is AutoOps licensed?](#autoops-license) +* [Does AutoOps monitor the entire {{stack}}?](#autoops-monitoring) +* [Can AutoOps automatically resolve issues?](#autoops-issue-resolution) +* [Which versions of {{es}} are supported in AutoOps for {{ech}} and self-managed clusters?](#autoops-supported-versions) +* [How long does Elastic retain AutoOps data?](#autoops-data-retention) +* [Where are AutoOps metrics stored, and does AutoOps affect customer ECU usage?](#autoops-metrics-storage) +* [Has AutoOps replaced Stack Monitoring?](#autoops-vs-stack-monitoring) -$$$faq-autoops-deployment-types$$$Is AutoOps available in all types of deployments? -: In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and [{{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md), and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md). +**Questions about AutoOps for self-managed clusters** +* [Does AutoOps for self-managed clusters incur additional costs?](#additional-payment) +* [Does shipping metrics data to {{ecloud}} incur additional costs?](#autoops-metrics-cost) +* [Which deployment types can be connected to AutoOps through Cloud Connect?](#deployment-types) -$$$faq-autoops-regions$$$Why can't I see AutoOps in some deployments? -: AutoOps is rolling out in phases across CSPs and [regions](ec-autoops-regions.md), so you may not see it if your deployment is in a region where AutoOps is not available yet. +**Setting up AutoOps for self-managed clusters** +* [Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?](#cc-autoops-ech) +* [Can I use AutoOps for my clusters if my environment is air-gapped?](#autoops-air-gapped) +* [Can I use macOS to install {{agent}} for this feature?](#macos-install) +* [Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?](#elastic-ip-address) -$$$faq-autoops-monitoring$$$Does AutoOps monitor the entire {{stack}}? -: AutoOps is currently limited to {{es}} (not {{kib}}, Logstash, and Beats). +**Collected metrics and data in AutoOps for self-managed clusters** +* [Where are metrics stored in AutoOps for self-managed clusters?](#autoops-metrics-storage) +* [What information does {{agent}} gather from my cluster?](#extracted-info) +* [How does AutoOps gather data from my cluster and ensure its security?](#data-gathering) +* [Can I view the data gathered by {{agent}}?](#data-viewing-config) -$$$faq-autoops-supported-versions$$$What versions of {{es}} are supported for {{ech}}? -: AutoOps supports {{es}} versions according to the [supported {{stack}} versions](https://www.elastic.co/support/eol). +## General AutoOps questions -$$$faq-autoops-license$$$How is AutoOps currently licensed? -: Using AutoOps for {{ech}} deployments is available at all [subscription tiers](https://www.elastic.co/subscriptions/cloud). +$$$what-is-autoops$$$**What does AutoOps do?** +: AutoOps for {{es}} simplifies cluster management by providing performance recommendations, resource utilization and cost insights, real-time issue detection, and resolution paths. By analyzing hundreds of {{es}} metrics, your configuration, and usage patterns, AutoOps provides operational and monitoring recommendations that reduce administration time and hardware costs. + +$$$autoops-deployment-types$$$**Where is AutoOps available?** +: In the [regions](ec-autoops-regions.md) where it has been rolled out, AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) and can be set up for [ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through [Cloud Connect](/deploy-manage/cloud-connect.md). + +$$$cant-see-autoops$$$**Why can't I see AutoOps in some deployments and projects?** +AutoOps is rolling out in phases across CSPs and [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), so you may not see it if your deployment or project is in a region where AutoOps is not available yet. AutoOps is currently not available in Azure and GCP. + +$$$autoops-license$$$**How is AutoOps licensed?** +: For {{ech}} deployments and {{serverless-short}} projects, AutoOps is available to {{ecloud}} customers at all subscription levels at no additional cost, and it does not consume ECU. :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md ::: -$$$faq-autoops-issue-resolution$$$Can AutoOps currently automatically resolve issues? -: AutoOps only analyzes metrics, and is a read-only solution. +$$$autoops-monitoring$$$**Does AutoOps monitor the entire {{stack}}?** +: AutoOps is currently limited to {{es}} (not {{kib}}, Logstash, or Beats). + +$$$autoops-issue-resolution$$$**Can AutoOps automatically resolve issues?** +: AutoOps only analyzes metrics and is a read-only solution. + +$$$autoops-supported-versions$$$**Which versions of {{es}} are supported in AutoOps for {{ech}} and self-managed clusters?** +: AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol) (7.17.x and above). + +$$$autoops-data-retention$$$**How long does Elastic retain AutoOps data?** +: AutoOps has a 10 day retention period. + +$$$autoops-metrics-storage$$$**Where are AutoOps metrics stored, and does AutoOps affect customer ECU usage?** +: AutoOps metrics are stored internally within the Elastic infrastructure, not on customer deployments. Using AutoOps does not consume customer ECU. + +$$$autoops-vs-stack-monitoring$$$**Has AutoOps replaced Stack Monitoring?** +: Currently, AutoOps has many of the same features as Stack Monitoring as well as several new ones. However, it only provides insights on {{es}} and analyzes metrics, not logs. Read more in [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). + +## Questions about AutoOps for self-managed clusters + +$$$additional-payment$$$ **Does AutoOps for self-managed clusters incur additional costs?** +: :::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md +::: + +$$$autoops-metrics-cost$$$ **Does shipping metrics data to {{ecloud}} incur additional costs?** +: Elastic does not charge extra for this service, but your cloud service provider (CSP) might. When sending metrics data from your cluster in a CSP region to {{ecloud}}, shipping costs are determined by your agreement with that CSP. + + You can [choose the CSP region where your data is stored](/deploy-manage/monitor/autoops/ec-autoops-regions.md#autoops-for-self-managed-clusters-regions). + +$$$deployment-types$$$ **Which deployment types can be connected to AutoOps through Cloud Connect?** +: You can connect to AutoOps on a standalone {{stack}}, ECE ({{ece}}), or ECK ({{eck}}) deployment, both on-premise and in private cloud environments. + +### Setting up AutoOps for self-managed clusters + +$$$cc-autoops-ech$$$ **Can I use Cloud Connect to connect my {{ech}} clusters to AutoOps?** +: :::{include} /deploy-manage/_snippets/autoops-cc-ech-faq.md +::: + +$$$autoops-air-gapped$$$ **Can I use AutoOps for my clusters if my environment is air-gapped?** +: Not at this time. AutoOps is currently only available as a cloud service and you need an internet connection to send metrics to {{ecloud}}. For air-gapped environments, we plan to offer a locally deployable version in the future. + +$$$macos-install$$$ **Can I use macOS to install {{agent}} for this feature?** +: macOS is not a supported platform for installing {{agent}} and connecting your clusters to AutoOps. + +$$$elastic-ip-address$$$ **Do I have to define an Elastic IP address to enable the agent to send data to {{ecloud}}?** +: You may need to define an IP address if your organization’s settings will block the agent from sending out data. + + To enable IP ranges, {{ecloud}} offers a selection of static IP addresses. All traffic directed to {{ecloud}} deployments, whether originating from the public internet, your private cloud network through the public internet, or your on-premise network through the public internet utilizes Ingress Static IPs as the network destination. + +: For more information, refer to [](/deploy-manage/security/elastic-cloud-static-ips.md). + +### Collected metrics and data in AutoOps for self-managed clusters + +$$$autoops-metrics-storage$$$ **Where are metrics stored in AutoOps for self-managed clusters?** +: You can choose where to store your metrics from the following AWS regions: + + :::{include} ../_snippets/autoops-cc-regions.md + ::: + +$$$extracted-info$$$ **What information does {{agent}} gather from my cluster?** +: {{agent}} only extracts and sends cluster metrics to {{ecloud}}, not the underlying data within your cluster. The following metrics are collected: + + | API | Description | Collected data | + | --- | --- | --- | + | [_cat/shards](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-shards) | Returns detailed information about the shards within the cluster | Shard states, node allocation, index names, sizes, and replica information | + | [_nodes/stats](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-nodes-stats) | Retrieves statistics from cluster nodes including JVM, OS, process, and transport metrics | CPU usage, memory utilization, thread pools, file system stats | + | [_cluster/settings](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-settings) | Returns the settings configured for the cluster | Persistent and transient settings such as cluster-wide configurations | + | [_cluster/health](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-health) | Provides information about the overall health of the cluster | Status (green/yellow/red), number of nodes, number of shards | + | [_cat/template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cat-templates) | Lists all index templates in the cluster | Template names, patterns, and basic settings | + | [_index_template](/manage-data/data-store/templates.md) | Retrieves composable index templates | Index settings, mappings, and aliases | + | [_component_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-cluster-get-component-template) | Fetches component templates used for building index templates | Metadata for re-usable mappings and settings | + | [_tasks](https://www.elastic.co/docs/api/doc/elasticsearch/group/endpoint-tasks) | Displays information about currently running tasks on the cluster | Task descriptions, start times, running nodes, and execution details | + | [_template](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-get-template) | Retrieves legacy index templates | Similar to composable index templates but in older format | + | [_resolve/index/*](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-indices-resolve-index) | Resolves index, data stream, and alias names to their current definitions | Mappings between names and underlying data objects | -$$$faq-autoops-data-retention$$$How long does Elastic retain AutoOps data? -: Currently, AutoOps has a 10 day retention period for all {{ech}} customers. +$$$data-gathering$$$ **How does AutoOps gather data from my cluster and ensure its security?** +: AutoOps gathers data from your cluster using two protocols: + * **HTTP request**: Made to our Cloud Connected API to register your cluster with {{ecloud}} and gather registration-related data. + * **OpenTelemetry Protocol (OTLP)**: Used to gather all other operational data. -$$$faq-autoops-metrics-storage$$$Where are AutoOps metrics stored, and does AutoOps affect customer ECU usage? -: AutoOps metrics are stored internally within the Elastic infrastructure, not on customer deployments. So using AutoOps does not consume customer ECU. + Each channel is authenticated using an API key or token to ensure your data's security. The following table offers more details: -$$$faq-autoops-vs-stack-monitoring$$$Has AutoOps replaced Stack Monitoring? -: Currently, AutoOps has many of the same features as Stack Monitoring as well as several new ones. However, it only provides insights on {{es}} and analyzes metrics, but not logs. Read more in [](/deploy-manage/monitor/autoops-vs-stack-monitoring.md). + | Protocol | Data extracted | Port | Authentication method | + | --- | --- | --- | --- | + | HTTP | Basic cluster information from the `/` endpoint

License information from the `/_license` endpoint | **443**: standard HTTPS port | Uses an {{ecloud}} API key which is limited for use with Cloud Connect only. | + | OTLP over HTTP | Operational information | **443**: standard HTTPS port | Uses an AutoOps token which is functionally equivalent to an API key. | +$$$data-viewing-config$$$**Can I view the data gathered by {{agent}}?** +: You can use the `autoops_es_debug.yaml` config file to export and review a sample of the data gathered from your cluster and sent to Elastic Cloud. \ No newline at end of file diff --git a/deploy-manage/toc.yml b/deploy-manage/toc.yml index b2cfacc4e4..8b4773bbf1 100644 --- a/deploy-manage/toc.yml +++ b/deploy-manage/toc.yml @@ -675,7 +675,6 @@ toc: - file: monitor/autoops/cc-connect-self-managed-to-autoops.md - file: monitor/autoops/cc-connect-local-dev-to-autoops.md - file: monitor/autoops/cc-manage-users.md - - file: monitor/autoops/cc-cloud-connect-autoops-faq.md - file: monitor/autoops/cc-cloud-connect-autoops-troubleshooting.md - file: monitor/autoops/ec-autoops-regions.md - file: monitor/autoops/ec-autoops-events.md diff --git a/redirects.yml b/redirects.yml index f81cb02bc9..432357bc47 100644 --- a/redirects.yml +++ b/redirects.yml @@ -582,5 +582,8 @@ redirects: # Remote cluster settings moved to reference: https://github.com/elastic/docs-content/issues/579 'deploy-manage/remote-clusters/remote-clusters-settings.md': 'elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md' +# Related to https://github.com/elastic/docs-content/pull/3685 + 'deploy-manage/monitor/autoops/cc-cloud-connect-autoops-faq.md': 'deploy-manage/monitor/autoops/ec-autoops-faq.md' +