You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,15 +106,17 @@ This will remove all docker images created by the server during the build proces
106
106
107
107
# Request Logging
108
108
109
-
Request logging can be enabled by setting `SHARDEUM_JSONRPC_ENABLE_REQUEST_LOGGING=true` in your environment. When enabled:
109
+
Request logging is disabled by default. To enable it, set `SHARDEUM_JSONRPC_ENABLE_REQUEST_LOGGING=true` in your environment.
110
110
111
-
- File logging is enabled by default and logs are written to `logs/requests.log`
112
-
- Can be disabled by explicitly setting `SHARDEUM_JSONRPC_FILE_LOGGING=false`
111
+
When request logging is enabled:
112
+
- Logs will be written to a file at `logs/requests.log` by default
113
+
- You can disable file logging by setting `SHARDEUM_JSONRPC_FILE_LOGGING=false`
113
114
- The logging directory can be configured using `SHARDEUM_JSONRPC_LOGGING_DIR` (defaults to `logs`)
114
115
- The logs can be viewed by running `npm run tail-request-logs`
115
116
- Console logging is disabled by default
116
-
-Can be enabled by setting `SHARDEUM_JSONRPC_CONSOLE_LOGGING=true`
117
+
-You can enable console logging by setting `SHARDEUM_JSONRPC_CONSOLE_LOGGING=true`
117
118
119
+
Note: Request logging is disabled by default in production environments to prevent log files from growing too large. Consider implementing log rotation if enabling request logging in production.
0 commit comments