Open topic with navigation
In NuoDB's monitoring framework, each admin service process tracks all the statistics for its host and NuoDB Manager reports these statistics from its one connection with that admin service process. In this monitoring framework, the following statistic sets are available using the
The monitoring framework is disabled by default and can be enabled by setting the NuoDB Manager
Note: By default, the
monitor command reports only database process statistics.
NuoDB Manager can subscribe to metrics from the command line with the
--command option and
monitor command. Monitors are not available when running NuoDB Manager interactively. The first set of statistics from the
monitor command includes all available metrics. Subsequent sets of statistics include only those metrics that have changed since the last time the metrics were published. Typically, the metrics are published every ten seconds. The exact interval is published as the
monitor database, or
monitor process subscribe to the stream of NuoDB metrics (see Metrics Published by Database Processes) published by the database processes (TE, SM, or SSM).
monitorDomainNewequals false (default)
Each database process statistic set is preceded by two process status lines. The first line is of the format:
nnn] [ db =
name] [ nodeId =
Dec 12, 2014 5:03:10 PM [SM] ip-172-31-40-24/184.108.40.206:48006 (us-east-1) [ pid = 32594 ] [ db = test2 ] [ nodeId = 1 ] RUNNING
The second process status line is the usage summary line.
Sample usage summary line from a TE:
Idle 8% + CPU 15% Runnable 0% Sync 25% Lock 0% Fetch 1% Commit 1% Throttle 57% Network Send 2%
Sample usage summary line from an SM or SSM:
Idle 0% + CPU 0% Runnable 0% Sync 0% Fetch 0% Throttle 0% Network Send 0% Archive Read 0% Write 0% Journal 0%
This usage summary line breaks down time spent by a database process (TE, SM, or SSM).
Idle is the percentage of time that the process had no work to do. The remaining figures break down the time when the process was not idle.
CPU is the percentage of this time that was spent running code, in user or kernel mode.
Runnable is an estimate of how much
CPU would increase if the hardware had more cores. The remaining figures have some unknown amount of overlap with
CPU because of the way the accounting is done. Percentages are rounded to the nearest integer.
|Sync||Time one thread was waiting for another thread to release exclusive access to an object.||TE/SM/SSM|
|Lock||Time a client was waiting for another client to finish a transaction that locked an SQL record.||TE|
|Fetch||Time spent waiting to fetch an atomThe internal object structure representing all data in a NuoDB database. Atoms are self-coordinating objects that represent specific types of information (such as data, indexes or schemas). Any Atom can serialize itself, transmit its serialized contents to a new replica, send replication messages to replicas of itself. TEs operate on Atoms, listen for changes, and communicate changes with other TEs in the database. The SM allows Atoms to serialize themselves to permanent storage. from another node or from disk.||TE/SM/SSM|
|Commit||Time a client was waiting in
|Throttle||Time processing was paused due to over consumption of a resource such as memory or I/O bandwidth.||TE/SM/SSM|
|Network Send||Time spent sending messages over the network.||TE/SM/SSM|
|Archive Read||Time spent reading atoms from the archive on disk.||SM/SSM|
|Write||Time spent writing atoms to the archive on disk.||SM/SSM|
|Journal||Time spent writing messages to the journal for crash recovery.||SM/SSM|
Each database process statistic set is preceded by one process status line of the format:
Nov 3, 2015 1:14:22 PM test:8339 [ ip-172-31-3-189/220.127.116.11:48004 ]
monitorDomainNew equal to true, you can disable reporting of database process statistics by setting the property
monitorDatabaseProcessStats to false.
Operating system (OS) metrics are only available if the property
monitorDomainNew equals true (not by default). OS metrics are gathered by the broker for its host. All OS metrics are prefixed with
OS- so that the database aggregate statistics set can distinguish OS metrics from NuoDB database process metrics. OS metric statistics sets are preceded by a line with the format:
Nov 3, 2015 1:00:02 PM (OS) [ ip-172-31-1-136/172.31.1.136:48004 ]:
monitorDomainNew equal to true, you can disable reporting of OS metrics by setting the property
monitorHostStats to false.
Database aggregate statistics are only available if the property
monitorDomainNew equals true (not by default). Database aggregate statistics include both database process metrics and OS metrics. All OS metrics are prefixed with
OS- to distinguish them from NuoDB database process metrics. Database aggregate statistics sets are preceded by a line with the format:
Nov 3, 2015 1:00:02 PM (aggregate) [ test2 ]:
monitorDomainNew equal to true, you can disable reporting of database aggregate statistics by setting the property
monitorDomainAggregates to false.
Reporting of alarms triggered by the database is only available if the property
monitorDomainNew equals true (not by default). Alarms are reported as in the following example if the property
alarmPretty is true:
Nov 4, 2015 10:09:45 AM NodeLeft Alarm [domainleft]: Details: Node SM db=[test] pid=676 id=5 req=SMs (local) Alarm Definition [domainleft]: type=NodeLeft dimension=Domain entity=* (Warning)
Alarms are reported as in the following example if the property
alarmPretty is false:
Alarm id=43f44ec2-bc6e-472c-87ef-13a8cf3bd6ef entity=[domain] def=[Alarm Definition [domainleft]: type=NodeLeft dimension=Domain entity=* (Warning)] ud=[Node SM db=[test] pid=742 id=7 req=SMs (local)]
monitorDomainNew equal to true, you can disable reporting of triggered alarms by setting the property
monitorDomainAlarm to false.