Difference between revisions of "Draft: TLM/Current/TLMPEGuide/Logging"
From Genesys Documentation
m |
m |
||
Line 13: | Line 13: | ||
#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. | #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. | #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> | + | </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 | |Status=No | ||
}} | }} | ||
|PEPageType=7a5823f3-05b5-412b-b580-e73e34079c41 | |PEPageType=7a5823f3-05b5-412b-b580-e73e34079c41 | ||
}} | }} |
Revision as of 12:04, June 19, 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
Include a link to the "suite-level" documentation for logging:
Telemetry Service sends logs to stdout.
#mintydocs_link must be called from a MintyDocs-enabled page (Draft:TLM/Current/TLMPEGuide/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.
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.