Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
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
7 changes: 3 additions & 4 deletions deploy-manage/_snippets/autoops-callout-with-ech.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,4 @@
:::{admonition} Simplify monitoring with AutoOps
Use AutoOps in your {{ech}}, ECE, ECK, or self-managed deployments.

AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. For more information, refer to [](/deploy-manage/monitor/autoops.md).
::::
:applies_to: { ess:, ece:, eck:, self:, "serverless": "ga" }
AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths. Learn more about [](/deploy-manage/monitor/autoops.md).
:::
2 changes: 1 addition & 1 deletion deploy-manage/_snippets/autoops-cc-ech-faq.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@
This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.

For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md#ec-autoops-how-to-access) from the deployment overview page.
For {{ech}} deployments, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page.
5 changes: 4 additions & 1 deletion deploy-manage/deploy/elastic-cloud/serverless.md
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ products:
Serverless projects use the core components of the {{stack}}, such as {{es}} and {{kib}}, and are based on an architecture that decouples compute and storage. Search and indexing operations are separated, which offers high flexibility for scaling your workloads while ensuring a high level of performance.

:::{note}
There are differences between {{es-serverless}} and {{ech}}, for a list of differences between them, see [differences between {{ech}} and {{es-serverless}}](../elastic-cloud.md#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud).
There are differences between {{es-serverless}} and {{ech}}. Learn more in [Compare {{ech}} and {{es-serverless}}](../elastic-cloud.md#general-what-is-serverless-elastic-differences-between-serverless-projects-and-hosted-deployments-on-ecloud).
:::

## Get started
Expand Down Expand Up @@ -55,6 +55,9 @@ Afterwards, you can:
* **Data:** Choose the data you want to ingest and the method to ingest it. By default, data is stored indefinitely in your project, and you define the retention settings for your data streams.
* **Performance:** For granular control over costs and query performance against your project data, serverless projects come with a set of predefined settings you can edit.

:::{include} /deploy-manage/_snippets/autoops-callout-with-ech.md
:::

## Monitor serverless status [general-serverless-status]

Serverless projects run on cloud platforms, which may undergo changes in availability. When availability changes, Elastic makes sure to provide you with a current service status.
Expand Down
5 changes: 3 additions & 2 deletions deploy-manage/monitor.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Depending on your deployment type, you can use a variety of solutions for monito

You have several options for monitoring your cluster or deployment.

Use [AutoOps](/deploy-manage/monitor/autoops.md) in your {{ech}}, ECE, ECK, or self-managed deployments. AutoOps is a monitoring tool that simplifies cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.
Use [](/deploy-manage/monitor/autoops.md) to simplify cluster management through performance recommendations, resource utilization visibility, and real-time issue detection with resolution paths.

Alternatively, you can use [Stack Monitoring](/deploy-manage/monitor/stack-monitoring.md) to monitor logs and metrics across the {{stack}}.

Expand All @@ -47,7 +47,8 @@ deployment:

AutoOps diagnoses issues in {{es}} by analyzing hundreds of metrics, providing root-cause analysis and accurate resolution paths. With AutoOps, customers can prevent and resolve issues, cut down administration time, and optimize resource utilization.

In the [regions](/deploy-manage/monitor/autoops/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).
:::{include} /deploy-manage/monitor/_snippets/autoops-availability.md
:::

### Stack monitoring

Expand Down
1 change: 1 addition & 0 deletions deploy-manage/monitor/_snippets/autoops-availability.md
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
AutoOps is automatically available in [{{ech}} deployments](/deploy-manage/monitor/autoops/autoops-for-cloud-hosted.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) through Cloud Connect.
2 changes: 1 addition & 1 deletion deploy-manage/monitor/autoops-vs-stack-monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ You can store your Stack Monitoring logs and metrics in the following ways:
### Availability

#### AutoOps [ao-availability]
AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can [access](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) AutoOps from your hosted deployments.
AutoOps lives in {{ecloud}}, so you need to have an {{ecloud}} account to access it. Once logged in, you can access AutoOps from your [{{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md), [{{serverless-short}} projects](/deploy-manage/monitor/autoops/access-autoops-for-serverless.md), or [connect your self-managed clusters](/deploy-manage/monitor/autoops/cc-connect-self-managed-to-autoops.md) to it.

#### Stack Monitoring [sm-availability]
Once setup is complete, you can access the Stack Monitoring UI inside {{kib}}, where you can monitor all your {{stack}} components.
Expand Down
34 changes: 18 additions & 16 deletions deploy-manage/monitor/autoops.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,7 @@
:alt: Screenshot showing the Overview page in AutoOps
:::


## AutoOps key features [ec_autoops_key_features]
## Key features in AutoOps [ec_autoops_key_features]

* Real-time root-cause analysis for hundreds of issues.
* Accurate resolution paths and customized recommendations.
Expand All @@ -38,38 +37,41 @@
* Unbalanced loads between nodes.
* Indexing latency, rejections, search latency, high index/search queues, and slow queries.
* Resource utilization.
* Multi-deployment dashboard to quickly spot issues across all clusters.
* Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks.
* Coming soon: Long-term reports for sustained evaluation.

## Regions where AutoOps is available

Depending on your deployment type, AutoOps has been rolled out across various [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md). More regions and CSPs are coming soon.

## Additional capabilities [ec_additional_capabilities]
## Deployment types where AutoOps is available

* Multi-deployment dashboard to quickly spot issues across all clusters.
* Possibility to customize event triggers and connect to different notification services such as PagerDuty, Slack, MS Teams, and webhooks.
* Long-term reports for sustained evaluation. This feature is currently not available and will be rolled out shortly.
:::{include} /deploy-manage/monitor/_snippets/autoops-availability.md
:::

## AutoOps availability
AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.

Check notice on line 53 in deploy-manage/monitor/autoops.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.Wordiness: Consider using 'because' instead of 'since'.

In the [regions](/deploy-manage/monitor/autoops/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).
## How AutoOps is licensed

Check notice on line 55 in deploy-manage/monitor/autoops.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.Capitalization: 'How AutoOps is licensed' should use sentence-style capitalization.

AutoOps is currently not available for air-gapped environments since it is a cloud service and you need an internet connection to send metrics to {{ecloud}}. However, we plan to offer a locally deployable version in the future.
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.

Check notice on line 57 in deploy-manage/monitor/autoops.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.Acronyms: 'ECU' has no definition.
:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md
:::

## AutoOps retention period [ec_autoops_retention_period]
## How long AutoOps retains data [ec_autoops_retention_period]

AutoOps currently has a 10 day retention period.

## What AutoOps monitors [ec_autoops_scope]

Check notice on line 65 in deploy-manage/monitor/autoops.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.Capitalization: 'What AutoOps monitors [ec_autoops_scope]' should use sentence-style capitalization.

## AutoOps scope [ec_autoops_scope]

AutoOps currently monitors only {{es}}, not the entire {{stack}}. Any deployment information pertains solely to {{es}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future.
AutoOps currently only monitors {{es}}, not the entire {{stack}}. AutoOps is compatible with [supported {{es}} versions](https://www.elastic.co/support/eol)(7.17.x and above). We plan to expand AutoOps monitoring to the entire stack in the future.

## Section overview

In this section, you'll find the following information:

* How to [use AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md).
* How to [use AutoOps in your {{ech}} deployments](/deploy-manage/monitor/autoops/autoops-for-cloud-hosted.md).
* How to [use AutoOps in your {{serverless-full}} projects](/deploy-manage/monitor/autoops/autoops-for-serverless.md).
* How to [connect your ECE, ECK, or self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) to AutoOps.
* [Regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md) where AutoOps is available.
* What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).
* Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment.
* [Frequently asked questions](/deploy-manage/monitor/autoops/ec-autoops-faq.md) about AutoOps.
26 changes: 26 additions & 0 deletions deploy-manage/monitor/autoops/autoops-for-cloud-hosted.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
---
mapped_pages:
- https://www.elastic.co/guide/en/cloud/current/ec-autoops-how-to-access.html
applies_to:
deployment:
ess: all
products:
- id: cloud-hosted
navigation_title: For {{ech}}
---

# AutoOps for {{ech}}

Check notice on line 12 in deploy-manage/monitor/autoops/autoops-for-cloud-hosted.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.Capitalization: 'AutoOps for ***' should use sentence-style capitalization.

For [{{ech}}](/deploy-manage/deploy/elastic-cloud/cloud-hosted.md) deployments, AutoOps is set up and enabled automatically in all supported [regions](ec-autoops-regions.md#autoops-for-ech-regions). More regions are coming soon.

## Section overview

In this section, you'll find the following information:

Check notice on line 18 in deploy-manage/monitor/autoops/autoops-for-cloud-hosted.md

View workflow job for this annotation

GitHub Actions / vale

Elastic.FutureTense: 'you'll find' might be in future tense. Write in the present tense to describe the state of the product as it is now.

* How to [access AutoOps in your {{ech}} deployment](ec-autoops-how-to-access.md).
* Which [views](/deploy-manage/monitor/autoops/views.md) AutoOps offers to gain insight into your deployment.
* What [events](/deploy-manage/monitor/autoops/ec-autoops-events.md) are and how you can configure [event settings](/deploy-manage/monitor/autoops/ec-autoops-event-settings.md) and [notifications](/deploy-manage/monitor/autoops/ec-autoops-notifications-settings.md).

:::{tip}
Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md) for answers to frequently asked questions about AutoOps.
:::
5 changes: 4 additions & 1 deletion deploy-manage/monitor/autoops/autoops-for-serverless.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@ Let’s say you ingest 1TB of data into your Observability project.
* **Retention**: Given that 1GB retained per hour = [$0.018](https://www.elastic.co/pricing/serverless-observability) and assuming it took one hour to ingest 1TB of data, that 1TB will be billed 1.42GB for that slice of one hour (1TB/720 hours per month), which translates to $0.025. Each subsequent hour in that month will cost the same.
:::

## Coming soon
## Coming soon to AutoOps for Serverless

The following features are coming soon to AutoOps for {{serverless-short}}:

Expand All @@ -85,3 +85,6 @@ In this section, you'll find the following information:
* How to use the [Search tier view](search-tier-view-autoops-serverless.md) to see the impact of search performance on your use of search VCUs.
* How to use the [Search AI Lake view](search-ai-lake-view-autoops-serverless.md) to drill down into your storage-related usage.

:::{tip}
Refer to our [FAQ](/deploy-manage/monitor/autoops/ec-autoops-faq.md) for answers to frequently asked questions about AutoOps.
:::
Loading
Loading