Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning

The 2017.02 roadmaps has made some elements of the SystemMetrics from the McStatus section meaningless. In below examples the removed elements are commented out.

In 2017.02 and later, please remove the following elements from the SystemMetrics module configuration file otherwise errors will be logged:

   <oclListenerParameterId>M.S.ocl</oclListenerParameterId>
   <fslListenerParameterId>M.S.fsl</fslListenerParameterId>
   <synchListenerParameterId>M.S.synchL</synchListenerParameterId>
   <synchRunnerParameterId>M.S.synchR</synchRunnerParameterId>
   <synchTaskListenerParameterId>M.S.synchTL</synchTaskListenerParameterId>
   <tmLauncherParameterId>M.S.tmLa</tmLauncherParameterId>        
   <tmChaserParameterId>M.S.tmC</tmChaserParameterId>
   <tmLogProcessorParameterId>M.S.tmLP</tmLogProcessorParameterId>
   <sysMonListenerParameterId>M.S.sysmL</sysMonListenerParameterId>
   <sysMonMonitorParameterId>M.S.sysmM</sysMonMonitorParameterId>
   <sysMonHeartbeatParameterId>M.S.sysmH</sysMonHeartbeatParameterId>

 

Table of Contents

Introduction to SystemMetrics

...

Code Block
xml
xml
<?xml version="1.0" encoding="UTF-8"?>
<systemMetrics xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/systemMetrics.xsd">
    <general>
        <locationId>metrics</locationId>
		<synchLevel>1</synchLevel>
    </general>
    <!-- Database total record and byte count -->
    <database>
        <rowCountParameterId>M.N.db</rowCountParameterId>
        <byteCountParameterId>M.B.db</byteCountParameterId>
    </database>
    <!-- TimeSeries record and byte count -->
    <!-- When SystemMetrics is run between an ImportAmalgamate and MC_MarkedRecordManager / MC_RollingBarrel spikes are to be expected -->
    <table>
        <tableName>TimeSeries</tableName>
        <rowCountParameterId>M.N.ts</rowCountParameterId>        
        <byteCountParameterId>M.B.ts</byteCountParameterId>
    </table>
    <!-- When SystemMetrics is run between an ImportAmalgamate and MC_MarkedRecordManager / MC_RollingBarrel spikes are to be expected -->
    <table>
        <tableName>TimeSeries</tableName>
        <rowCountParameterId>M.N.tsO4w</rowCountParameterId>        
        <byteCountParameterId>M.B.tsO4w</byteCountParameterId>
        <maximalAge unit="day" multiplier="4"/>
    </table>
    <!-- TimeSeries records with an expiry time over longer than 52 weeks -->
    <!-- When SystemMetrics is run between an ImportAmalgamate and MC_MarkedRecordManager / MC_RollingBarrel spikes are to be expected -->
    <table>
        <tableName>TimeSeries</tableName>
        <rowCountParameterId>M.N.tsE52w</rowCountParameterId>        
        <byteCountParameterId>M.B.tsE52w</byteCountParameterId>
        <lifeSpan unit="week" multiplier="52" />
    </table>
    <!-- WarmStates record and byte count -->
    <table>
        <tableName>WarmStates</tableName>
        <rowCountParameterId>M.N.ws</rowCountParameterId>        
        <!-- uncomment when WarmStates are stored in the database, not external on disk)-->
        <!--  <byteCountParameterId>B.ws</byteCountParameterId> -->
    </table>
    <table>
        <tableName>WarmStates</tableName>
        <rowCountParameterId>M.N.wsE10d</rowCountParameterId>        
        <!-- uncomment when WarmStates are stored in the database, not external on disk)-->
        <!-- <byteCountParameterId>M.NB.wse10d</byteCountParameterId> -->
        <lifeSpan unit="day" multiplier="10" />
    </table>
    <!-- Samples record count -->
    <!-- uncomment when Samples are used -->
    <!--  <table>
        <tableName>Samples</tableName>
        <rowCountParameterId>M.N.sa</rowCountParameterId>
    </table>
    -->
    <!-- ThresholdEvents record count -->
    <table>
        <tableName>ThresholdEvents</tableName>
        <rowCountParameterId>M.N.te</rowCountParameterId>
    </table>
    <!-- Counts the number of errors -->
    <logEntry>
        <rowCountParameterId>M.N.err</rowCountParameterId>
        <logLevel>ERROR</logLevel>
    </logEntry>
    <logEntry>
        <rowCountParameterId>M.N.warn</rowCountParameterId>
        <logLevel>WARN</logLevel>
    </logEntry>
    <!-- Counts the log entries with event code Config.Error -->
    <logEntry>
        <rowCountParameterId>M.N.cfgE</rowCountParameterId>
        <eventCode>Config.Error</eventCode>
    </logEntry>
    <logEntry>
        <rowCountParameterId>M.N.cfgW</rowCountParameterId>
        <eventCode>Config.Warn</eventCode>
    </logEntry>
    <mcStatus>
        <failedOverParameterId>M.S.failO</failedOverParameterId>
        <aliveRemoteMcCountParameterId>M.N.remMcs</aliveRemoteMcCountParameterId>
        <taskQueueLengthParameterId>M.N.tQL</taskQueueLengthParameterId>
        <activeTasksCountParameterId>M.N.rt</activeTasksCountParameterId>        
        <ocSessionsCountParameterId>M.N.ses</ocSessionsCountParameterId>
        <liveComponentCountParameterId>M.N.mccpts</liveComponentCountParameterId>        
<!-- Only usable up to 2017.01, no long possible in 2017.02 ! 
        <oclListenerParameterId>M.S.ocl</oclListenerParameterId>
        <fslListenerParameterId>M.S.fsl</fslListenerParameterId>
        <synchListenerParameterId>M.S.synchL</synchListenerParameterId>
        <synchRunnerParameterId>M.S.synchR</synchRunnerParameterId>
        <synchTaskListenerParameterId>M.S.synchTL</synchTaskListenerParameterId>
        <tmLauncherParameterId>M.S.tmLa</tmLauncherParameterId>        
        <tmChaserParameterId>M.S.tmC</tmChaserParameterId>
        <tmLogProcessorParameterId>M.S.tmLP</tmLogProcessorParameterId>
        <sysMonListenerParameterId>M.S.sysmL</sysMonListenerParameterId>
        <sysMonMonitorParameterId>M.S.sysmM</sysMonMonitorParameterId>
        <sysMonHeartbeatParameterId>M.S.sysmH</sysMonHeartbeatParameterId> -->
    </mcStatus>
    <fssStatus>
        <buildVersionParameterId>M.N.build</buildVersionParameterId>
        <queueLengthParameterId>M.N.fsQL</queueLengthParameterId>
        <downParameterId>M.N.fsDown</downParameterId>
    </fssStatus>
</systemMetrics>

 

...