Skip to content

Add links to config resources #1340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
May 1, 2025
Merged

Add links to config resources #1340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
268385f
Update configure-elasticsearch.md
shainaraskas May 1, 2025
12747a6
clarify
shainaraskas May 1, 2025
65c72a6
Merge branch 'main' into shainaraskas-patch-2
shainaraskas May 1, 2025
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
2 changes: 1 addition & 1 deletion deploy-manage/deploy/self-managed/_snippets/config-file-format.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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:
Expand Down
2 changes: 1 addition & 1 deletion deploy-manage/deploy/self-managed/_snippets/env-var-setting-subs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -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}
Expand Down
6 changes: 3 additions & 3 deletions deploy-manage/deploy/self-managed/configure-elasticsearch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down Expand Up @@ -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.
* [](/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.
Loading