Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-15929

ptp process does not print severity when logs written to stdout in a container

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Undefined Undefined
    • rhel-9.4
    • rhel-9.2.0
    • linuxptp
    • None
    • linuxptp-4.2-1.el9
    • None
    • None
    • ZStream
    • rhel-sst-cs-stacks
    • ssg_core_services
    • 20
    • 23
    • None
    • False
    • Hide

      None

      Show
      None
    • No
    • Red Hat Enterprise Linux
    • None
    • Approved Blocker
    • None

      This is reported by the customer :

      The logs from the ptp containers contain no severity and therefore log entries end up with a "Default" severity. This is in the linuxptp-daemon-container
      When LinuxPTP is deployed within a container, all logs are written to stdout by utilizing the -m option. These logs are directed to the pod's log, making them accessible via 'kubectl logs.' Please note that stderr won't be available in the system logs.

      The ability to access log severity through stdout is a valuable feature that customers are actively seeking. When severity information is included in the pod logs, it simplifies the process of creating customized alerts using log monitoring tools

       

      steps 
      oc logs linuxptp-daemon-6mhbw -c linuxptp-daemon-container
      Actual results: No severity

              rhn-support-mlichvar Miroslav Lichvar
              aputtur@redhat.com Aneesh Puttur
              Miroslav Lichvar Miroslav Lichvar
              Yalin Li Yalin Li
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: