From 268385f46ba06ee98f9fdbc1d748867a88fbf9be Mon Sep 17 00:00:00 2001 From: shainaraskas <58563081+shainaraskas@users.noreply.github.com> Date: Thu, 1 May 2025 15:36:33 -0400 Subject: [PATCH 1/2] Update configure-elasticsearch.md --- .../deploy/self-managed/configure-elasticsearch.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/deploy/self-managed/configure-elasticsearch.md b/deploy-manage/deploy/self-managed/configure-elasticsearch.md index bf74c397bd..21b735ea23 100644 --- a/deploy-manage/deploy/self-managed/configure-elasticsearch.md +++ b/deploy-manage/deploy/self-managed/configure-elasticsearch.md @@ -32,8 +32,8 @@ For a list of settings that must be configured before using your cluster in prod {{es}} has three configuration files: * `elasticsearch.yml` for configuring {{es}} -* `jvm.options` for configuring {{es}} JVM settings -* `log4j2.properties` for configuring {{es}} logging +* `jvm.options` for configuring {{es}} [JVM settings](elasticsearch://reference/elasticsearch/jvm-settings.md) +* `log4j2.properties` for configuring [{{es}} logging](/deploy-manage/monitor/logging-configuration/elasticsearch-log4j-configuration-self-managed.md) These files are located in the config directory, whose default location depends on whether the installation is from an archive distribution (`tar.gz` or `zip`) or a package distribution (Debian or RPM packages). @@ -92,4 +92,4 @@ Refer to the following documentation to learn how to perform key configuration t * [](/deploy-manage/manage-connectors.md): Manage connection information between Elastic and third-party systems. * [](/deploy-manage/remote-clusters.md): Enable communication between {{es}} clusters to support [cross-cluster replication](/deploy-manage/tools/cross-cluster-replication.md) and [cross-cluster search](/solutions/search/cross-cluster-search.md). * [](/deploy-manage/maintenance/add-and-remove-elasticsearch-nodes.md): Learn how to add or remove nodes to change the size and capacity of your cluster. -* [](/deploy-manage/production-guidance.md): Review tips and guidance that you can use to design a production environment that matches your workloads, policies, and deployment needs. \ No newline at end of file +* [](/deploy-manage/production-guidance.md): Review tips and guidance that you can use to design a production environment that matches your workloads, policies, and deployment needs. From 12747a64327c87ebdbbda6f17464273601962aa3 Mon Sep 17 00:00:00 2001 From: shainaraskas Date: Thu, 1 May 2025 15:38:06 -0400 Subject: [PATCH 2/2] clarify --- .../deploy/self-managed/_snippets/config-file-format.md | 2 +- .../deploy/self-managed/_snippets/env-var-setting-subs.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/self-managed/_snippets/config-file-format.md b/deploy-manage/deploy/self-managed/_snippets/config-file-format.md index 91d8e2189a..cf9c06a6dd 100644 --- a/deploy-manage/deploy/self-managed/_snippets/config-file-format.md +++ b/deploy-manage/deploy/self-managed/_snippets/config-file-format.md @@ -1,4 +1,4 @@ -The configuration format is [YAML](https://yaml.org/). Here is an example of changing the path of the data and logs directories in {{es}}: +The `elasticsearch.yml` configuration format is [YAML](https://yaml.org/). Here is an example of changing the path of the data and logs directories in {{es}}: ```yaml path: diff --git a/deploy-manage/deploy/self-managed/_snippets/env-var-setting-subs.md b/deploy-manage/deploy/self-managed/_snippets/env-var-setting-subs.md index 032c6d0ded..58ac800ff8 100644 --- a/deploy-manage/deploy/self-managed/_snippets/env-var-setting-subs.md +++ b/deploy-manage/deploy/self-managed/_snippets/env-var-setting-subs.md @@ -1,4 +1,4 @@ -Environment variables referenced with the `${...}` notation within the configuration file will be replaced with the value of the environment variable. For example: +Environment variables referenced with the `${...}` notation within the `elasticsearch.yml` configuration file will be replaced with the value of the environment variable. For example: ```yaml node.name: ${HOSTNAME}