|
2 | 2 | mapped_urls: |
3 | 3 | - https://www.elastic.co/guide/en/serverless/current/project-and-management-settings.html |
4 | 4 | - https://www.elastic.co/guide/en/serverless/current/elasticsearch-manage-project.html |
| 5 | + |
| 6 | +applies_to: |
| 7 | + serverless: |
5 | 8 | --- |
6 | 9 |
|
7 | 10 | # Project settings |
8 | 11 |
|
9 | | -% What needs to be done: Refine |
| 12 | +$$$elasticsearch-manage-project-search-power-settings$$$ |
| 13 | + |
| 14 | +{{serverless-full}} projects are fully managed and automatically scaled by Elastic. You have the option of {{es-serverless}}, {{observability}}, or {{elastic-sec}} for your project. |
| 15 | + |
| 16 | +Your project’s performance and general data retention are controlled by the **Search AI Lake settings**. To manage these settings: |
| 17 | + |
| 18 | +1. Navigate to [cloud.elastic.co](https://cloud.elastic.co/). |
| 19 | +2. Log in to your Elastic Cloud account. |
| 20 | +3. Select your project from the **Serverless projects** panel and click **Manage**. |
| 21 | + |
| 22 | +Additionally, there are [features and add-ons](#project-features-add-ons) available for security that you can configure. |
| 23 | + |
| 24 | +## Search AI Lake settings [elasticsearch-manage-project-search-ai-lake-settings] |
| 25 | + |
| 26 | +Once ingested, your data is stored in cost-efficient, general storage. A cache layer is available on top of the general storage for recent and frequently queried data that provides faster search speed. Data in this cache layer is considered **search-ready**. |
10 | 27 |
|
11 | | -% GitHub issue: https://github.com/elastic/docs-projects/issues/337 |
| 28 | +Together, these data storage layers form your project’s **Search AI Lake**. |
12 | 29 |
|
13 | | -% Use migrated content from existing pages that map to this page: |
| 30 | +The total volume of search-ready data is the sum of the following: |
14 | 31 |
|
15 | | -% - [ ] ./raw-migrated-files/docs-content/serverless/project-and-management-settings.md |
16 | | -% Notes: anything that isn't deduplicated from |
17 | | -% - [ ] ./raw-migrated-files/docs-content/serverless/elasticsearch-manage-project.md |
| 32 | +1. The volume of non-time series project data |
| 33 | +2. The volume of time series project data included in the Search Boost Window |
18 | 34 |
|
19 | | -% Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc): |
| 35 | +::::{note} |
| 36 | +Time series data refers to any document in standard indices or data streams that includes the `@timestamp` field. This field must be present for data to be subject to the Search Boost Window setting. |
20 | 37 |
|
21 | | -$$$elasticsearch-manage-project-search-ai-lake-settings$$$ |
| 38 | +:::: |
22 | 39 |
|
| 40 | +Each project type offers different settings that let you adjust the performance and volume of search-ready data, as well as the features available in your projects. |
| 41 | + |
| 42 | +The documentation in this section describes shared capabilities that are available in multiple solutions. These settings allow you to tune your project settings not all functionality as you would have with a self-managed deployment. |
23 | 43 | $$$elasticsearch-manage-project-search-power-settings$$$ |
24 | 44 |
|
25 | | -$$$project-features-add-ons$$$ |
| 45 | +| Setting | Description | Project Type | |
| 46 | +| :--- | :--- | :--- | |
| 47 | +| **Search Power** | Search Power controls the speed of searches against your data. With Search Power, you can improve search performance by adding more resources for querying, or you can reduce provisioned resources to cut costs. Choose from three Search Power settings:<br><br>**On-demand:** Autoscales based on data and search load, with a lower minimum baseline for resource use. This flexibility results in more variable query latency and reduced maximum throughput.<br><br>**Performant:** Delivers consistently low latency and autoscales to accommodate moderately high query throughput.<br><br>**High-throughput:** Optimized for high-throughput scenarios, autoscaling to maintain query latency even at very high query volumes.<br> | Elasticsearch | |
| 48 | +| **Search Boost Window** | Non-time series data is always considered search-ready. The **Search Boost Window** determines the volume of time series project data that will be considered search-ready.<br><br>Increasing the window results in a bigger portion of time series project data included in the total search-ready data volume.<br> | Elasticsearch | |
| 49 | +| **Data Retention** | Data retention policies determine how long your project data is retained.<br>In {{serverless-full}} data retention policies are configured through [data streams](../../../manage-data/lifecycle/data-stream.md) and you can specify different retention periods for specific data streams in your project.<br><br> {{elastic-sec}} has to additional configuration settings that can be configured to managed your data retention.<br><br>**Maximum data retention period**<br><br>When enabled, this setting determines the maximum length of time that data can be retained in any data streams of this project.<br><br>Editing this setting replaces the data retention set for all data streams of the project that have a longer data retention defined. Data older than the new maximum retention period that you set is permanently deleted.<br><br> **Default data retention period**<br><br>When enabled, this setting determines the default retention period that is automatically applied to all data streams in your project that do not have a custom retention period already set.<br> |Elasticsearch<br>Observability<br>Security | |
| 50 | +| **Project features** | Controls [feature tiers and add-on options](../../../deploy-manage/deploy/elastic-cloud/project-settings.md#project-features-add-ons) for your {{elastic-sec}} project. | Security | |
| 51 | + |
| 52 | +## Project features and add-ons [project-features-add-ons] |
| 53 | + |
| 54 | +```yaml {applies_to} |
| 55 | +serverless: |
| 56 | + security: |
| 57 | +``` |
| 58 | +
|
| 59 | +For {{elastic-sec}} projects, edit the **Project features** to select a feature tier and enable add-on options for specific use cases. |
| 60 | +
|
| 61 | +| Feature tier | Description and add-ons | |
| 62 | +| :--- | :--- | |
| 63 | +| **Security Analytics Essentials** | Standard security analytics, detections, investigations, and collaborations. Allows these add-ons:<br><br>* **Endpoint Protection Essentials**: endpoint protections with {{elastic-defend}}.<br>* **Cloud Protection Essentials**: Cloud native security features.<br> | |
| 64 | +| **Security Analytics Complete** | Everything in **Security Analytics Essentials*** plus advanced features such as entity analytics, threat intelligence, and more. Allows these add-ons:<br><br>* **Endpoint Protection Complete**: Everything in **Endpoint Protection Essentials** plus advanced endpoint detection and response features.<br>* **Cloud Protection Complete**: Everything in **Cloud Protection Essentials** plus advanced cloud security features.<br> | |
| 65 | +
|
| 66 | +### Downgrading the feature tier [elasticsearch-manage-project-downgrading-the-feature-tier] |
| 67 | +
|
| 68 | +When you downgrade your Security project features selection from **Security Analytics Complete** to **Security Analytics Essentials**, the following features become unavailable: |
| 69 | +
|
| 70 | +* All Entity Analytics features |
| 71 | +* The ability to use certain entity analytics-related integration packages, such as: |
| 72 | + * Data Exfiltration detection |
| 73 | + * Lateral Movement detection |
| 74 | + * Living off the Land Attack detection |
| 75 | +* Intelligence Indicators page |
| 76 | +* External rule action connectors |
| 77 | +* Case connectors |
| 78 | +* Endpoint response actions history |
| 79 | +* Endpoint host isolation exceptions |
| 80 | +* AI Assistant |
| 81 | +* Attack discovery |
26 | 82 |
|
27 | | -**This page is a work in progress.** The documentation team is working to combine content pulled from the following pages: |
| 83 | +And, the following data may be permanently deleted: |
28 | 84 |
|
29 | | -* [/raw-migrated-files/docs-content/serverless/project-and-management-settings.md](/raw-migrated-files/docs-content/serverless/project-and-management-settings.md) |
30 | | -* [/raw-migrated-files/docs-content/serverless/elasticsearch-manage-project.md](/raw-migrated-files/docs-content/serverless/elasticsearch-manage-project.md) |
| 85 | +* AI Assistant conversation history |
| 86 | +* AI Assistant settings |
| 87 | +* Entity Analytics user and host risk scores |
| 88 | +* Entity Analytics asset criticality information |
| 89 | +* Detection rule external connector settings |
| 90 | +* Detection rule response action settings |
0 commit comments