|
|
| (One intermediate revision by the same user not shown) |
| Line 1: |
Line 1: |
| − | {{Article
| + | #redirect [[Draft:TLM/Current/TLMPEGuide/Observability#Logging]] |
| − | |Standalone=No
| |
| − | |DisplayName=Logging
| |
| − | |Context=Learn how to store logs for Telemetry Service
| |
| − | |ComingSoon=No
| |
| − | |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}}
| |
| − | | |
| − | 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.
| |
| − | |Status=No
| |
| − | }}
| |
| − | |PEPageType=7a5823f3-05b5-412b-b580-e73e34079c41
| |
| − | }}
| |
Latest revision as of 16:23, December 20, 2021
