- To: "conduit@xxxxxxxxxxxxxxxx" <conduit@xxxxxxxxxxxxxxxx>
- Subject: [conduit] CONDUIT LDM Clock Drift
- From: "Herzmann, Daryl E [AGRON]" <akrherz@xxxxxxxxxxx>
- Date: Wed, 28 Oct 2020 16:55:13 +0000
- Authentication-results: unidata.ucar.edu; dkim=none (message not signed) header.d=none;unidata.ucar.edu; dmarc=none action=none header.from=iastate.edu;
Greetings (emailing the right list this time!), It has been mentioned a few times on this list that there is a clock drift issue with the CONDUIT LDM feed emitting from NCO/IDP. I'd like to ping this issue again and see if NCO can please check that system clocks are being synced there. The attached plot of feed latency shows the building of latency with time from my monitoring, which is a tell tale sign of clock drift. thanks! daryl -- /** * daryl herzmann * Systems Analyst III -- Iowa Environmental Mesonet * https://mesonet.agron.iastate.edu */
Attachment:
latency.png
Description: latency.png
- Follow-Ups:
- Re: [conduit] CONDUIT LDM Clock Drift
- From: Pete Pokrandt
- Re: [conduit] CONDUIT LDM Clock Drift
- From: Bob Lipschutz - NOAA Affiliate
- Re: [conduit] CONDUIT LDM Clock Drift