20.6. PTP 이벤트 소비자 애플리케이션이 이벤트를 수신하는지 확인

프로세스

1. 활성 linuxptp-daemon Pod 목록을 가져옵니다. 다음 명령을 실행합니다.

   $ oc get pods -n openshift-ptp

   출력 예

   NAME                    READY   STATUS    RESTARTS   AGE
   linuxptp-daemon-2t78p   3/3     Running   0          8h
   linuxptp-daemon-k8n88   3/3     Running   0          8h

2. 다음 명령을 실행하여 필수 소비자 측 cloud-event-proxy 컨테이너의 메트릭에 액세스합니다.

   $ oc exec -it <linuxptp-daemon> -n openshift-ptp -c cloud-event-proxy -- curl 127.0.0.1:9091/metrics

   다음과 같습니다.

   <linuxptp-daemon>

   쿼리할 Pod를 지정합니다(예: linuxptp-daemon-2t78p ).

   출력 예

   # HELP cne_transport_connections_resets Metric to get number of connection resets
   # TYPE cne_transport_connections_resets gauge
   cne_transport_connection_reset 1
   # HELP cne_transport_receiver Metric to get number of receiver created
   # TYPE cne_transport_receiver gauge
   cne_transport_receiver{address="/cluster/node/compute-1.example.com/ptp",status="active"} 2
   cne_transport_receiver{address="/cluster/node/compute-1.example.com/redfish/event",status="active"} 2
   # HELP cne_transport_sender Metric to get number of sender created
   # TYPE cne_transport_sender gauge
   cne_transport_sender{address="/cluster/node/compute-1.example.com/ptp",status="active"} 1
   cne_transport_sender{address="/cluster/node/compute-1.example.com/redfish/event",status="active"} 1
   # HELP cne_events_ack Metric to get number of events produced
   # TYPE cne_events_ack gauge
   cne_events_ack{status="success",type="/cluster/node/compute-1.example.com/ptp"} 18
   cne_events_ack{status="success",type="/cluster/node/compute-1.example.com/redfish/event"} 18
   # HELP cne_events_transport_published Metric to get number of events published by the transport
   # TYPE cne_events_transport_published gauge
   cne_events_transport_published{address="/cluster/node/compute-1.example.com/ptp",status="failed"} 1
   cne_events_transport_published{address="/cluster/node/compute-1.example.com/ptp",status="success"} 18
   cne_events_transport_published{address="/cluster/node/compute-1.example.com/redfish/event",status="failed"} 1
   cne_events_transport_published{address="/cluster/node/compute-1.example.com/redfish/event",status="success"} 18
   # HELP cne_events_transport_received Metric to get number of events received  by the transport
   # TYPE cne_events_transport_received gauge
   cne_events_transport_received{address="/cluster/node/compute-1.example.com/ptp",status="success"} 18
   cne_events_transport_received{address="/cluster/node/compute-1.example.com/redfish/event",status="success"} 18
   # HELP cne_events_api_published Metric to get number of events published by the rest api
   # TYPE cne_events_api_published gauge
   cne_events_api_published{address="/cluster/node/compute-1.example.com/ptp",status="success"} 19
   cne_events_api_published{address="/cluster/node/compute-1.example.com/redfish/event",status="success"} 19
   # HELP cne_events_received Metric to get number of events received
   # TYPE cne_events_received gauge
   cne_events_received{status="success",type="/cluster/node/compute-1.example.com/ptp"} 18
   cne_events_received{status="success",type="/cluster/node/compute-1.example.com/redfish/event"} 18
   # HELP promhttp_metric_handler_requests_in_flight Current number of scrapes being served.
   # TYPE promhttp_metric_handler_requests_in_flight gauge
   promhttp_metric_handler_requests_in_flight 1
   # HELP promhttp_metric_handler_requests_total Total number of scrapes by HTTP status code.
   # TYPE promhttp_metric_handler_requests_total counter
   promhttp_metric_handler_requests_total{code="200"} 4
   promhttp_metric_handler_requests_total{code="500"} 0
   promhttp_metric_handler_requests_total{code="503"} 0