From 6e622db53ba9fc7732d9e98d2291fd2834c0c718 Mon Sep 17 00:00:00 2001 From: slinkydeveloper Date: Wed, 23 Aug 2023 15:59:34 +0200 Subject: [PATCH] Fix bad logging page indentation --- docs/restate/logging.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/restate/logging.md b/docs/restate/logging.md index f0ccb7bd..f97404be 100644 --- a/docs/restate/logging.md +++ b/docs/restate/logging.md @@ -45,6 +45,7 @@ When testing Restate locally, we recommend keeping the default configuration. When deploying in production, we recommend setting the log level to `info` and enabling the `Json` format in conjunction with a log collector, so you can later inspect and filter logs based on its event fields. We recommend to set up logging to a more verbose filter, and use the `Pretty` format. Some example filters: - * `info,restate_ingress_grpc=trace,restate_invoker=trace,restate=debug,hyper=debug` for network related issues - * `info,restate_worker::partition::effects=debug` to get insights on the state machine effects - * `info,restate_meta=trace` to check service discovery and registration + +* `info,restate_ingress_grpc=trace,restate_invoker=trace,restate=debug,hyper=debug` for network related issues +* `info,restate_worker::partition::effects=debug` to get insights on the state machine effects +* `info,restate_meta=trace` to check service discovery and registration