Gargi-jais11 commented on code in PR #320:
URL: https://github.com/apache/ozone-site/pull/320#discussion_r2767880387
##########
docs/05-administrator-guide/03-operations/11-tools/04-logs-in-ozone.md:
##########
@@ -0,0 +1,89 @@
+# Logs in Ozone
+
+Apache Ozone produces different types of logs to help users monitor and
troubleshoot the cluster. This document provides an overview of the available
logs, their configuration, and how to use them for debugging.
+
+## Service Logs
+
+Each Ozone service (Ozone Manager, Storage Container Manager, Datanode, S3
Gateway, and Recon) generates its own log file. These logs contain detailed
information about the service's operations, including errors and warnings.
+
+By default, log files are stored in the `$OZONE_LOG_DIR` directory, which is
usually set to the `logs` directory under the Ozone installation. The log file
names are specific to each service, for example:
+
+- `ozone-om-....log` for Ozone Manager
+- `ozone-scm-....log` for Storage Container Manager
+- `ozone-datanode-....log` for Datanode
+
+The logging behavior for each service is controlled by its `log4j.properties`
file, located in the service's `$OZONE_CONF_DIR` directory, usually
`etc/hadoop`. You can modify this file to change the log level, appenders, and
other logging parameters.
+
+## Audit Logs
Review Comment:
Also add section for Datanode Container Log
```suggestion
## Datanode Container Logs
In addition to the main service log, Datanode also generates
container-specific logs that track container replica-level events. These logs
record brief messages about container state changes (open, closing, closed,
unhealthy), replication events, reconstruction, reconciliation, container
moves, and other container lifecycle events.
Container logs are configured via `dn-container-log4j2.properties` and are
stored as `dn-container-${hostName}.log` in the `$OZONE_LOG_DIR` directory.
## Audit Logs
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
