Difference between revisions of "Draft: TLM/Current/TLMPEGuide/Logging"

Revision as of 07:09, June 29, 2021

This is a draft page; the published version of this page can be found at TLM/Current/TLMPEGuide/Logging.

Learn how to store logs for Telemetry Service

Telemetry Service sends logs to stdout.

Telemetry Service logs are structured so that log documents can be split into two distinct indexes: one for the Core Telemetry activity and the other for the Telemetry client logs.

@@ Line 6: / Line 6: @@
 |Section={{Section
 |alignment=Vertical
-|structuredtext=<div style="background-color: aliceblue; font-style: italic;">Include a link to the "suite-level" documentation for logging: {{SuiteLevelLink|logging}}
+|structuredtext=Telemetry Service sends logs to stdout.
-Describe the following:
-#Log rotation and log sizing requirements.
-#Logging to stdout is preferred. If the service doesn't log to stdout, it must log to a PVC pointing to a log volume. Specify the storage characteristics of the log volume, such as IOPS, disk size, and read-write.
-#How to set log levels. Will likely be handled in the Helm chart, so you could include a link to the Configure page from here.
-</div>Telemetry Service sends logs to stdout.
 Telemetry Service logs are structured so that log documents can be split into two distinct indexes: one for the Core Telemetry activity and the other for the Telemetry client logs.