Skip to content

Commit ca3fce2

Browse files
Update logging.mdx
1 parent b5b10a3 commit ca3fce2

File tree

1 file changed

+1
-5
lines changed

1 file changed

+1
-5
lines changed

vcluster/configure/vcluster-yaml/logging.mdx

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -17,10 +17,6 @@ vCluster supports two log encoding formats for the vCluster control plane pod.
1717
- console (_Default_): Human-readable format. Ideal for development and manual log review.
1818
- JSON: Structured format for log aggregation. Ideal for external monitoring and analysis tools.
1919

20-
:::note Platform logging
21-
The `logging.encoding` setting only affects vCluster control plane pod logs. Platform logs generated from a virtual cluster connected to the platform uses a separate configuration and will not be affected by these formats.
22-
:::
23-
2420
### Console format
2521

2622
The console format provides human-readable logs with timestamps, log levels, source locations, and contextual information. The console format is best suited for use cases where users will be troubleshooting a single virtual cluster. Choose this format in environments where human readability is more important than structured log parsing. Example use cases include:
@@ -39,7 +35,7 @@ The console format provides human-readable logs with timestamps, log levels, sou
3935

4036
The JSON format structures log data for programmatic processing and integration with log management systems. The JSON format is best suited for use cases where external tools are used to monitor and analyze logs for multiple virtual clusters. Log aggregation tools (e.g. Elasticsearch or Splunk) can ingest these logs to support automated analysis, alerting, and integration with monitoring platforms (e.g. Prometheus and Grafana). Examples use cases include:
4137

42-
* Product environments where multiple virtual clusters are being monitored and logs from all of them need need to be parsed and processed automatically.
38+
* Product environments where multiple virtual clusters are being monitored and logs from all of them need to be parsed and processed automatically.
4339

4440
```json
4541
{"level":"info","ts":1750160027.442782,"logger":"license","caller":"loader/inject.go:52","msg":"initializing license...","component":"vcluster"}

0 commit comments

Comments
 (0)