![]() * move compression header to compression.h * prototype with zstd compression * updated capabilities * no need for resetting compression * left-over reset function * use ZSTD_compressStream() instead of ZSTD_compressStream2() for backwards compatibility * remove call to LZ4_decoderRingBufferSize() * debug signature failures * fix the buffers of lz4 * fix decoding of zstd * detect compression based on initialization; prefer ZSTD over LZ4 * allow both lz4 and zstd * initialize zstd streams * define missing ZSTD_CLEVEL_DEFAULT * log zero compressed size * debug log * flush compression buffer * add sender compression statistics * removed debugging messages * do not fail if zstd is not available * cleanup and buildinfo * fix max message size, use zstd level 1, add compressio ratio reporting * use compression level 1 * fix ratio title * better compression error logs * for backwards compatibility use buffers of COMPRESSION_MAX_CHUNK * switch to default compression level * additional streaming error conditions detection * do not expose compression stats when compression is not enabled * test for the right lz4 functions * moved lz4 and zstd to their own files * add gzip streaming compression * gzip error handling * added unittest for streaming compression * eliminate a copy of the uncompressed data during zstd compression * eliminate not needed zstd allocations * cleanup * decode gzip with Z_SYNC_FLUSH * set the decoding gzip algorithm * user configuration for compression levels and compression algorithms order * fix exclusion of not preferred compressions * remove now obsolete compression define, since gzip is always available * rename compression algorithms order in stream.conf * move common checks in compression.c * cleanup * backwards compatible error checking |
||
---|---|---|
.. | ||
api | ||
gui | ||
rtc | ||
server | ||
Makefile.am | ||
README.md |
Agent Dashboards
Because Netdata is a health monitoring and performance troubleshooting system, we put a lot of emphasis on real-time, meaningful, and context-aware charts.
We bundle Netdata with a dashboard and hundreds of charts, designed by both our team and the community, but you can also customize them yourself.
There are two primary ways to view Netdata's dashboards on the agent:
-
The local Agent dashboard that comes pre-configured with every Netdata installation. You can see it at
http://NODE:19999
, replacingNODE
withlocalhost
, the hostname of your node, or its IP address. You can customize the contents and colors of the standard dashboard using JavaScript. -
The
dashboard.js
JavaScript library, which helps you customize the standard dashboards using JavaScript, or create entirely new custom dashboards or Atlassian Confluence dashboards.
You can also view all the data Netdata collects through the REST API v1.
dashboard.js
Netdata uses the dashboards.js
file to define, configure, create, and update
all the charts and other visualizations that appear on any Netdata dashboard.
You need to put dashboard.js
on any HTML page that's going to render Netdata
charts.
The custom dashboards documentation contains examples of such custom HTML pages.
Generating dashboard.js
We build the dashboards.js
file by concatenating all the source files located
in the web/gui/src/dashboard.js/
directory. That's done using the provided
build script:
cd web/gui
make
If you make any changes to the src
directory when developing Netdata, you
should regenerate the dashboard.js
file before you commit to the Netdata
repository.