...

Xconf Server → Telemetry → Permanent Profiles

•  "Schedule" – This gives the information about the schedule log upload frequency and / or date and time for the telemetry upload schedule.

For example,   */5 * * * * :- This will schedule the telemetry log upload at every 5 min.

Below is the format for this field.

Image Added

• Telemetry profile entries 

First field is “Header” - This is the name for the particular logs collection. This is a custom name and can be decided based on the use case or error condition or any other scenario.
Second field is “Content” - This is the "log message string" that appears in the RDK logs.
Third field is “type” - This is the name of the log file where the above log message string needs to be searched.
Fourth field is “Skip frequency” - This is a skip frequency. It can have values like 0, 1, 2 etc.
                     0 - This particular log message is never skipped.
                     1 - Skip every alternate occurrence of this log message.
                     2 - Skip 2 consecutive log message occurrences and then collect 1 occurrence and then again skip 2 occurrences.

TFTP Server

Upload Repository : TFTP Server

...

1. Restart the dcm-log service using “systemctl restart dcm-log”
2. To check the status of the service “systemctl status dcm-log”
3. By triggering the service , Turris-Omnia starts uploading the logs and json file to the HTTP/TFTP server on the scheduled interval
4. The log upload and Telemetry markers can be uploaded via HTTP and TFTP as required
5. The profile can be verified using curl, conf file , through logs and in server.

Log Upload

• Both TFTP and the / HTTP, Logs and Json Upload will be into http://35.155.171.121/xconf/upload/

...