monitoring.dev-production.esf-international.org
Open in
urlscan Pro
138.201.247.114
Public Scan
URL:
https://monitoring.dev-production.esf-international.org/
Submission Tags: phishingrod
Submission: On October 13 via api from DE — Scanned from CA
Submission Tags: phishingrod
Submission: On October 13 via api from DE — Scanned from CA
Form analysis 5 forms found in the DOM
<form id="optionsForm1" class="form-horizontal" data-hs-cf-bound="true">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="stop_updates_when_focus_is_lost" type="checkbox" checked="checked" data-toggle="toggle" data-offstyle="danger" data-onstyle="success"
data-on="On Focus" data-off="Always" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">On Focus</label><label class="btn btn-danger active toggle-off">Always</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>When to refresh the charts?</strong><br><small>When set to <b>On Focus</b>, the charts will stop being updated if the page / tab does not have the focus of the user. When set to <b>Always</b>, the charts will
always be refreshed. Set it to <b>On Focus</b> it to lower the CPU requirements of the browser (and extend the battery of laptops and tablets) when this page does not have your focus. Set to <b>Always</b> to work on another window (i.e.
change the settings of something) and have the charts auto-refresh in this window.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="eliminate_zero_dimensions" type="checkbox" checked="checked" data-toggle="toggle" data-on="Non Zero" data-off="All"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Non Zero</label><label class="btn btn-default active toggle-off">All</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which dimensions to show?</strong><br><small>When set to <b>Non Zero</b>, dimensions that have all their values (within the current view) set to zero will not be transferred from the netdata server (except if
all dimensions of the chart are zero, in which case this setting does nothing - all dimensions are transferred and shown). When set to <b>All</b>, all dimensions will always be shown. Set it to <b>Non Zero</b> to lower the data
transferred between netdata and your browser, lower the CPU requirements of your browser (fewer lines to draw) and increase the focus on the legends (fewer entries at the legends).</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-default off" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="destroy_on_hide" type="checkbox" data-toggle="toggle" data-on="Destroy" data-off="Hide" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Destroy</label><label class="btn btn-default active toggle-off">Hide</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>How to handle hidden charts?</strong><br><small>When set to <b>Destroy</b>, charts that are not in the current viewport of the browser (are above, or below the visible area of the page), will be destroyed and
re-created if and when they become visible again. When set to <b>Hide</b>, the not-visible charts will be just hidden, to simplify the DOM and speed up your browser. Set it to <b>Destroy</b>, to lower the memory requirements of your
browser. Set it to <b>Hide</b> for faster restoration of charts on page scrolling.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-default off" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="async_on_scroll" type="checkbox" data-toggle="toggle" data-on="Async" data-off="Sync" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Async</label><label class="btn btn-default active toggle-off">Sync</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Page scroll handling?</strong><br><small>When set to <b>Sync</b>, charts will be examined for their visibility immediately after scrolling. On slow computers this may impact the smoothness of page scrolling.
To update the page when scrolling ends, set it to <b>Async</b>. Set it to <b>Sync</b> for immediate chart updates when scrolling. Set it to <b>Async</b> for smoother page scrolling on slower computers.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm2" class="form-horizontal" data-hs-cf-bound="true">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="parallel_refresher" type="checkbox" checked="checked" data-toggle="toggle" data-on="Parallel" data-off="Sequential"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Parallel</label><label class="btn btn-default active toggle-off">Sequential</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which chart refresh policy to use?</strong><br><small>When set to <b>parallel</b>, visible charts are refreshed in parallel (all queries are sent to netdata server in parallel) and are rendered
asynchronously. When set to <b>sequential</b> charts are refreshed one after another. Set it to parallel if your browser can cope with it (most modern browsers do), set it to sequential if you work on an older/slower computer.</small>
</td>
</tr>
<tr class="option-row" id="concurrent_refreshes_row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="concurrent_refreshes" type="checkbox" checked="checked" data-toggle="toggle" data-on="Resync" data-off="Best Effort"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Resync</label><label class="btn btn-default active toggle-off">Best Effort</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Shall we re-sync chart refreshes?</strong><br><small>When set to <b>Resync</b>, the dashboard will attempt to re-synchronize all the charts so that they are refreshed concurrently. When set to
<b>Best Effort</b>, each chart may be refreshed with a little time difference to the others. Normally, the dashboard starts refreshing them in parallel, but depending on the speed of your computer and the network latencies, charts start
having a slight time difference. Setting this to <b>Resync</b> will attempt to re-synchronize the charts on every update. Setting it to <b>Best Effort</b> may lower the pressure on your browser and the network.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="sync_selection" type="checkbox" checked="checked" data-toggle="toggle" data-on="Sync" data-off="Don't Sync" data-onstyle="success"
data-offstyle="danger" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Sync</label><label class="btn btn-danger active toggle-off">Don't Sync</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Sync hover selection on all charts?</strong><br><small>When enabled, a selection on one chart will automatically select the same time on all other visible charts and the legends of all visible charts will be
updated to show the selected values. When disabled, only the chart getting the user's attention will be selected. Enable it to get better insights of the data. Disable it if you are on a very slow computer that cannot actually do
it.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="sync_pan_and_zoom" type="checkbox" checked="checked" data-toggle="toggle" data-on="Sync" data-off="Don't Sync" data-onstyle="success"
data-offstyle="danger" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Sync</label><label class="btn btn-danger active toggle-off">Don't Sync</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Sync pan and zoom on all charts?</strong><br><small>When enabled, pan and zoom operations on a chart will be replicated to all charts (even the ones that are not currently visible - of course only when they
will become visible). When disabled, pan and zoom operations will not be propagated to other charts.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm3" class="form-horizontal" data-hs-cf-bound="true">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="netdata_theme_control" type="checkbox" checked="checked" data-toggle="toggle" data-offstyle="danger" data-onstyle="success"
data-on="Dark" data-off="White" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Dark</label><label class="btn btn-danger active toggle-off">White</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which theme to use?</strong><br><small>Netdata comes with two themes: <b>Dark</b> (the default) and <b>White</b>.<br><b>Switching this will reload the dashboard</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="show_help" type="checkbox" checked="checked" data-toggle="toggle" data-on="Help Me" data-off="No Help" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Help Me</label><label class="btn btn-default active toggle-off">No Help</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Do you need help?</strong><br><small>Netdata can show some help in some areas to help you use the dashboard. If all these balloons bother you, disable them using this
switch.<br><b>Switching this will reload the dashboard</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="pan_and_zoom_data_padding" type="checkbox" checked="checked" data-toggle="toggle" data-on="Pad" data-off="Don't Pad"
data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Pad</label><label class="btn btn-default active toggle-off">Don't Pad</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable data padding when panning and zooming?</strong><br><small>When set to <b>Pad</b> the charts will be padded with more data, both before and after the visible area, thus giving the impression the whole
database is loaded. This padding will happen only after the first pan or zoom operation on the chart (initially all charts have only the visible data). When set to <b>Don't Pad</b> only the visible data will be transfered from the
netdata server, even after the first pan and zoom operation.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="smooth_plot" type="checkbox" checked="checked" data-toggle="toggle" data-on="Smooth" data-off="Rough" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Smooth</label><label class="btn btn-default active toggle-off">Rough</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable Bézier lines on charts?</strong><br><small>When set to <b>Smooth</b> the charts libraries that support it, will plot smooth curves instead of simple straight lines to connect the points.<br>Keep in
mind <a href="http://dygraphs.com" target="_blank">dygraphs</a>, the main charting library in netdata dashboards, can only smooth line charts. It cannot smooth area or stacked charts. When set to <b>Rough</b>, this setting can lower the
CPU resources consumed by your browser.</small></td>
</tr>
</tbody>
</table>
</div>
</form><form id="optionsForm4" class="form-horizontal" data-hs-cf-bound="true">
<div class="form-group">
<table>
<tbody>
<tr class="option-row">
<td colspan="2" align="center"><small><b>These settings are applied gradually, as charts are updated. To force them, refresh the dashboard now</b>.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 38px;"><input id="units_conversion" type="checkbox" checked="checked" data-toggle="toggle" data-on="Scale Units" data-off="Fixed Units"
data-onstyle="success" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Scale Units</label><label class="btn btn-default active toggle-off">Fixed Units</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Enable auto-scaling of select units?</strong><br><small>When set to <b>Scale Units</b> the values shown will dynamically be scaled (e.g. 1000 kilobits will be shown as 1 megabit). Netdata can auto-scale these
original units: <code>kilobits/s</code>, <code>kilobytes/s</code>, <code>KB/s</code>, <code>KB</code>, <code>MB</code>, and <code>GB</code>. When set to <b>Fixed Units</b> all the values will be rendered using the original units
maintained by the netdata server.</small></td>
</tr>
<tr id="settingsLocaleTempRow" class="option-row">
<td class="option-control">
<div class="toggle btn btn-primary" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="units_temp" type="checkbox" checked="checked" data-toggle="toggle" data-on="Celsius" data-off="Fahrenheit" data-width="110px">
<div class="toggle-group"><label class="btn btn-primary toggle-on">Celsius</label><label class="btn btn-default active toggle-off">Fahrenheit</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Which units to use for temperatures?</strong><br><small>Set the temperature units of the dashboard.</small></td>
</tr>
<tr id="settingsLocaleTimeRow" class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="seconds_as_time" type="checkbox" checked="checked" data-toggle="toggle" data-on="Time" data-off="Seconds" data-onstyle="success"
data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Time</label><label class="btn btn-default active toggle-off">Seconds</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Convert seconds to time?</strong><br><small>When set to <b>Time</b>, charts that present <code>seconds</code> will show <code>DDd:HH:MM:SS</code>. When set to <b>Seconds</b>, the raw number of seconds will be
presented.</small></td>
</tr>
<tr class="option-row">
<td class="option-control">
<div class="toggle btn btn-success" data-toggle="toggle" style="width: 110px; height: 19px;"><input id="local_timezone" type="checkbox" checked="checked" data-toggle="toggle" data-on="Your Time" data-off="Server Time"
data-onstyle="success" data-offstyle="danger" data-width="110px">
<div class="toggle-group"><label class="btn btn-success toggle-on">Your Time</label><label class="btn btn-danger active toggle-off">Server Time</label><span class="toggle-handle btn btn-default"></span></div>
</div>
</td>
<td class="option-info"><strong>Show browser local time or server time?</strong><br><small>When set to <b>Your Time</b>, the charts will use your browser local time. When set to <b>Server Time</b> the charts will use the server time.<br>Set
it to <b>Your Time</b> to have a common time-reference, no matter where the server is and which time zone it uses (all your dashboards will report your local time). Set it to <b>Server Time</b> when you need to compare netdata charts
with server log files.<br>Your browser time zone is: <b><span id="browser_timezone">America/Vancouver</span></b>.<br>The server reported timezone is: <b><span id="server_timezone">Europe/Berlin</span></b> (you can set this in
netdata.conf <code>[global].timezone</code>).<br>The current time zone on the dashboard is: <b><span id="current_timezone">unset, using browser default</span></b>.<br>
<div class="dropup"><button class="btn btn-default dropdown-toggle" type="button" id="dropdownTimeZone" data-toggle="dropdown" aria-haspopup="true" aria-expanded="true">Select Server Time Zone <span class="caret"></span></button>
<ul class="dropdown-menu scrollable-menu-50" aria-labelledby="dropdownTimeZone">
<li><a href="#" onclick="return selected_server_timezone("UTC")">Universal Time Coordinated (UTC)</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Abidjan")">Africa/Abidjan</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Accra")">Africa/Accra</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Algiers")">Africa/Algiers</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Bissau")">Africa/Bissau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Cairo")">Africa/Cairo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Casablanca")">Africa/Casablanca</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Ceuta")">Africa/Ceuta</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/El_Aaiun")">Africa/El_Aaiun</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Johannesburg")">Africa/Johannesburg</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Khartoum")">Africa/Khartoum</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Lagos")">Africa/Lagos</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Maputo")">Africa/Maputo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Monrovia")">Africa/Monrovia</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Nairobi")">Africa/Nairobi</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Ndjamena")">Africa/Ndjamena</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Tripoli")">Africa/Tripoli</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Tunis")">Africa/Tunis</a></li>
<li><a href="#" onclick="return selected_server_timezone("Africa/Windhoek")">Africa/Windhoek</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Adak")">America/Adak</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Anchorage")">America/Anchorage</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Araguaina")">America/Araguaina</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Buenos_Aires")">America/Argentina/Buenos_Aires</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Catamarca")">America/Argentina/Catamarca</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Cordoba")">America/Argentina/Cordoba</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Jujuy")">America/Argentina/Jujuy</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/La_Rioja")">America/Argentina/La_Rioja</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Mendoza")">America/Argentina/Mendoza</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Rio_Gallegos")">America/Argentina/Rio_Gallegos</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Salta")">America/Argentina/Salta</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/San_Juan")">America/Argentina/San_Juan</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/San_Luis")">America/Argentina/San_Luis</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Tucuman")">America/Argentina/Tucuman</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Argentina/Ushuaia")">America/Argentina/Ushuaia</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Asuncion")">America/Asuncion</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Atikokan")">America/Atikokan</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Bahia")">America/Bahia</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Bahia_Banderas")">America/Bahia_Banderas</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Barbados")">America/Barbados</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Belem")">America/Belem</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Belize")">America/Belize</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Blanc-Sablon")">America/Blanc-Sablon</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Boa_Vista")">America/Boa_Vista</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Bogota")">America/Bogota</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Boise")">America/Boise</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Cambridge_Bay")">America/Cambridge_Bay</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Campo_Grande")">America/Campo_Grande</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Cancun")">America/Cancun</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Caracas")">America/Caracas</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Cayenne")">America/Cayenne</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Chicago")">America/Chicago</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Chihuahua")">America/Chihuahua</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Costa_Rica")">America/Costa_Rica</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Creston")">America/Creston</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Cuiaba")">America/Cuiaba</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Curacao")">America/Curacao</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Danmarkshavn")">America/Danmarkshavn</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Dawson")">America/Dawson</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Dawson_Creek")">America/Dawson_Creek</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Denver")">America/Denver</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Detroit")">America/Detroit</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Edmonton")">America/Edmonton</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Eirunepe")">America/Eirunepe</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/El_Salvador")">America/El_Salvador</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Fortaleza")">America/Fortaleza</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Fort_Nelson")">America/Fort_Nelson</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Glace_Bay")">America/Glace_Bay</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Godthab")">America/Godthab</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Goose_Bay")">America/Goose_Bay</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Grand_Turk")">America/Grand_Turk</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Guatemala")">America/Guatemala</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Guayaquil")">America/Guayaquil</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Guyana")">America/Guyana</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Halifax")">America/Halifax</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Havana")">America/Havana</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Hermosillo")">America/Hermosillo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Indianapolis")">America/Indiana/Indianapolis</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Knox")">America/Indiana/Knox</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Marengo")">America/Indiana/Marengo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Petersburg")">America/Indiana/Petersburg</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Tell_City")">America/Indiana/Tell_City</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Vevay")">America/Indiana/Vevay</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Vincennes")">America/Indiana/Vincennes</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Indiana/Winamac")">America/Indiana/Winamac</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Inuvik")">America/Inuvik</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Iqaluit")">America/Iqaluit</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Jamaica")">America/Jamaica</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Juneau")">America/Juneau</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Kentucky/Louisville")">America/Kentucky/Louisville</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Kentucky/Monticello")">America/Kentucky/Monticello</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/La_Paz")">America/La_Paz</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Lima")">America/Lima</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Los_Angeles")">America/Los_Angeles</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Maceio")">America/Maceio</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Managua")">America/Managua</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Manaus")">America/Manaus</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Martinique")">America/Martinique</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Matamoros")">America/Matamoros</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Mazatlan")">America/Mazatlan</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Menominee")">America/Menominee</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Merida")">America/Merida</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Metlakatla")">America/Metlakatla</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Mexico_City")">America/Mexico_City</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Miquelon")">America/Miquelon</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Moncton")">America/Moncton</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Monterrey")">America/Monterrey</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Montevideo")">America/Montevideo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Nassau")">America/Nassau</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/New_York")">America/New_York</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Nipigon")">America/Nipigon</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Nome")">America/Nome</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Noronha")">America/Noronha</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/North_Dakota/Beulah")">America/North_Dakota/Beulah</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/North_Dakota/Center")">America/North_Dakota/Center</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/North_Dakota/New_Salem")">America/North_Dakota/New_Salem</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Ojinaga")">America/Ojinaga</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Panama")">America/Panama</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Pangnirtung")">America/Pangnirtung</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Paramaribo")">America/Paramaribo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Phoenix")">America/Phoenix</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Port-au-Prince")">America/Port-au-Prince</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Port_of_Spain")">America/Port_of_Spain</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Porto_Velho")">America/Porto_Velho</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Puerto_Rico")">America/Puerto_Rico</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Punta_Arenas")">America/Punta_Arenas</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Rainy_River")">America/Rainy_River</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Rankin_Inlet")">America/Rankin_Inlet</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Recife")">America/Recife</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Regina")">America/Regina</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Resolute")">America/Resolute</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Rio_Branco")">America/Rio_Branco</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Santarem")">America/Santarem</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Santiago")">America/Santiago</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Santo_Domingo")">America/Santo_Domingo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Sao_Paulo")">America/Sao_Paulo</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Scoresbysund")">America/Scoresbysund</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Sitka")">America/Sitka</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/St_Johns")">America/St_Johns</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Swift_Current")">America/Swift_Current</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Tegucigalpa")">America/Tegucigalpa</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Thule")">America/Thule</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Thunder_Bay")">America/Thunder_Bay</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Tijuana")">America/Tijuana</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Toronto")">America/Toronto</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Vancouver")">America/Vancouver</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Whitehorse")">America/Whitehorse</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Winnipeg")">America/Winnipeg</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Yakutat")">America/Yakutat</a></li>
<li><a href="#" onclick="return selected_server_timezone("America/Yellowknife")">America/Yellowknife</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Casey")">Antarctica/Casey</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Davis")">Antarctica/Davis</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/DumontDUrville")">Antarctica/DumontDUrville</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Macquarie")">Antarctica/Macquarie</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Mawson")">Antarctica/Mawson</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Palmer")">Antarctica/Palmer</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Rothera")">Antarctica/Rothera</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Syowa")">Antarctica/Syowa</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Troll")">Antarctica/Troll</a></li>
<li><a href="#" onclick="return selected_server_timezone("Antarctica/Vostok")">Antarctica/Vostok</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Almaty")">Asia/Almaty</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Amman")">Asia/Amman</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Anadyr")">Asia/Anadyr</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Aqtau")">Asia/Aqtau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Aqtobe")">Asia/Aqtobe</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Ashgabat")">Asia/Ashgabat</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Atyrau")">Asia/Atyrau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Baghdad")">Asia/Baghdad</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Baku")">Asia/Baku</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Bangkok")">Asia/Bangkok</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Barnaul")">Asia/Barnaul</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Beirut")">Asia/Beirut</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Bishkek")">Asia/Bishkek</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Brunei")">Asia/Brunei</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Chita")">Asia/Chita</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Choibalsan")">Asia/Choibalsan</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Colombo")">Asia/Colombo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Damascus")">Asia/Damascus</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Dhaka")">Asia/Dhaka</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Dili")">Asia/Dili</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Dubai")">Asia/Dubai</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Dushanbe")">Asia/Dushanbe</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Famagusta")">Asia/Famagusta</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Gaza")">Asia/Gaza</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Hebron")">Asia/Hebron</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Ho_Chi_Minh")">Asia/Ho_Chi_Minh</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Hong_Kong")">Asia/Hong_Kong</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Hovd")">Asia/Hovd</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Irkutsk")">Asia/Irkutsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Jakarta")">Asia/Jakarta</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Jayapura")">Asia/Jayapura</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Jerusalem")">Asia/Jerusalem</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kabul")">Asia/Kabul</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kamchatka")">Asia/Kamchatka</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Karachi")">Asia/Karachi</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kathmandu")">Asia/Kathmandu</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Khandyga")">Asia/Khandyga</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kolkata")">Asia/Kolkata</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Krasnoyarsk")">Asia/Krasnoyarsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kuala_Lumpur")">Asia/Kuala_Lumpur</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Kuching")">Asia/Kuching</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Macau")">Asia/Macau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Magadan")">Asia/Magadan</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Makassar")">Asia/Makassar</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Manila")">Asia/Manila</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Nicosia")">Asia/Nicosia</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Novokuznetsk")">Asia/Novokuznetsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Novosibirsk")">Asia/Novosibirsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Omsk")">Asia/Omsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Oral")">Asia/Oral</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Pontianak")">Asia/Pontianak</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Pyongyang")">Asia/Pyongyang</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Qatar")">Asia/Qatar</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Qyzylorda")">Asia/Qyzylorda</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Riyadh")">Asia/Riyadh</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Sakhalin")">Asia/Sakhalin</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Samarkand")">Asia/Samarkand</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Seoul")">Asia/Seoul</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Shanghai")">Asia/Shanghai</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Singapore")">Asia/Singapore</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Srednekolymsk")">Asia/Srednekolymsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Taipei")">Asia/Taipei</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Tashkent")">Asia/Tashkent</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Tbilisi")">Asia/Tbilisi</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Tehran")">Asia/Tehran</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Thimphu")">Asia/Thimphu</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Tokyo")">Asia/Tokyo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Tomsk")">Asia/Tomsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Ulaanbaatar")">Asia/Ulaanbaatar</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Urumqi")">Asia/Urumqi</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Ust-Nera")">Asia/Ust-Nera</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Vladivostok")">Asia/Vladivostok</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Yakutsk")">Asia/Yakutsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Yangon")">Asia/Yangon</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Yekaterinburg")">Asia/Yekaterinburg</a></li>
<li><a href="#" onclick="return selected_server_timezone("Asia/Yerevan")">Asia/Yerevan</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Azores")">Atlantic/Azores</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Bermuda")">Atlantic/Bermuda</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Canary")">Atlantic/Canary</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Cape_Verde")">Atlantic/Cape_Verde</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Faroe")">Atlantic/Faroe</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Madeira")">Atlantic/Madeira</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Reykjavik")">Atlantic/Reykjavik</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/South_Georgia")">Atlantic/South_Georgia</a></li>
<li><a href="#" onclick="return selected_server_timezone("Atlantic/Stanley")">Atlantic/Stanley</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Adelaide")">Australia/Adelaide</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Brisbane")">Australia/Brisbane</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Broken_Hill")">Australia/Broken_Hill</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Currie")">Australia/Currie</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Darwin")">Australia/Darwin</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Eucla")">Australia/Eucla</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Hobart")">Australia/Hobart</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Lindeman")">Australia/Lindeman</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Lord_Howe")">Australia/Lord_Howe</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Melbourne")">Australia/Melbourne</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Perth")">Australia/Perth</a></li>
<li><a href="#" onclick="return selected_server_timezone("Australia/Sydney")">Australia/Sydney</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Amsterdam")">Europe/Amsterdam</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Andorra")">Europe/Andorra</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Astrakhan")">Europe/Astrakhan</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Athens")">Europe/Athens</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Belgrade")">Europe/Belgrade</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Berlin")">Europe/Berlin</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Brussels")">Europe/Brussels</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Bucharest")">Europe/Bucharest</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Budapest")">Europe/Budapest</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Chisinau")">Europe/Chisinau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Copenhagen")">Europe/Copenhagen</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Dublin")">Europe/Dublin</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Gibraltar")">Europe/Gibraltar</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Helsinki")">Europe/Helsinki</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Istanbul")">Europe/Istanbul</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Kaliningrad")">Europe/Kaliningrad</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Kiev")">Europe/Kiev</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Kirov")">Europe/Kirov</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Lisbon")">Europe/Lisbon</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/London")">Europe/London</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Luxembourg")">Europe/Luxembourg</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Madrid")">Europe/Madrid</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Malta")">Europe/Malta</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Minsk")">Europe/Minsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Monaco")">Europe/Monaco</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Moscow")">Europe/Moscow</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Oslo")">Europe/Oslo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Paris")">Europe/Paris</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Prague")">Europe/Prague</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Riga")">Europe/Riga</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Rome")">Europe/Rome</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Samara")">Europe/Samara</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Saratov")">Europe/Saratov</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Simferopol")">Europe/Simferopol</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Sofia")">Europe/Sofia</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Stockholm")">Europe/Stockholm</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Tallinn")">Europe/Tallinn</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Tirane")">Europe/Tirane</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Ulyanovsk")">Europe/Ulyanovsk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Uzhgorod")">Europe/Uzhgorod</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Vienna")">Europe/Vienna</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Vilnius")">Europe/Vilnius</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Volgograd")">Europe/Volgograd</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Warsaw")">Europe/Warsaw</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Zaporozhye")">Europe/Zaporozhye</a></li>
<li><a href="#" onclick="return selected_server_timezone("Europe/Zurich")">Europe/Zurich</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Chagos")">Indian/Chagos</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Christmas")">Indian/Christmas</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Cocos")">Indian/Cocos</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Kerguelen")">Indian/Kerguelen</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Mahe")">Indian/Mahe</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Maldives")">Indian/Maldives</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Mauritius")">Indian/Mauritius</a></li>
<li><a href="#" onclick="return selected_server_timezone("Indian/Reunion")">Indian/Reunion</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Apia")">Pacific/Apia</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Auckland")">Pacific/Auckland</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Bougainville")">Pacific/Bougainville</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Chatham")">Pacific/Chatham</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Chuuk")">Pacific/Chuuk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Easter")">Pacific/Easter</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Efate")">Pacific/Efate</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Enderbury")">Pacific/Enderbury</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Fakaofo")">Pacific/Fakaofo</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Fiji")">Pacific/Fiji</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Funafuti")">Pacific/Funafuti</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Galapagos")">Pacific/Galapagos</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Gambier")">Pacific/Gambier</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Guadalcanal")">Pacific/Guadalcanal</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Guam")">Pacific/Guam</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Honolulu")">Pacific/Honolulu</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Kiritimati")">Pacific/Kiritimati</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Kosrae")">Pacific/Kosrae</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Kwajalein")">Pacific/Kwajalein</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Majuro")">Pacific/Majuro</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Marquesas")">Pacific/Marquesas</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Nauru")">Pacific/Nauru</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Niue")">Pacific/Niue</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Norfolk")">Pacific/Norfolk</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Noumea")">Pacific/Noumea</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Pago_Pago")">Pacific/Pago_Pago</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Palau")">Pacific/Palau</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Pitcairn")">Pacific/Pitcairn</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Pohnpei")">Pacific/Pohnpei</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Port_Moresby")">Pacific/Port_Moresby</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Rarotonga")">Pacific/Rarotonga</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Tahiti")">Pacific/Tahiti</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Tarawa")">Pacific/Tarawa</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Tongatapu")">Pacific/Tongatapu</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Wake")">Pacific/Wake</a></li>
<li><a href="#" onclick="return selected_server_timezone("Pacific/Wallis")">Pacific/Wallis</a></li>
</ul>
</div><b><span id="timezone_error_message"></span></b>
</small></td>
</tr>
</tbody>
</table>
</div>
</form>#
<form action="#" data-hs-cf-bound="true"><input class="form-control" id="switchRegistryPersonGUID" placeholder="your personal ID" maxlength="36" autocomplete="off" style="text-align:center;font-size:1.4em"></form>Text Content
netdata Real-time performance monitoring, done right! Connection ProblemThis agent cannot connect to Netdata Cloud. Please talk to system's administrator for more information. Discover your monitoring superpowers Do you know that you can manage a lot of nodes with Netdata Cloud? Sign-in esfi-dev-prod Sign-in Toggle navigation * * esfi-dev-prod My nodes Your nodes list is empty -------------------------------------------------------------------------------- Demo netdata nodes UK - London (DigitalOcean.com) US - New York (DigitalOcean.com) US - San Francisco (DigitalOcean.com) US - Atlanta (CDN77.com) Germany - Frankfurt (DigitalOcean.com) Canada - Toronto (DigitalOcean.com) Japan - Singapore (DigitalOcean.com) India - Bangalore (DigitalOcean.com) -------------------------------------------------------------------------------- Nodes beta Switch Identity What is this? * Nodes beta * Alarms * Settings * Update * * * * Import * Export * Print * Help * Sign In NETDATA REAL-TIME PERFORMANCE MONITORING, IN THE GREATEST POSSIBLE DETAIL Drag charts to pan. Shift + wheel on them, to zoom in and out. Double-click on them, to reset. Hover on them too! system.intr SYSTEM OVERVIEW Overview of the key system metrics. 0.0Disk ReadKiB/s 50.9Disk WriteKiB/s 4.0CPU%0.0100.0 0.03Net Inboundmegabits/s 0.08Net Outboundmegabits/s 61.6Used RAM% CPU Total CPU utilization (all cores). 100% here means there is no CPU idle time at all. You can get per core usage at the CPUs section and per application usage at the Applications Monitoring section. Keep an eye on iowait iowait (0.00%). If it is constantly high, your disks are a bottleneck and they slow your system down. An important metric worth monitoring, is softirq softirq (0.00%). A constantly high percentage of softirq may indicate network driver issues. Total CPU utilization (system.cpu) percentage 0.0 20.0 40.0 60.0 80.0 100.0 20:07:00 20:08:00 20:09:00 20:10:00 20:11:00 20:12:00 20:13:00 20:14:00 20:15:00 20:16:00 20:17:00 20:18:00 20:19:00 20:20:00 20:21:00 softirq user system iowait Sat, Oct 12, 2024 20:21:12 percentage softirq0.0 user2.0 system2.0 iowait0.0 LOAD Current system load, i.e. the number of processes using CPU or waiting for system resources (usually CPU and disk). The 3 metrics refer to 1, 5 and 15 minute averages. The system calculates this once every 5 seconds. For more information check this wikipedia article System Load Average (system.load) load 0.00 0.10 0.20 0.30 20:07:00 20:08:00 20:09:00 20:10:00 20:11:00 20:12:00 20:13:00 20:14:00 20:15:00 20:16:00 20:17:00 20:18:00 20:19:00 20:20:00 20:21:00 load1 load5 load15 Sat, Oct 12, 2024 20:21:05 load load10.16 load50.06 load150.12 DISK Total Disk I/O, for all physical disks. You can get detailed information about each disk at the Disks section and per application Disk usage at the Applications Monitoring section. Physical are all the disks that are listed in /sys/block, but do not exist in /sys/devices/virtual/block. Disk I/O (system.io) KiB/s -400 -200 0 200 400 600 800 1,000 20:07:00 20:08:00 20:09:00 20:10:00 20:11:00 20:12:00 20:13:00 20:14:00 20:15:00 20:16:00 20:17:00 20:18:00 20:19:00 20:20:00 20:21:00 in out Sat, Oct 12, 2024 20:21:12 KiB/s in0 out-51 Memory paged from/to disk. This is usually the total disk I/O of the system. system.pgpgio RAM System Random Access Memory (i.e. physical memory) usage. system.ram NETWORK Total bandwidth of all physical network interfaces. This does not include lo, VPNs, network bridges, IFB devices, bond interfaces, etc. Only the bandwidth of physical network interfaces is aggregated. Physical are all the network interfaces that are listed in /proc/net/dev, but do not exist in /sys/devices/virtual/net. system.net Total IP traffic in the system. system.ip Total IPv6 Traffic. system.ipv6 PROCESSES System processes. Running are the processes in the CPU. Blocked are processes that are willing to enter the CPU, but they cannot, e.g. because they wait for disk activity. system.processes Number of new processes created. system.forks All system processes. system.active_processes Context Switches, is the switching of the CPU from one process, task or thread to another. If there are many processes or threads willing to execute and very few CPU cores available to handle them, the system is making more context switching to balance the CPU resources among them. The whole process is computationally intensive. The more the context switches, the slower the system gets. system.ctxt IDLEJITTER Idle jitter is calculated by netdata. A thread is spawned that requests to sleep for a few microseconds. When the system wakes it up, it measures how many microseconds have passed. The difference between the requested and the actual duration of the sleep, is the idle jitter. This number is useful in real-time environments, where CPU jitter can affect the quality of the service (like VoIP media gateways). system.idlejitter INTERRUPTS Total number of CPU interrupts. Check system.interrupts that gives more detail about each interrupt and also the CPUs section where interrupts are analyzed per CPU core. system.intr CPU interrupts in detail. At the CPUs section, interrupts are analyzed per CPU core. system.interrupts SOFTIRQS CPU softirqs in detail. At the CPUs section, softirqs are analyzed per CPU core. system.softirqs SOFTNET Statistics for CPUs SoftIRQs related to network receive work. Break down per CPU core can be found at CPU / softnet statistics. processed states the number of packets processed, dropped is the number packets dropped because the network device backlog was full (to fix them on Linux use sysctl to increase net.core.netdev_max_backlog), squeezed is the number of packets dropped because the network device budget ran out (to fix them on Linux use sysctl to increase net.core.netdev_budget and/or net.core.netdev_budget_usecs). More information about identifying and troubleshooting network driver related issues can be found at Red Hat Enterprise Linux Network Performance Tuning Guide. system.softnet_stat ENTROPY Entropy, is a pool of random numbers (/dev/random) that is mainly used in cryptography. If the pool of entropy gets empty, processes requiring random numbers may run a lot slower (it depends on the interface each program uses), waiting for the pool to be replenished. Ideally a system with high entropy demands should have a hardware device for that purpose (TPM is one such device). There are also several software-only options you may install, like haveged, although these are generally useful only in servers. system.entropy UPTIME system.uptime IPC SEMAPHORES system.ipc_semaphores system.ipc_semaphore_arrays IPC SHARED MEMORY system.shared_memory_segments system.shared_memory_bytes -------------------------------------------------------------------------------- CPUS Detailed information for each CPU of the system. A summary of the system for all CPUs can be found at the System Overview section. UTILIZATION cpu.cpu0 INTERRUPTS cpu.cpu0_interrupts SOFTIRQS cpu.cpu0_softirqs SOFTNET Statistics for per CPUs core SoftIRQs related to network receive work. Total for all CPU cores can be found at System / softnet statistics. processed states the number of packets processed, dropped is the number packets dropped because the network device backlog was full (to fix them on Linux use sysctl to increase net.core.netdev_max_backlog), squeezed is the number of packets dropped because the network device budget ran out (to fix them on Linux use sysctl to increase net.core.netdev_budget and/or net.core.netdev_budget_usecs). More information about identifying and troubleshooting network driver related issues can be found at Red Hat Enterprise Linux Network Performance Tuning Guide. cpu.cpu0_softnet_stat CPUIDLE cpu.cpu0_cpuidle -------------------------------------------------------------------------------- MEMORY Detailed information about the memory management of the system. SYSTEM Available Memory is estimated by the kernel, as the amount of RAM that can be used by userspace processes, without causing swapping. mem.available Committed Memory, is the sum of all memory which has been allocated by processes. mem.committed A page fault is a type of interrupt, called trap, raised by computer hardware when a running program accesses a memory page that is mapped into the virtual address space, but not actually loaded into main memory. If the page is loaded in memory at the time the fault is generated, but is not marked in the memory management unit as being loaded in memory, then it is called a minor or soft page fault. A major page fault is generated when the system needs to load the memory page from disk or swap memory. mem.pgfaults KERNEL Dirty is the amount of memory waiting to be written to disk. Writeback is how much memory is actively being written to disk. mem.writeback The total amount of memory being used by the kernel. Slab is the amount of memory used by the kernel to cache data structures for its own use. KernelStack is the amount of memory allocated for each task done by the kernel. PageTables is the amount of memory dedicated to the lowest level of page tables (A page table is used to turn a virtual address into a physical memory address). VmallocUsed is the amount of memory being used as virtual address space. mem.kernel SLAB Reclaimable is the amount of memory which the kernel can reuse. Unreclaimable can not be reused even when the kernel is lacking memory. mem.slab HUGEPAGES Hugepages is a feature that allows the kernel to utilize the multiple page size capabilities of modern hardware architectures. The kernel creates multiple pages of virtual memory, mapped from both physical RAM and swap. There is a mechanism in the CPU architecture called "Translation Lookaside Buffers" (TLB) to manage the mapping of virtual memory pages to actual physical memory addresses. The TLB is a limited hardware resource, so utilizing a large amount of physical memory with the default page size consumes the TLB and adds processing overhead. By utilizing Huge Pages, the kernel is able to create pages of much larger sizes, each page consuming a single resource in the TLB. Huge Pages are pinned to physical RAM and cannot be swapped/paged out. Transparent HugePages (THP) is backing virtual memory with huge pages, supporting automatic promotion and demotion of page sizes. It works for all applications for anonymous memory mappings and tmpfs/shmem. mem.transparent_hugepages -------------------------------------------------------------------------------- DISKS Charts with performance information for all the system disks. Special care has been given to present disk performance metrics in a way compatible with iostat -x. netdata by default prevents rendering performance charts for individual partitions and unmounted virtual disks. Disabled charts can still be enabled by configuring the relative settings in the netdata configuration file. /MNT/HC VOLUME 3989981 disk.sdb disk.sdb disk_util.sdb Amount of data transferred to and from disk. disk.sdb Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.sdb Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.sdb Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.sdb The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.sdb The average I/O operation size. disk_avgsz.sdb The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.sdb The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk. disk_mops.sdb The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.sdb Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._mnt_hc_volume_3989981 inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._mnt_hc_volume_3989981 /MNT/HC VOLUME 16223457 disk.sdc disk.sdc disk_util.sdc Amount of data transferred to and from disk. disk.sdc Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.sdc I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.sdc Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.sdc Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.sdc The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.sdc The average I/O operation size. disk_avgsz.sdc The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.sdc The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk. disk_mops.sdc The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.sdc Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._mnt_hc_volume_16223457 inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._mnt_hc_volume_16223457 SDA disk.sda disk.sda disk_util.sda Amount of data transferred to and from disk. disk.sda Completed disk I/O operations. Keep in mind the number of operations requested might be higher, since the system is able to merge adjacent to each other (see merged operations chart). disk_ops.sda I/O operations currently in progress. This metric is a snapshot - it is not an average over the last interval. disk_qops.sda Backlog is an indication of the duration of pending disk operations. On every I/O event the system is multiplying the time spent doing I/O since the last update of this field with the number of pending operations. While not accurate, this metric can provide an indication of the expected completion time of the operations in progress. disk_backlog.sda Disk Utilization measures the amount of time the disk was busy with something. This is not related to its performance. 100% means that the system always had an outstanding operation on the disk. Keep in mind that depending on the underlying technology of the disk, 100% here may or may not be an indication of congestion. disk_util.sda The average time for I/O requests issued to the device to be served. This includes the time spent by the requests in queue and the time spent servicing them. disk_await.sda The average I/O operation size. disk_avgsz.sda The average service time for completed I/O operations. This metric is calculated using the total busy time of the disk and the number of completed operations. If the disk is able to execute multiple parallel operations the reporting average service time will be misleading. disk_svctm.sda The number of merged disk operations. The system is able to merge adjacent I/O operations, for example two 4KB reads can become one 8KB read before given to disk. disk_mops.sda The sum of the duration of all completed I/O operations. This number can exceed the interval if the disk is able to execute I/O operations in parallel. disk_iotime.sda / Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._ inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._ /DEV Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._dev inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._dev /DEV/SHM Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._dev_shm inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._dev_shm /RUN Disk space utilization. reserved for root is automatically reserved by the system to prevent the root user from getting out of space. disk_space._run inodes (or index nodes) are filesystem objects (e.g. files and directories). On many types of file system implementations, the maximum number of inodes is fixed at filesystem creation, limiting the maximum number of files the filesystem can hold. It is possible for a device to run out of inodes. When this happens, new files cannot be created on the device, even though there may be free space available. disk_inodes._run -------------------------------------------------------------------------------- NETWORKING STACK Metrics for the networking stack of the system. These metrics are collected from /proc/net/netstat, apply to both IPv4 and IPv6 traffic and are related to operation of the kernel networking stack. TCP TCP connection aborts. baddata (TCPAbortOnData) happens while the connection is on FIN_WAIT1 and the kernel receives a packet with a sequence number beyond the last one for this connection - the kernel responds with RST (closes the connection). userclosed (TCPAbortOnClose) happens when the kernel receives data on an already closed connection and responds with RST. nomemory (TCPAbortOnMemory happens when there are too many orphaned sockets (not attached to an fd) and the kernel has to drop a connection - sometimes it will send an RST, sometimes it won't. timeout (TCPAbortOnTimeout) happens when a connection times out. linger (TCPAbortOnLinger) happens when the kernel killed a socket that was already closed by the a... TCP connection aborts. baddata (TCPAbortOnData) happens while the connection is on FIN_WAIT1 and the kernel receives a packet with a sequence number beyond the last one for this connection - the kernel responds with RST (closes the connection). userclosed (TCPAbortOnClose) happens when the kernel receives data on an already closed connection and responds with RST. nomemory (TCPAbortOnMemory happens when there are too many orphaned sockets (not attached to an fd) and the kernel has to drop a connection - sometimes it will send an RST, sometimes it won't. timeout (TCPAbortOnTimeout) happens when a connection times out. linger (TCPAbortOnLinger) happens when the kernel killed a socket that was already closed by the application and lingered around for long enough. failed (TCPAbortFailed) happens when the kernel attempted to send an RST but failed because there was no memory available. show more information ip.tcpconnaborts The SYN queue of the kernel tracks TCP handshakes until connections get fully established. It overflows when too many incoming TCP connection requests hang in the half-open state and the server is not configured to fall back to SYN cookies*. Overflows are usually caused by SYN flood DoS attacks (i.e. someone sends lots of SYN packets and never completes the handshakes). drops (or TcpExtTCPReqQFullDrop) is the number of connections dropped because the SYN queue was full and SYN cookies were disabled. cookies (or TcpExtTCPReqQFullDoCookies) is the number of SYN cookies sent because the SYN queue was full. ip.tcp_syn_queue The accept queue of the kernel holds the fully established TCP connections, waiting to be handled by the listening application. overflows (or ListenOverflows) is the number of established connections that could not be handled because the receive queue of the listening application was full. drops (or ListenDrops) is the number of incoming connections that could not be handled, including SYN floods, overflows, out of memory, security issues, no route to destination, reception of related ICMP messages, socket is broadcast or multicast. ip.tcp_accept_queue ip.tcpreorders ip.tcpofo ip.tcpsyncookies ECN Explicit Congestion Notification (ECN) is a TCP extension that allows end-to-end notification of network congestion without dropping packets. ECN is an optional feature that may be used between two ECN-enabled endpoints when the underlying network infrastructure also supports it. ip.ecnpkts -------------------------------------------------------------------------------- IPV4 NETWORKING Metrics for the IPv4 stack of the system. Internet Protocol version 4 (IPv4) is the fourth version of the Internet Protocol (IP). It is one of the core protocols of standards-based internetworking methods in the Internet. IPv4 is a connectionless protocol for use on packet-switched networks. It operates on a best effort delivery model, in that it does not guarantee delivery, nor does it assure proper sequencing or avoidance of duplicate delivery. These aspects, including data integrity, are addressed by an upper layer transport protocol, such as the Transmission Control Protocol (TCP). SOCKETS ipv4.sockstat_sockets PACKETS ipv4.packets ERRORS ipv4.errors ICMP ipv4.icmp ipv4.icmp_errors ipv4.icmpmsg TCP The number of established TCP connections (known as CurrEstab). This is a snapshot of the established connections at the time of measurement (i.e. a connection established and a connection disconnected within the same iteration will not affect this metric). ipv4.tcpsock ipv4.sockstat_tcp_sockets ipv4.tcppackets active or ActiveOpens is the number of outgoing TCP connections attempted by this host. passive or PassiveOpens is the number of incoming TCP connections accepted by this host. ipv4.tcpopens InErrs is the number of TCP segments received in error (including header too small, checksum errors, sequence errors, bad packets - for both IPv4 and IPv6). InCsumErrors is the number of TCP segments received with checksum errors (for both IPv4 and IPv6). RetransSegs is the number of TCP segments retransmitted. ipv4.tcperrors EstabResets is the number of established connections resets (i.e. connections that made a direct transition from ESTABLISHED or CLOSE_WAIT to CLOSED). OutRsts is the number of TCP segments sent, with the RST flag set (for both IPv4 and IPv6). AttemptFails is the number of times TCP connections made a direct transition from either SYN_SENT or SYN_RECV to CLOSED, plus the number of times TCP connections made a direct transition from the SYN_RECV to LISTEN. TCPSynRetrans shows retries for new outbound TCP connections, which can indicate general connectivity issues or backlog on the remote host. ipv4.tcphandshake ipv4.sockstat_tcp_mem UDP ipv4.sockstat_udp_sockets ipv4.udppackets ipv4.udperrors ipv4.sockstat_udp_mem FRAGMENTS ipv4.fragsin -------------------------------------------------------------------------------- IPV6 NETWORKING Metrics for the IPv6 stack of the system. Internet Protocol version 6 (IPv6) is the most recent version of the Internet Protocol (IP), the communications protocol that provides an identification and location system for computers on networks and routes traffic across the Internet. IPv6 was developed by the Internet Engineering Task Force (IETF) to deal with the long-anticipated problem of IPv4 address exhaustion. IPv6 is intended to replace IPv4. PACKETS ipv6.packets ipv6.ect ERRORS ipv6.errors TCP6 ipv6.sockstat6_tcp_sockets UDP6 ipv6.sockstat6_udp_sockets ipv6.udppackets ipv6.udperrors MULTICAST6 ipv6.mcast ipv6.mcastpkts ICMP6 ipv6.icmp ipv6.icmperrors ipv6.icmpechos ipv6.icmpneighbor ipv6.icmpmldv2 ipv6.icmptypes -------------------------------------------------------------------------------- NETWORK INTERFACES Performance metrics for network interfaces. BR-2740AECB97C3 net.br-2740aecb97c3 net.br-2740aecb97c3 net.br-2740aecb97c3 net_packets.br-2740aecb97c3 ETH0 net.eth0 net.eth0 net.eth0 net_packets.eth0 -------------------------------------------------------------------------------- FIREWALL (NETFILTER) Performance metrics of the netfilter components. CONNECTION TRACKER Netfilter Connection Tracker performance metrics. The connection tracker keeps track of all connections of the machine, inbound and outbound. It works by keeping a database with all open connections, tracking network and address translation and connection expectations. netfilter.conntrack_sockets netfilter.conntrack_new netfilter.conntrack_changes netfilter.conntrack_expect netfilter.conntrack_errors netfilter.conntrack_search -------------------------------------------------------------------------------- SYSTEMD SERVICES Resources utilization of systemd services. netdata monitors all systemd services via CGROUPS (the resources accounting used by containers). CPU services.cpu MEM services.mem_usage SWAP services.swap_usage DISK services.throttle_io_read services.throttle_io_write services.throttle_io_ops_read services.throttle_io_ops_write -------------------------------------------------------------------------------- APPLICATIONS Per application statistics are collected using netdata's apps.plugin. This plugin walks through all processes and aggregates statistics for applications of interest, defined in /etc/netdata/apps_groups.conf, which can be edited by running $ /etc/netdata/edit-config apps_groups.conf (the default is here). The plugin internally builds a process tree (much like ps fax does), and groups processes together (evaluating both child and parent processes) so that the result is always a chart with a predefined set of dimensions (of course, only application groups found running are reported). The reported values are compatible with top, although the netdata plugin counts also the resources of exited children (unlike top which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU apps.cpu apps.cpu_user apps.cpu_system DISK apps.preads apps.pwrites apps.lreads apps.lwrites apps.files MEM Real memory (RAM) used by applications. This does not include shared memory. apps.mem Virtual memory allocated by applications. Please check this article for more information. apps.vmem apps.minor_faults PROCESSES apps.threads apps.processes Carried over process group uptime since the Netdata restart. The period of time within which at least one process in the group was running. apps.uptime apps.uptime_min apps.uptime_avg apps.uptime_max apps.pipes SWAP apps.swap apps.major_faults NET apps.sockets EBPF SYSCALL apps.file_open apps.file_closed apps.file_deleted apps.vfs_write_call apps.vfs_read_call apps.vfs_write_bytes apps.vfs_read_bytes apps.process_create apps.thread_create apps.task_close EBPF NET apps.bandwidth_sent apps.bandwidth_recv -------------------------------------------------------------------------------- USER GROUPS Per user group statistics are collected using netdata's apps.plugin. This plugin walks through all processes and aggregates statistics per user group. The reported values are compatible with top, although the netdata plugin counts also the resources of exited children (unlike top which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU groups.cpu groups.cpu_user groups.cpu_system DISK groups.preads groups.pwrites groups.lreads groups.lwrites groups.files MEM Real memory (RAM) used per user group. This does not include shared memory. groups.mem Virtual memory allocated per user group since the Netdata restart. Please check this article for more information. groups.vmem groups.minor_faults PROCESSES groups.threads groups.processes Carried over process group uptime. The period of time within which at least one process in the group was running. groups.uptime groups.uptime_min groups.uptime_avg groups.uptime_max groups.pipes SWAP groups.swap groups.major_faults NET groups.sockets -------------------------------------------------------------------------------- USERS Per user statistics are collected using netdata's apps.plugin. This plugin walks through all processes and aggregates statistics per user. The reported values are compatible with top, although the netdata plugin counts also the resources of exited children (unlike top which shows only the resources of the currently running processes). So for processes like shell scripts, the reported values include the resources used by the commands these scripts run within each timeframe. CPU users.cpu users.cpu_user users.cpu_system DISK users.preads users.pwrites users.lreads users.lwrites users.files MEM Real memory (RAM) used per user. This does not include shared memory. users.mem Virtual memory allocated per user. Please check this article for more information. users.vmem users.minor_faults PROCESSES users.threads users.processes Carried over process group uptime since the Netdata restart. The period of time within which at least one process in the group was running. users.uptime users.uptime_min users.uptime_avg users.uptime_max users.pipes SWAP users.swap users.major_faults NET users.sockets -------------------------------------------------------------------------------- EBPF Monitor system calls, internal functions, bytes read, bytes written and errors using eBPF. FILE Calls for internal functions on Linux kernel. The open dimension is attached to the kernel internal function do_sys_open, which is the common function called from open(2) and openat(2). The close dimension is attached to the function __close_fd, which is called from system call close(2). ebpf.file_descriptor VFS This chart does not show all events that remove files from the file system, because file systems can create their own functions to remove files, it shows calls for the function vfs_unlink. ebpf.deleted_objects Successful or failed calls to functions vfs_read and vfs_write. This chart may not show all file system events if it uses other functions to store data on disk. ebpf.io Total of bytes read or written with success using the functions vfs_read and vfs_write. ebpf.io_bytes PROCESS Number of times that the function do_fork is called to create a new task, which is the common name used to define process and tasks inside the kernel. Netdata identifies the threads by couting the number of calls for sys_clone that has the flag CLONE_THREAD set. ebpf.process_thread Calls for the functions responsible for closing (do_exit) and releasing (release_task) tasks. ebpf.exit Difference between the number of process created and the number of threads created per period(process dimension), it also shows the number of possible zombie process running on system. ebpf.process_status -------------------------------------------------------------------------------- DRONE Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_drone.cpu cgroup_drone.mem_usage_limit cgroup_drone.throttle_io cgroup_drone.throttle_io cgroup_drone.net_eth0 cgroup_drone.net_eth0 CPU cgroup_drone.cpu cgroup_drone.cpu_per_core MEM cgroup_drone.mem_usage_limit cgroup_drone.mem_usage cgroup_drone.mem cgroup_drone.writeback cgroup_drone.mem_activity cgroup_drone.pgfaults DISK cgroup_drone.throttle_io cgroup_drone.throttle_serviced_ops NET ETH0 cgroup_drone.net_eth0 cgroup_drone.net_packets_eth0 -------------------------------------------------------------------------------- GITEA Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_gitea.cpu cgroup_gitea.mem_usage_limit cgroup_gitea.throttle_io cgroup_gitea.throttle_io cgroup_gitea.net_eth0 cgroup_gitea.net_eth0 CPU cgroup_gitea.cpu cgroup_gitea.cpu_per_core MEM cgroup_gitea.mem_usage_limit cgroup_gitea.mem_usage cgroup_gitea.mem cgroup_gitea.writeback cgroup_gitea.mem_activity cgroup_gitea.pgfaults DISK cgroup_gitea.throttle_io cgroup_gitea.throttle_serviced_ops NET ETH0 cgroup_gitea.net_eth0 cgroup_gitea.net_packets_eth0 -------------------------------------------------------------------------------- RUNNER Container resource utilization metrics. Netdata reads this information from cgroups (abbreviated from control groups), a Linux kernel feature that limits and accounts resource usage (CPU, memory, disk I/O, network, etc.) of a collection of processes. cgroups together with namespaces (that offer isolation between processes) provide what we usually call: containers. cgroup_runner.cpu cgroup_runner.mem_usage_limit cgroup_runner.throttle_io cgroup_runner.throttle_io cgroup_runner.net_eth0 cgroup_runner.net_eth0 CPU cgroup_runner.cpu cgroup_runner.cpu_per_core MEM cgroup_runner.mem_usage_limit cgroup_runner.mem_usage cgroup_runner.mem cgroup_runner.writeback cgroup_runner.mem_activity cgroup_runner.pgfaults DISK cgroup_runner.throttle_io cgroup_runner.throttle_serviced_ops NET ETH0 cgroup_runner.net_eth0 cgroup_runner.net_packets_eth0 -------------------------------------------------------------------------------- WEB LOG NGINX Information extracted from a server log file. web_log plugin incrementally parses the server log file to provide, in real-time, a break down of key server performance metrics. For web servers, an extended log file format may optionally be used (for nginx and apache) offering timing information and bandwidth for both requests and responses. web_log plugin may also be configured to provide a break down of requests per URL pattern (check /etc/netdata/python.d/web_log.conf). REQUESTS web_log_nginx.requests web_log_nginx.excluded_requests web_log_nginx.requests_by_type RESPONSES web_log_nginx.responses_by_status_code_class web_log_nginx.status_code_class_2xx_responses web_log_nginx.status_code_class_3xx_responses web_log_nginx.status_code_class_4xx_responses web_log_nginx.status_code_class_5xx_responses BANDWIDTH Bandwidth of requests (received) and responses (sent). received requires an extended log format (without it, the web server log does not have this information). This chart may present unusual spikes, since the bandwidth is accounted at the time the log line is saved by the web server, even if the time needed to serve it spans across a longer duration. We suggest to use QoS (e.g. FireQOS) for accurate accounting of the web server bandwidth. web_log_nginx.bandwidth TIMINGS Web server response timings - the time the web server needed to prepare and respond to requests. This requires an extended log format and its meaning is web server specific. For most web servers this accounts the time from the reception of a complete request, to the dispatch of the last byte of the response. So, it includes the network delays of responses, but it does not include the network delays of requests. web_log_nginx.request_processing_time CLIENT web_log_nginx.current_poll_uniq_clients HTTP METHOD web_log_nginx.requests_by_http_method HTTP VERSION web_log_nginx.requests_by_http_version IP PROTO web_log_nginx.requests_by_ip_proto -------------------------------------------------------------------------------- NETDATA MONITORING Performance metrics for the operation of netdata itself and its plugins. NETDATA netdata.net netdata.server_cpu netdata.clients netdata.requests The netdata API response time measures the time netdata needed to serve requests. This time includes everything, from the reception of the first byte of a request, to the dispatch of the last byte of its reply, therefore it includes all network latencies involved (i.e. a client over a slow network will influence these metrics). netdata.response_time netdata.compression_ratio QUERIES netdata.queries netdata.db_points DBENGINE netdata.dbengine_compression_ratio netdata.page_cache_hit_ratio netdata.page_cache_stats netdata.dbengine_long_term_page_stats netdata.dbengine_io_throughput netdata.dbengine_io_operations netdata.dbengine_global_errors netdata.dbengine_global_file_descriptors netdata.dbengine_ram CGROUPS netdata.plugin_cgroups_cpu PROC netdata.plugin_proc_cpu netdata.plugin_proc_modules WEB netdata.web_thread1_cpu STATSD netdata.plugin_statsd_charting_cpu netdata.plugin_statsd_collector1_cpu netdata.statsd_metrics netdata.statsd_useful_metrics netdata.statsd_events netdata.statsd_reads netdata.statsd_bytes netdata.statsd_packets netdata.tcp_connects netdata.tcp_connected netdata.private_charts DISKSPACE netdata.plugin_diskspace netdata.plugin_diskspace_dt TC.HELPER netdata.plugin_tc_cpu netdata.plugin_tc_time APPS.PLUGIN netdata.apps_cpu netdata.apps_sizes netdata.apps_fix netdata.apps_children_fix GO.D netdata.execution_time_of_web_log_nginx ACLK STATS This chart shows if ACLK was online during entirety of the sample duration. netdata.aclk_status This chart shows how many queries were added for ACLK_query thread to process and how many it was actually able to process. netdata.aclk_query_per_second netdata.aclk_write_q netdata.aclk_read_q netdata.aclk_cloud_req ACLK netdata.aclk_query_time netdata.aclk_query_threads -------------------------------------------------------------------------------- * System Overview * cpu * load * disk * ram * network * processes * idlejitter * interrupts * softirqs * softnet * entropy * uptime * ipc semaphores * ipc shared memory * CPUs * utilization * interrupts * softirqs * softnet * cpuidle * Memory * system * kernel * slab * hugepages * Disks * /mnt/HC Volume 3989981 * /mnt/HC Volume 16223457 * sda * / * /dev * /dev/shm * /run * Networking Stack * tcp * ecn * IPv4 Networking * sockets * packets * errors * icmp * tcp * udp * fragments * IPv6 Networking * packets * errors * tcp6 * udp6 * multicast6 * icmp6 * Network Interfaces * br-2740aecb97c3 * eth0 * Firewall (netfilter) * connection tracker * systemd Services * cpu * mem * swap * disk * Applications * cpu * disk * mem * processes * swap * net * ebpf syscall * ebpf net * User Groups * cpu * disk * mem * processes * swap * net * Users * cpu * disk * mem * processes * swap * net * eBPF * File * VFS * Process * drone * cpu * mem * disk * net eth0 * gitea * cpu * mem * disk * net eth0 * runner * cpu * mem * disk * net eth0 * web log nginx * requests * responses * bandwidth * timings * client * http method * http version * ip proto * Netdata Monitoring * netdata * queries * dbengine * cgroups * proc * web * statsd * diskspace * tc.helper * apps.plugin * go.d * aclk stats * aclk * Add more charts * Add more alarms * Every 2 seconds, Netdata collects 2,223 metrics on esfi-dev-prod, presents them in 313 charts and monitors them with 157 alarms. netdata v1.25.0-89-nightly Terms and conditions Privacy Policy Netdata Copyright 2018, Netdata, Inc. Copyright 2016-2018, Costa Tsaousis. Released under GPL v3 or later. Netdata uses third party tools. XSS PROTECTION This dashboard is about to render data from server: To protect your privacy, the dashboard will check all data transferred for cross site scripting (XSS). This is CPU intensive, so your browser might be a bit slower. If you trust the remote server, you can disable XSS protection. In this case, any remote dashboard decoration code (javascript) will also run. If you don't trust the remote server, you should keep the protection on. The dashboard will run slower and remote dashboard decoration code will not run, but better be safe than sorry... Keep protecting me I don't need this, the server is mine × PRINT THIS NETDATA DASHBOARD netdata dashboards cannot be captured, since we are lazy loading and hiding all but the visible charts. To capture the whole page with all the charts rendered, a new browser window will pop-up that will render all the charts at once. The new browser window will maintain the current pan and zoom settings of the charts. So, align the charts before proceeding. This process will put some CPU and memory pressure on your browser. For the netdata server, we will sequencially download all the charts, to avoid congesting network and server resources. Please, do not print netdata dashboards on paper! Print Close × PREPARING DASHBOARD FOR PRINTING... Please wait while we initialize and render all the charts on the dashboard. The print dialog will appear as soon as we finish rendering the page. × IMPORT A NETDATA SNAPSHOT netdata can export and import dashboard snapshots. Any netdata can import the snapshot of any other netdata. The snapshots are not uploaded to a server. They are handled entirely by your web browser, on your computer. Click here to select the netdata snapshot file to import Browse for a snapshot file (or drag it and drop it here), then click Import to render it. FilenameHostnameOrigin URLCharts InfoSnapshot InfoTime RangeComments Snapshot files contain both data and javascript code. Make sure you trust the files you import! Import Close × EXPORT A SNAPSHOT Please wait while we collect all the dashboard data... Select the desired resolution of the snapshot. This is the seconds of data per point. Filename Compression * Select Compression * * uncompressed * * pako.deflate (gzip, binary) * pako.deflate.base64 (gzip, ascii) * * lzstring.uri (LZ, ascii) * lzstring.utf16 (LZ, utf16) * lzstring.base64 (LZ, ascii) Comments Select snaphost resolution. This controls the size the snapshot file. The generated snapshot will include all charts of this dashboard, for the visible timeframe, so align, pan and zoom the charts as needed. The scroll position of the dashboard will also be saved. The snapshot will be downloaded as a file, to your computer, that can be imported back into any netdata dashboard (no need to import it back on this server). Snapshot files include all the information of the dashboard, including the URL of the origin server, its netdata unique ID, etc. So, if you share the snapshot file with third parties, they will be able to access the origin server, if this server is exposed on the internet. Snapshots are handled entirely by the web browser. The netdata servers are not aware of them. Export Cancel × WELCOME TO THE WORLD OF NETDATA if there is a metric for something, we want it visualised and we want this visualisation to be real-time, efficient and awesome netdata is a new way to monitor your systems and applications, to get real-time insights of what is really happening and what affects performance. It is carefully optimised to be a real-time system, without interfering in any way, to the core function of your systems. netdata has been designed to monitor massive amounts of metrics, per server, per second. When installed, it might come up with 1k to 3k metrics, but we have been testing it with 100k metrics, all collected per second, and still the cpu utilisation remained negligible. We have also tried to give each metric, a meaning, a context. We have grouped and categorized all metrics into meaningful charts, providing a better understanding of the underlying technologies and mechanisms. netdata is free, open-source software. If you decide to use it, it is important to give netdata a star at GitHub. Enjoy real-time performance monitoring! Costa Tsaousis Close × DASHBOARD HELP DYGRAPHS (LINE, AREA AND STACKED AREA CHARTS) * Mouse Interface * Touch Interface MOUSE OVER / HOVER Mouse over on a chart to show, at its legend, the values for the timestamp under the mouse (the chart will also highlight the point at the chart). All the other visible charts will also show and highlight their values for the same timestamp. -------------------------------------------------------------------------------- DRAG CHART CONTENTS Drag the contents of a chart, by pressing the left mouse button and moving the mouse, to pan it horizontally. All the charts will follow soon after you let the chart alone (this little delay is by design: it speeds up your browser and lets you focus on what you are exploring). Once a chart is panned, auto refreshing stops for all charts. To enable it again, double click a panned chart. -------------------------------------------------------------------------------- DOUBLE CLICK Double Click a chart to reset all the charts to their default auto-refreshing state. -------------------------------------------------------------------------------- SHIFT + DRAG While pressing the SHIFT key, press the left mouse button on the contents of a chart and move the mouse to select an area, to zoom in. The other charts will follow too. Zooming is performed in two phases: * The already loaded chart contents are zoomed (low resolution) * New data are transferred from the netdata server, to refresh the chart with possibly more detail. Once a chart is zoomed, auto refreshing stops for all charts. To enable it again, double click a zoomed chart. -------------------------------------------------------------------------------- HIGHLIGHT TIMEFRAME While pressing the ALT key, press the left mouse button on the contents of a chart and move the mouse to select an area. The selected are will be highlighted on all charts. -------------------------------------------------------------------------------- SHIFT + MOUSE WHEEL While pressing the SHIFT key and the mouse pointer is over the contents of a chart, scroll the mouse wheel to zoom in or out. This kind of zooming is aligned to center below the mouse pointer. The other charts will follow too. Once a chart is zoomed, auto refreshing stops for all charts. To enable it again, double click a zoomed chart. -------------------------------------------------------------------------------- LEGEND OPERATIONS Click on the label or value of a dimension, will select / un-select this dimension. You can press any of the SHIFT or CONTROL keys and then click on legend labels or values, to select / un-select multiple dimensions. SINGLE TAP Single Tap on the contents of a chart to show, at its legend, the values for the timestamp tapped (the chart will also highlight the point at the chart). All the other visible charts will also show and highlight their values for the same timestamp. -------------------------------------------------------------------------------- DRAG CHART CONTENTS Touch and Drag the contents of a chart to pan it horizontally. All the charts will follow soon after you let the chart alone (this little delay is by design: it speeds up your browser and lets you focus on what you are exploring). Once a chart is panned, auto refreshing stops for all charts. To enable it again, double tap a panned chart. -------------------------------------------------------------------------------- DOUBLE TAP Double tap a chart to reset all the charts to their default auto-refreshing state. -------------------------------------------------------------------------------- ZOOM (DOES NOT WORK ON FIREFOX AND IE/EDGE) With two fingers, zoom in or out. Once a chart is zoomed, auto refreshing stops for all charts. To enable it again, double click a zoomed chart. -------------------------------------------------------------------------------- LEGEND OPERATIONS Tap on the label or value of a dimension, will select / un-select this dimension. Close × NETDATA ALARMS * Active * All * Log loading... loading... loading... Close × NETDATA DASHBOARD OPTIONS These are browser settings. Each viewer has its own. They do not affect the operation of your netdata server. Settings take effect immediately and are saved permanently to browser local storage (except the refresh on focus / always option). To reset all options (including charts sizes) to their defaults, click here. * Performance * Synchronization * Visual * Locale On FocusAlways When to refresh the charts? When set to On Focus, the charts will stop being updated if the page / tab does not have the focus of the user. When set to Always, the charts will always be refreshed. Set it to On Focus it to lower the CPU requirements of the browser (and extend the battery of laptops and tablets) when this page does not have your focus. Set to Always to work on another window (i.e. change the settings of something) and have the charts auto-refresh in this window. Non ZeroAll Which dimensions to show? When set to Non Zero, dimensions that have all their values (within the current view) set to zero will not be transferred from the netdata server (except if all dimensions of the chart are zero, in which case this setting does nothing - all dimensions are transferred and shown). When set to All, all dimensions will always be shown. Set it to Non Zero to lower the data transferred between netdata and your browser, lower the CPU requirements of your browser (fewer lines to draw) and increase the focus on the legends (fewer entries at the legends). DestroyHide How to handle hidden charts? When set to Destroy, charts that are not in the current viewport of the browser (are above, or below the visible area of the page), will be destroyed and re-created if and when they become visible again. When set to Hide, the not-visible charts will be just hidden, to simplify the DOM and speed up your browser. Set it to Destroy, to lower the memory requirements of your browser. Set it to Hide for faster restoration of charts on page scrolling. AsyncSync Page scroll handling? When set to Sync, charts will be examined for their visibility immediately after scrolling. On slow computers this may impact the smoothness of page scrolling. To update the page when scrolling ends, set it to Async. Set it to Sync for immediate chart updates when scrolling. Set it to Async for smoother page scrolling on slower computers. ParallelSequential Which chart refresh policy to use? When set to parallel, visible charts are refreshed in parallel (all queries are sent to netdata server in parallel) and are rendered asynchronously. When set to sequential charts are refreshed one after another. Set it to parallel if your browser can cope with it (most modern browsers do), set it to sequential if you work on an older/slower computer. ResyncBest Effort Shall we re-sync chart refreshes? When set to Resync, the dashboard will attempt to re-synchronize all the charts so that they are refreshed concurrently. When set to Best Effort, each chart may be refreshed with a little time difference to the others. Normally, the dashboard starts refreshing them in parallel, but depending on the speed of your computer and the network latencies, charts start having a slight time difference. Setting this to Resync will attempt to re-synchronize the charts on every update. Setting it to Best Effort may lower the pressure on your browser and the network. SyncDon't Sync Sync hover selection on all charts? When enabled, a selection on one chart will automatically select the same time on all other visible charts and the legends of all visible charts will be updated to show the selected values. When disabled, only the chart getting the user's attention will be selected. Enable it to get better insights of the data. Disable it if you are on a very slow computer that cannot actually do it. SyncDon't Sync Sync pan and zoom on all charts? When enabled, pan and zoom operations on a chart will be replicated to all charts (even the ones that are not currently visible - of course only when they will become visible). When disabled, pan and zoom operations will not be propagated to other charts. DarkWhite Which theme to use? Netdata comes with two themes: Dark (the default) and White. Switching this will reload the dashboard. Help MeNo Help Do you need help? Netdata can show some help in some areas to help you use the dashboard. If all these balloons bother you, disable them using this switch. Switching this will reload the dashboard. PadDon't Pad Enable data padding when panning and zooming? When set to Pad the charts will be padded with more data, both before and after the visible area, thus giving the impression the whole database is loaded. This padding will happen only after the first pan or zoom operation on the chart (initially all charts have only the visible data). When set to Don't Pad only the visible data will be transfered from the netdata server, even after the first pan and zoom operation. SmoothRough Enable Bézier lines on charts? When set to Smooth the charts libraries that support it, will plot smooth curves instead of simple straight lines to connect the points. Keep in mind dygraphs, the main charting library in netdata dashboards, can only smooth line charts. It cannot smooth area or stacked charts. When set to Rough, this setting can lower the CPU resources consumed by your browser. These settings are applied gradually, as charts are updated. To force them, refresh the dashboard now. Scale UnitsFixed Units Enable auto-scaling of select units? When set to Scale Units the values shown will dynamically be scaled (e.g. 1000 kilobits will be shown as 1 megabit). Netdata can auto-scale these original units: kilobits/s, kilobytes/s, KB/s, KB, MB, and GB. When set to Fixed Units all the values will be rendered using the original units maintained by the netdata server. CelsiusFahrenheit Which units to use for temperatures? Set the temperature units of the dashboard. TimeSeconds Convert seconds to time? When set to Time, charts that present seconds will show DDd:HH:MM:SS. When set to Seconds, the raw number of seconds will be presented. Your TimeServer Time Show browser local time or server time? When set to Your Time, the charts will use your browser local time. When set to Server Time the charts will use the server time. Set it to Your Time to have a common time-reference, no matter where the server is and which time zone it uses (all your dashboards will report your local time). Set it to Server Time when you need to compare netdata charts with server log files. Your browser time zone is: America/Vancouver. The server reported timezone is: Europe/Berlin (you can set this in netdata.conf [global].timezone). The current time zone on the dashboard is: unset, using browser default. Select Server Time Zone * Universal Time Coordinated (UTC) * Africa/Abidjan * Africa/Accra * Africa/Algiers * Africa/Bissau * Africa/Cairo * Africa/Casablanca * Africa/Ceuta * Africa/El_Aaiun * Africa/Johannesburg * Africa/Khartoum * Africa/Lagos * Africa/Maputo * Africa/Monrovia * Africa/Nairobi * Africa/Ndjamena * Africa/Tripoli * Africa/Tunis * Africa/Windhoek * America/Adak * America/Anchorage * America/Araguaina * America/Argentina/Buenos_Aires * America/Argentina/Catamarca * America/Argentina/Cordoba * America/Argentina/Jujuy * America/Argentina/La_Rioja * America/Argentina/Mendoza * America/Argentina/Rio_Gallegos * America/Argentina/Salta * America/Argentina/San_Juan * America/Argentina/San_Luis * America/Argentina/Tucuman * America/Argentina/Ushuaia * America/Asuncion * America/Atikokan * America/Bahia * America/Bahia_Banderas * America/Barbados * America/Belem * America/Belize * America/Blanc-Sablon * America/Boa_Vista * America/Bogota * America/Boise * America/Cambridge_Bay * America/Campo_Grande * America/Cancun * America/Caracas * America/Cayenne * America/Chicago * America/Chihuahua * America/Costa_Rica * America/Creston * America/Cuiaba * America/Curacao * America/Danmarkshavn * America/Dawson * America/Dawson_Creek * America/Denver * America/Detroit * America/Edmonton * America/Eirunepe * America/El_Salvador * America/Fortaleza * America/Fort_Nelson * America/Glace_Bay * America/Godthab * America/Goose_Bay * America/Grand_Turk * America/Guatemala * America/Guayaquil * America/Guyana * America/Halifax * America/Havana * America/Hermosillo * America/Indiana/Indianapolis * America/Indiana/Knox * America/Indiana/Marengo * America/Indiana/Petersburg * America/Indiana/Tell_City * America/Indiana/Vevay * America/Indiana/Vincennes * America/Indiana/Winamac * America/Inuvik * America/Iqaluit * America/Jamaica * America/Juneau * America/Kentucky/Louisville * America/Kentucky/Monticello * America/La_Paz * America/Lima * America/Los_Angeles * America/Maceio * America/Managua * America/Manaus * America/Martinique * America/Matamoros * America/Mazatlan * America/Menominee * America/Merida * America/Metlakatla * America/Mexico_City * America/Miquelon * America/Moncton * America/Monterrey * America/Montevideo * America/Nassau * America/New_York * America/Nipigon * America/Nome * America/Noronha * America/North_Dakota/Beulah * America/North_Dakota/Center * America/North_Dakota/New_Salem * America/Ojinaga * America/Panama * America/Pangnirtung * America/Paramaribo * America/Phoenix * America/Port-au-Prince * America/Port_of_Spain * America/Porto_Velho * America/Puerto_Rico * America/Punta_Arenas * America/Rainy_River * America/Rankin_Inlet * America/Recife * America/Regina * America/Resolute * America/Rio_Branco * America/Santarem * America/Santiago * America/Santo_Domingo * America/Sao_Paulo * America/Scoresbysund * America/Sitka * America/St_Johns * America/Swift_Current * America/Tegucigalpa * America/Thule * America/Thunder_Bay * America/Tijuana * America/Toronto * America/Vancouver * America/Whitehorse * America/Winnipeg * America/Yakutat * America/Yellowknife * Antarctica/Casey * Antarctica/Davis * Antarctica/DumontDUrville * Antarctica/Macquarie * Antarctica/Mawson * Antarctica/Palmer * Antarctica/Rothera * Antarctica/Syowa * Antarctica/Troll * Antarctica/Vostok * Asia/Almaty * Asia/Amman * Asia/Anadyr * Asia/Aqtau * Asia/Aqtobe * Asia/Ashgabat * Asia/Atyrau * Asia/Baghdad * Asia/Baku * Asia/Bangkok * Asia/Barnaul * Asia/Beirut * Asia/Bishkek * Asia/Brunei * Asia/Chita * Asia/Choibalsan * Asia/Colombo * Asia/Damascus * Asia/Dhaka * Asia/Dili * Asia/Dubai * Asia/Dushanbe * Asia/Famagusta * Asia/Gaza * Asia/Hebron * Asia/Ho_Chi_Minh * Asia/Hong_Kong * Asia/Hovd * Asia/Irkutsk * Asia/Jakarta * Asia/Jayapura * Asia/Jerusalem * Asia/Kabul * Asia/Kamchatka * Asia/Karachi * Asia/Kathmandu * Asia/Khandyga * Asia/Kolkata * Asia/Krasnoyarsk * Asia/Kuala_Lumpur * Asia/Kuching * Asia/Macau * Asia/Magadan * Asia/Makassar * Asia/Manila * Asia/Nicosia * Asia/Novokuznetsk * Asia/Novosibirsk * Asia/Omsk * Asia/Oral * Asia/Pontianak * Asia/Pyongyang * Asia/Qatar * Asia/Qyzylorda * Asia/Riyadh * Asia/Sakhalin * Asia/Samarkand * Asia/Seoul * Asia/Shanghai * Asia/Singapore * Asia/Srednekolymsk * Asia/Taipei * Asia/Tashkent * Asia/Tbilisi * Asia/Tehran * Asia/Thimphu * Asia/Tokyo * Asia/Tomsk * Asia/Ulaanbaatar * Asia/Urumqi * Asia/Ust-Nera * Asia/Vladivostok * Asia/Yakutsk * Asia/Yangon * Asia/Yekaterinburg * Asia/Yerevan * Atlantic/Azores * Atlantic/Bermuda * Atlantic/Canary * Atlantic/Cape_Verde * Atlantic/Faroe * Atlantic/Madeira * Atlantic/Reykjavik * Atlantic/South_Georgia * Atlantic/Stanley * Australia/Adelaide * Australia/Brisbane * Australia/Broken_Hill * Australia/Currie * Australia/Darwin * Australia/Eucla * Australia/Hobart * Australia/Lindeman * Australia/Lord_Howe * Australia/Melbourne * Australia/Perth * Australia/Sydney * Europe/Amsterdam * Europe/Andorra * Europe/Astrakhan * Europe/Athens * Europe/Belgrade * Europe/Berlin * Europe/Brussels * Europe/Bucharest * Europe/Budapest * Europe/Chisinau * Europe/Copenhagen * Europe/Dublin * Europe/Gibraltar * Europe/Helsinki * Europe/Istanbul * Europe/Kaliningrad * Europe/Kiev * Europe/Kirov * Europe/Lisbon * Europe/London * Europe/Luxembourg * Europe/Madrid * Europe/Malta * Europe/Minsk * Europe/Monaco * Europe/Moscow * Europe/Oslo * Europe/Paris * Europe/Prague * Europe/Riga * Europe/Rome * Europe/Samara * Europe/Saratov * Europe/Simferopol * Europe/Sofia * Europe/Stockholm * Europe/Tallinn * Europe/Tirane * Europe/Ulyanovsk * Europe/Uzhgorod * Europe/Vienna * Europe/Vilnius * Europe/Volgograd * Europe/Warsaw * Europe/Zaporozhye * Europe/Zurich * Indian/Chagos * Indian/Christmas * Indian/Cocos * Indian/Kerguelen * Indian/Mahe * Indian/Maldives * Indian/Mauritius * Indian/Reunion * Pacific/Apia * Pacific/Auckland * Pacific/Bougainville * Pacific/Chatham * Pacific/Chuuk * Pacific/Easter * Pacific/Efate * Pacific/Enderbury * Pacific/Fakaofo * Pacific/Fiji * Pacific/Funafuti * Pacific/Galapagos * Pacific/Gambier * Pacific/Guadalcanal * Pacific/Guam * Pacific/Honolulu * Pacific/Kiritimati * Pacific/Kosrae * Pacific/Kwajalein * Pacific/Majuro * Pacific/Marquesas * Pacific/Nauru * Pacific/Niue * Pacific/Norfolk * Pacific/Noumea * Pacific/Pago_Pago * Pacific/Palau * Pacific/Pitcairn * Pacific/Pohnpei * Pacific/Port_Moresby * Pacific/Rarotonga * Pacific/Tahiti * Pacific/Tarawa * Pacific/Tongatapu * Pacific/Wake * Pacific/Wallis Close × UPDATE CHECK Your netdata version: v1.25.0-89-nightly Failed to get the latest netdata version. You can always get the latest netdata from its github page. -------------------------------------------------------------------------------- For progress reports and key netdata updates: Join the Netdata Community You can also follow netdata on twitter, follow netdata on facebook, or watch netdata on github. Check Now Close × SIGN IN Signing-in to netdata.cloud will synchronize the list of your netdata monitored nodes known at registry . This may include server hostnames, urls and identification GUIDs. After you upgrade all your netdata servers, your private registry will not be needed any more. Are you sure you want to proceed? Cancel Sign In × SYNCHRONIZE NETDATA.CLOUD WITH REGISTRY? You are about to synchronize your netdata.cloud account with data from the registry at . This may include server hostnames, urls and identification GUIDs. Are you sure you want to proceed? Cancel Synchronize × DELETE ? You are about to delete, from your personal list of netdata servers, the following server: Are you sure you want to do this? Keep in mind, this server will be added back if and when you visit it again. keep it delete it × SWITCH NETDATA REGISTRY IDENTITY You can copy and paste the following ID to all your browsers (e.g. work and home). All the browsers with the same ID will identify you, so please don't share this with others. Either copy this ID and paste it to another browser, or paste here the ID you have taken from another browser. Keep in mind that: * when you switch ID, your previous ID will be lost forever - this is irreversible. * both IDs (your old and the new) must list this netdata at their personal lists. * both IDs have to be known by the registry: . * to get a new ID, just clear your browser cookies. cancel impersonate × Checking known URLs for this server... Checks may fail if you are viewing an HTTPS page and the server to be checked is HTTP only. Close