Update logs.md (#4772)
Fixes an issue with the code. See https://github.com/opensearch-project/documentation-website/issues/4339 Signed-off-by: Heather Halter <HDHALTER@AMAZON.COM>
This commit is contained in:
parent
4d98febcbd
commit
61d6cb754b
|
@ -79,11 +79,11 @@ There are other ways to change log levels:
|
||||||
|
|
||||||
```properties
|
```properties
|
||||||
appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m%n
|
appender.console.layout.pattern = [%d{ISO8601}][%-5p][%-25c{1.}] [%node_name]%marker %m%n
|
||||||
appender.rolling_old.fileName = ${sys:os.logs.base_path}${sys:file.separator}${sys:os.logs.cluster_name}.log
|
appender.rolling_old.fileName = ${sys:opensearch.logs.base_path}${sys:file.separator}${sys:opensearch.logs.cluster_name}.log
|
||||||
```
|
```
|
||||||
|
|
||||||
- `${sys:os.logs.base_path}` is the directory for logs (for example, `/var/log/opensearch/`).
|
- `${sys:opensearch.logs.base_path}` is the directory for logs (for example, `/var/log/opensearch/`).
|
||||||
- `${sys:os.logs.cluster_name}` is the name of the cluster.
|
- `${sys:opensearch.logs.cluster_name}` is the name of the cluster.
|
||||||
- `[%node_name]` is the name of the node.
|
- `[%node_name]` is the name of the node.
|
||||||
|
|
||||||
|
|
||||||
|
@ -202,4 +202,4 @@ cluster.task.consumers.top_n.frequency:30s
|
||||||
|
|
||||||
## Deprecation logs
|
## Deprecation logs
|
||||||
|
|
||||||
Deprecation logs record when clients make deprecated API calls to your cluster. These logs can help you identify and fix issues prior to upgrading to a new major version. By default, OpenSearch logs deprecated API calls at the WARN level, which works well for almost all use cases. If desired, configure `logger.deprecation.level` using `_cluster/settings`, `opensearch.yml`, or `log4j2.properties`.
|
Deprecation logs record when clients make deprecated API calls to your cluster. These logs can help you identify and fix issues prior to upgrading to a new major version. By default, OpenSearch logs deprecated API calls at the WARN level, which works well for almost all use cases. If desired, configure `logger.deprecation.level` using `_cluster/settings`, `opensearch.yml`, or `log4j2.properties`.
|
||||||
|
|
Loading…
Reference in New Issue