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

[IDD #QBL-783661]: split LDM REQUEST for CONDUIT feed

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDD #QBL-783661]: split LDM REQUEST for CONDUIT feed
  • Date: Mon, 30 Sep 2019 13:03:44 -0600
Hi Rick,

Are you gathering LDM+system metrics on npserv1 and npserv2?

One gathers these metrics by running a pair of 'ldmadmin'
actions out of cron, typically once per minute:

# LDM metrics gathering
* * * * * bin/ldmadmin addmetrics > /dev/null
0 0 1 * * bin/ldmadmin newmetrics > /dev/null

After gathering metrics for "awhile" (typically at least a full
day), it is usually instructive to plot the metrics gathered
by running:

<as 'ldm'>
ldmadmin plotmetrics

In order for this to work, one would have had to install 'gnuplot'
on the machine running the LDM.

If you are not already gathering metrics, it would help greatly if
you would start as this might give us a better clue as to the
difference in CONDUIT ingestion npserv1 and npserv2.

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: QBL-783661
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.