[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDD #ZUJ-606770]: NOAAPORT2 March 13 18Zish

Murray,

re:
> Was there a slowdown of NOAAPORT2 files March 13 for the hour of 18Z?

If you mean files delivered in IDD datastreams that derive from
NOAAPort, then the best way for you to investigate this is by
examining plots of latencies for your machine and its upstream(s):

Unidata HomePage
http://www.unidata.ucar.edu

  Data -> IDD Operational Status
  http://rtstats.unidata.ucar.edu/rtstats/

    Real-time IDD Statistics -> Statistics by Host
    http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex

Find your machine(s) in the list of machines on the last page
and then examine the latency plot for the feed(s) you are
investigating.  For instance, if your machine is:

unidata1.cmc.ec.gc.ca

then the page that has a variety of links to real-time stats
plots is:

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/siteindex?unidata1.cmc.ec.gc.ca

From that page, you can look at the past two days of latencies for
the feeds that the machine is receiving.  For instance, plot the
latencies for the NEXRAD Level 3 products that are distributed in
the NEXRAD3 feed:

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+unidata1.cmc.ec.gc.ca

You will see that there were latencies greater than 1200 seconds at
around 18 UTC on March 13.

To see what upstream(s) is providing the NEXRAD3 feed to this machine,
click on the topology link.  This will show:

Topology for NEXRAD3 to unidata1.cmc.ec.gc.ca

    0 unidata1.cmc.ec.gc.ca
        1 idd.unidata.ucar.edu. [no stats] 

Now, idd.unidata.ucar.edu is actually a cluster of machines, and it
is not obvious which of the real-server backends of this cluster
was/is feed your machine the NEXRAD3 feed.  But, you can spot check
the latencies for the real-server back end machines (which are
uni14, uni15, uni16, uni17, uni18, uni19, uni20, uni21, uni23,
and uni24) to see if their real-time stats show any latencies in
this feed.  For instance, lets randomly choose uni15 and see
if it reported latencies in the NEXRAD3 feed:

http://rtstats.unidata.ucar.edu/cgi-bin/rtstats/iddstats_nc?NEXRAD3+uni15.unidata.ucar.edu

High latencies are shown at about the time of interest.

Cheers,

Tom
--
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: ZUJ-606770
Department: Support IDD
Priority: Normal
Status: Closed
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.