---
title: Default data path
description: Describes what AutoOps detects and surfaces with the Default data path insight: Elasticsearch is storing data under the default directory inside the installation path.
url: https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch/default_data_path
products:
  - Elastic Cloud Enterprise
  - Elastic Cloud on Kubernetes
  - Elasticsearch
applies_to:
  - Elastic Cloud on Kubernetes: Generally available
  - Elastic Cloud Enterprise: Generally available
  - Self-managed Elastic deployments: Generally available
---

# Default data path
Elasticsearch is storing data under the default directory inside the installation path. Upgrades, reinstalls, or removing the install tree can delete indices on that path.
<note>
  For a complete list of insights, refer to [AutoOps insights](https://docs-v3-preview.elastic.dev/elastic/autoops-insights/tree/main/elasticsearch).
</note>


## Insight details


| Field     | Value                       |
|-----------|-----------------------------|
| Component | Elasticsearch               |
| Severity  | Low                         |
| Scope     | Cluster                     |
| Domains   | configuration, disk-storage |


## Example: What you might see in AutoOps

The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.

### The data path is set to default


#### What was detected

The data path is the default location: logs-prod-000045.

#### Recommendations

<note>
  AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
</note>

<dropdown title="Set custom data path">
  **Condition**: Always shown for this insight.The default data path can be removed during upgrades. Configure a custom `path.data` location, migrate data if needed, then dismiss this insight.
</dropdown>


#### Background and impact

By default, Elasticsearch stores index data in a subdirectory of the installation directory. Upgrades, reinstalls, or removing the install tree can delete data on that path. Production deployments should use a dedicated data directory on storage that survives software upgrades.

## Guide

[Node settings](https://docs-v3-preview.elastic.dev/elastic/elasticsearch/tree/main/reference/elasticsearch/configuration-reference/node-settings#data-path)