Why CLOCK_REALTIME metrics depend on event publisher flag

[nmathew]

hi @aneeshkp

ccd_ptp_clock_state{iface="CLOCK_REALTIME",node="dc295srv31",process="phc2sys"} 1

this metrics getting updated properly only if we enable the event publisher , why so?

Metrics processing logic takes different path according event publisher flag, linuxptp-daemon with event publisher disabled and cloud-event-proxy with event publisher enabled.

why node ptp sync state depend on event publisher flag?

Any pointers on these will be helpful.

Thank you,
Nobin

[nmathew]

Is this a design choice, because local ptp clock sync is required only if DU app is running locally?
event publisher is also required only if DU app is running on the node.

please let me know..

[nmathew]

@aneeshkp any inputs..

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale