diff options
author | Chris <github.account@chrigel.net> | 2018-02-20 20:12:23 +0100 |
---|---|---|
committer | Chris <github.account@chrigel.net> | 2018-02-20 20:59:51 +0100 |
commit | 6fcd770b8609de110b827ab443ed8cfc09a4c634 (patch) | |
tree | 25580bbce5aa648eab10dc8ad14391a4933521fa /web | |
parent | 2d9b7f32332fab1655516e5fc2b11ffe87e1f3cc (diff) |
Add dashboard info for portcheck plugin. Rearranged error codes
Diffstat (limited to 'web')
-rw-r--r-- | web/dashboard_info.js | 21 |
1 files changed, 21 insertions, 0 deletions
diff --git a/web/dashboard_info.js b/web/dashboard_info.js index dbc821227b..1323d3c211 100644 --- a/web/dashboard_info.js +++ b/web/dashboard_info.js @@ -219,6 +219,12 @@ netdataDashboard.menu = { info: 'Performance metrics for <b>PHP-FPM</b>, an alternative FastCGI implementation for PHP.' }, + 'portcheck': { + title: 'Port Check', + icon: '<i class="fas fa-heartbeat"></i>', + info: 'Service availability and latency monitoring using port checks.' + }, + 'postfix': { title: 'postfix', icon: '<i class="fas fa-envelope"></i>', @@ -1719,6 +1725,21 @@ netdataDashboard.context = { }, // ------------------------------------------------------------------------ + // Port check + + 'portcheck.latency': { + info: 'The <code>Latency</code> describes the time spent opening and closing a socket. No data is sent or received. ' + + 'A response time of <code>0.0 ms</code> indicates a connection error.' + }, + + 'portcheck.error': { + valueRange: "[0, 3]", + info: 'The <code>Error</code> is returned by the plugin when it could not connect to the host/port. It is one of: ' + + '<code>0</code> (connection successful), <code>1</code> (port closed), <code>2</code> (host or port timeout), <code>3</code> (hostname lookup failed). ' + + 'The error code is most useful for 3rd-party apps and alarms.' + }, + + // ------------------------------------------------------------------------ 'chrony.system': { info: 'In normal operation, chronyd never steps the system clock, because any jump in the timescale can have adverse consequences for certain application programs. Instead, any error in the system clock is corrected by slightly speeding up or slowing down the system clock until the error has been removed, and then returning to the system clockâs normal speed. A consequence of this is that there will be a period when the system clock (as read by other programs using the <code>gettimeofday()</code> system call, or by the <code>date</code> command in the shell) will be different from chronyd\'s estimate of the current true time (which it reports to NTP clients when it is operating in server mode). The value reported on this line is the difference due to this effect.', |