Update logging.mdx

Author: joaniekube

vcluster/configure/vcluster-yaml/logging.mdx

@@ -5,55 +5,94 @@ sidebar_position: 13
 description: Configuration for setting structured logging options for vCluster.
 ---
 
-vCluster prints out structured logs to the console, by default. There are two log-encoding options provided: `console` and `json`.
+import Logging from '../../_partials/config/sleepMode.mdx'
 
-The default logging option is set to `console`.
+vCluster outputs structured logs that help you monitor and troubleshoot your virtual clusters. You can configure the log format to suit your monitoring and analysis tools and workflows.
 
-## Configure logging
+## Configure log encoding
 
-To choose the logging encoding for vCluster logs, you can set the `logging.encoding` field in the `vcluster.yaml` to
-one of the following values: `json` or `console`. For example:
-```yaml
-logging:
-  encoding: json
-```
+You can set the log encoding format in your `vcluster.yaml` configuration:
 
-:::note
-Setting `logging.encoding` value in vCluster.yaml only applies to the logs generated by vCluster and has no control over
-platform generated logs. So, make sure that you have set the appropriate logging format in platform as well that suits
-your requirements. Refer [platform logging](https://www.vcluster.com/docs/platform/administer/monitoring/metrics#configure-logging)
-for configuring logging in platform.
+<InterpolatedCodeBlock 
+  code={`logging:
+  encoding: [[VAR:ENCODING:json]]`} 
+  language="yaml" 
+/>
+
+Select either `json` or `console` for the `encoding` value.
+
+:::note Platform logging
+The `logging.encoding` setting only affects vCluster component logs. Platform-generated logs use a separate configuration.
 :::
 
-### Console logging
+## Log encoding formats
+
+vCluster supports two log encoding formats:
+
+- [console](#console-format) (_Default_): Human-readable format ideal for development and manual log review.
+- [JSON](#json-format): Structured format for log aggregation and automated analysis.
 
-The logs in this format include constant log messages, a human-readable timestamp, log levels, the file and line numberof the source caller, and with variables in the body:
+### Console format
+
+The console format provides human-readable logs with timestamps, log levels, source locations, and contextual information:
 
 ```text
 2025-06-16 04:43:25	INFO	license	loader/inject.go:52	initializing license...	{"component": "vcluster"}
 2025-06-16 04:43:25	INFO	license	loader/inject.go:59	detected license type	{"component": "vcluster", "licenseType": "Online"}
 2025-06-16 04:43:29	INFO	online/license.go:141	Enabled features:	{"component": "vcluster"}
 2025-06-16 04:43:29	INFO	online/license.go:146	rancher-integration	{"component": "vcluster"}
-
 ```
 
-### JSON logging
+The console format is best suited for local development and testing, where developers benefit from quick, readable output. It also works well for manual log review and debugging, especially when troubleshooting issues directly in the terminal. Choose this format in environments where human readability is more important than structured log parsing.
 
-In addition to `console` logging, vCluster also supports printing logs encoded in JSON format.
+### JSON format
 
-This output format is helpful for structured logging, which allows you to search and filter logs easily.
+The JSON format structures log data for programmatic processing and integration with log management systems:
 
-```text
+```json
 {"level":"info","ts":1750160027.442782,"logger":"license","caller":"loader/inject.go:52","msg":"initializing license...","component":"vcluster"}
 {"level":"info","ts":1750160027.4497442,"logger":"license","caller":"loader/inject.go:59","msg":"detected license type","component":"vcluster","licenseType":"Online"}
 {"level":"info","ts":1750160029.1307533,"caller":"online/license.go:141","msg":"Enabled features:","component":"vcluster"}
 {"level":"info","ts":1750160029.1307998,"caller":"online/license.go:146","msg":"connected-clusters","component":"vcluster"}
 ```
 
-The JSON encoded logs contain at least the following fields:
+#### JSON log fields
+
+Each JSON log entry contains the following standard fields:
+
+| Field | Type | Description |
+|-------|------|-------------|
+| `level` | string | Log level (`info`, `warn`, `error`, `debug`) |
+| `ts`    | number | Unix timestamp (seconds since epoch) |
+| `caller`| string | Source file and line number |
+| `msg`   | string | Log message content |
+| `component` | string | vCluster component that generated the log |
+
+Additional fields might be displayed based on context and log content.
+
+The JSON format is ideal for production environments where logs need to be parsed and processed automatically. It works well with log aggregation tools like Elasticsearch or Splunk and supports automated analysis, alerting, and integration with monitoring platforms such as Prometheus and Grafana.
+
+## Examples
+
+### Development environment
+
+For local development with human-readable logs:
+
+```yaml
+logging:
+  encoding: console
+```
+
+### Production environment
+
+For production with structured logging and monitoring:
+
+```yaml
+logging:
+  encoding: json
+```
+
+## Config reference
+
+<Logging />
 
-- `level`: The log level of the message
-- `ts`: The timestamp of the message (floating-point number of seconds since the Unix epoch)
-- `caller`: The file and line number of the message
-- `msg`: The message itself
-- `component`: The vCluster component that emitted the message