Create a top-level directory to contain source code. (#16896)
* Move ML under src * Move spwan under src * Move cli/ under src/ * move registry/ under src/ * move streaming/ under src/ * Move claim under src. Update docs * Move database/ under src/ * Move libnetdata/ under src/ * Update references to libnetdata * Fix logsmanagement includes * Update generated script path.
This commit is contained in:
vkalintiris
GitHub
parent
2edc0c4890
commit
115d074a6c
|
|
@ -2,7 +2,7 @@
|
|||
path = aclk/aclk-schemas
|
||||
url = https://github.com/netdata/aclk-schemas.git
|
||||
[submodule "ml/kmeans/dlib"]
|
||||
path = ml/dlib
|
||||
path = src/ml/dlib
|
||||
url = https://github.com/davisking/dlib.git
|
||||
shallow = true
|
||||
ignore = dirty
|
||||
|
|
|
|||
529
CMakeLists.txt
529
CMakeLists.txt
|
|
@ -564,146 +564,146 @@ endif()
|
|||
#
|
||||
|
||||
set(LIBJUDY_PREV_FILES
|
||||
libnetdata/libjudy/src/JudyL/JudyLPrev.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLPrevEmpty.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLPrev.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLPrevEmpty.c
|
||||
)
|
||||
|
||||
set(LIBJUDY_NEXT_FILES
|
||||
libnetdata/libjudy/src/JudyL/JudyLNext.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLNextEmpty.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLNext.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLNextEmpty.c
|
||||
)
|
||||
|
||||
set(LIBJUDY_SOURCES
|
||||
libnetdata/libjudy/src/Judy.h
|
||||
libnetdata/libjudy/src/JudyCommon/JudyMalloc.c
|
||||
libnetdata/libjudy/src/JudyCommon/JudyPrivate.h
|
||||
libnetdata/libjudy/src/JudyCommon/JudyPrivate1L.h
|
||||
libnetdata/libjudy/src/JudyCommon/JudyPrivateBranch.h
|
||||
libnetdata/libjudy/src/JudyL/JudyL.h
|
||||
libnetdata/libjudy/src/JudyL/JudyLByCount.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLCascade.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLCount.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLCreateBranch.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLDecascade.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLDel.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLFirst.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLFreeArray.c
|
||||
libnetdata/libjudy/src/JudyL/j__udyLGet.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLGet.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLInsArray.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLIns.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLInsertBranch.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLMallocIF.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLMemActive.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLMemUsed.c
|
||||
libnetdata/libjudy/src/JudyL/JudyLTables.c
|
||||
libnetdata/libjudy/src/JudyHS/JudyHS.c
|
||||
src/libnetdata/libjudy/src/Judy.h
|
||||
src/libnetdata/libjudy/src/JudyCommon/JudyMalloc.c
|
||||
src/libnetdata/libjudy/src/JudyCommon/JudyPrivate.h
|
||||
src/libnetdata/libjudy/src/JudyCommon/JudyPrivate1L.h
|
||||
src/libnetdata/libjudy/src/JudyCommon/JudyPrivateBranch.h
|
||||
src/libnetdata/libjudy/src/JudyL/JudyL.h
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLByCount.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLCascade.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLCount.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLCreateBranch.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLDecascade.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLDel.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLFirst.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLFreeArray.c
|
||||
src/libnetdata/libjudy/src/JudyL/j__udyLGet.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLGet.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLInsArray.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLIns.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLInsertBranch.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLMallocIF.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLMemActive.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLMemUsed.c
|
||||
src/libnetdata/libjudy/src/JudyL/JudyLTables.c
|
||||
src/libnetdata/libjudy/src/JudyHS/JudyHS.c
|
||||
${LIBJUDY_PREV_FILES}
|
||||
${LIBJUDY_NEXT_FILES}
|
||||
)
|
||||
|
||||
set(LIBNETDATA_FILES
|
||||
${CONFIG_H}
|
||||
libnetdata/adaptive_resortable_list/adaptive_resortable_list.c
|
||||
libnetdata/adaptive_resortable_list/adaptive_resortable_list.h
|
||||
libnetdata/config/appconfig.c
|
||||
libnetdata/config/appconfig.h
|
||||
libnetdata/aral/aral.c
|
||||
libnetdata/aral/aral.h
|
||||
libnetdata/avl/avl.c
|
||||
libnetdata/avl/avl.h
|
||||
libnetdata/buffer/buffer.c
|
||||
libnetdata/buffer/buffer.h
|
||||
libnetdata/circular_buffer/circular_buffer.c
|
||||
libnetdata/circular_buffer/circular_buffer.h
|
||||
libnetdata/clocks/clocks.c
|
||||
libnetdata/clocks/clocks.h
|
||||
libnetdata/completion/completion.c
|
||||
libnetdata/completion/completion.h
|
||||
libnetdata/datetime/iso8601.c
|
||||
libnetdata/datetime/iso8601.h
|
||||
libnetdata/datetime/rfc7231.c
|
||||
libnetdata/datetime/rfc7231.h
|
||||
libnetdata/datetime/rfc3339.c
|
||||
libnetdata/datetime/rfc3339.h
|
||||
libnetdata/dictionary/dictionary.c
|
||||
libnetdata/dictionary/dictionary.h
|
||||
libnetdata/eval/eval.c
|
||||
libnetdata/eval/eval.h
|
||||
libnetdata/facets/facets.c
|
||||
libnetdata/facets/facets.h
|
||||
libnetdata/functions_evloop/functions_evloop.c
|
||||
libnetdata/functions_evloop/functions_evloop.h
|
||||
libnetdata/gorilla/gorilla.cc
|
||||
libnetdata/gorilla/gorilla.h
|
||||
libnetdata/july/july.c
|
||||
libnetdata/july/july.h
|
||||
libnetdata/inlined.h
|
||||
libnetdata/json/json.c
|
||||
libnetdata/json/json.h
|
||||
libnetdata/json/jsmn.c
|
||||
libnetdata/json/jsmn.h
|
||||
libnetdata/libnetdata.c
|
||||
libnetdata/libnetdata.h
|
||||
libnetdata/line_splitter/line_splitter.c
|
||||
libnetdata/line_splitter/line_splitter.h
|
||||
libnetdata/libnetdata.h
|
||||
libnetdata/locks/locks.c
|
||||
libnetdata/locks/locks.h
|
||||
libnetdata/log/journal.c
|
||||
libnetdata/log/journal.h
|
||||
libnetdata/log/log.c
|
||||
libnetdata/log/log.h
|
||||
libnetdata/os.c
|
||||
libnetdata/os.h
|
||||
libnetdata/simple_hashtable.h
|
||||
libnetdata/endian.h
|
||||
libnetdata/onewayalloc/onewayalloc.c
|
||||
libnetdata/onewayalloc/onewayalloc.h
|
||||
libnetdata/popen/popen.c
|
||||
libnetdata/popen/popen.h
|
||||
libnetdata/procfile/procfile.c
|
||||
libnetdata/procfile/procfile.h
|
||||
libnetdata/query_progress/progress.c
|
||||
libnetdata/query_progress/progress.h
|
||||
libnetdata/required_dummies.h
|
||||
libnetdata/socket/security.c
|
||||
libnetdata/socket/security.h
|
||||
libnetdata/simple_pattern/simple_pattern.c
|
||||
libnetdata/simple_pattern/simple_pattern.h
|
||||
libnetdata/socket/socket.c
|
||||
libnetdata/socket/socket.h
|
||||
libnetdata/statistical/statistical.c
|
||||
libnetdata/statistical/statistical.h
|
||||
libnetdata/storage_number/storage_number.c
|
||||
libnetdata/storage_number/storage_number.h
|
||||
libnetdata/string/string.c
|
||||
libnetdata/string/string.h
|
||||
libnetdata/threads/threads.c
|
||||
libnetdata/threads/threads.h
|
||||
libnetdata/url/url.c
|
||||
libnetdata/url/url.h
|
||||
libnetdata/uuid/uuid.c
|
||||
libnetdata/uuid/uuid.h
|
||||
libnetdata/string/utf8.h
|
||||
libnetdata/worker_utilization/worker_utilization.c
|
||||
libnetdata/worker_utilization/worker_utilization.h
|
||||
libnetdata/http/http_access.c
|
||||
libnetdata/http/http_access.h
|
||||
libnetdata/http/http_defs.c
|
||||
libnetdata/http/http_defs.h
|
||||
libnetdata/http/content_type.c
|
||||
libnetdata/http/content_type.h
|
||||
libnetdata/config/dyncfg.c
|
||||
libnetdata/config/dyncfg.h
|
||||
libnetdata/json/json-c-parser-inline.h
|
||||
libnetdata/template-enum.h
|
||||
src/libnetdata/adaptive_resortable_list/adaptive_resortable_list.c
|
||||
src/libnetdata/adaptive_resortable_list/adaptive_resortable_list.h
|
||||
src/libnetdata/config/appconfig.c
|
||||
src/libnetdata/config/appconfig.h
|
||||
src/libnetdata/aral/aral.c
|
||||
src/libnetdata/aral/aral.h
|
||||
src/libnetdata/avl/avl.c
|
||||
src/libnetdata/avl/avl.h
|
||||
src/libnetdata/buffer/buffer.c
|
||||
src/libnetdata/buffer/buffer.h
|
||||
src/libnetdata/circular_buffer/circular_buffer.c
|
||||
src/libnetdata/circular_buffer/circular_buffer.h
|
||||
src/libnetdata/clocks/clocks.c
|
||||
src/libnetdata/clocks/clocks.h
|
||||
src/libnetdata/completion/completion.c
|
||||
src/libnetdata/completion/completion.h
|
||||
src/libnetdata/datetime/iso8601.c
|
||||
src/libnetdata/datetime/iso8601.h
|
||||
src/libnetdata/datetime/rfc7231.c
|
||||
src/libnetdata/datetime/rfc7231.h
|
||||
src/libnetdata/datetime/rfc3339.c
|
||||
src/libnetdata/datetime/rfc3339.h
|
||||
src/libnetdata/dictionary/dictionary.c
|
||||
src/libnetdata/dictionary/dictionary.h
|
||||
src/libnetdata/eval/eval.c
|
||||
src/libnetdata/eval/eval.h
|
||||
src/libnetdata/facets/facets.c
|
||||
src/libnetdata/facets/facets.h
|
||||
src/libnetdata/functions_evloop/functions_evloop.c
|
||||
src/libnetdata/functions_evloop/functions_evloop.h
|
||||
src/libnetdata/gorilla/gorilla.cc
|
||||
src/libnetdata/gorilla/gorilla.h
|
||||
src/libnetdata/july/july.c
|
||||
src/libnetdata/july/july.h
|
||||
src/libnetdata/inlined.h
|
||||
src/libnetdata/json/json.c
|
||||
src/libnetdata/json/json.h
|
||||
src/libnetdata/json/jsmn.c
|
||||
src/libnetdata/json/jsmn.h
|
||||
src/libnetdata/libnetdata.c
|
||||
src/libnetdata/libnetdata.h
|
||||
src/libnetdata/line_splitter/line_splitter.c
|
||||
src/libnetdata/line_splitter/line_splitter.h
|
||||
src/libnetdata/libnetdata.h
|
||||
src/libnetdata/locks/locks.c
|
||||
src/libnetdata/locks/locks.h
|
||||
src/libnetdata/log/journal.c
|
||||
src/libnetdata/log/journal.h
|
||||
src/libnetdata/log/log.c
|
||||
src/libnetdata/log/log.h
|
||||
src/libnetdata/os.c
|
||||
src/libnetdata/os.h
|
||||
src/libnetdata/simple_hashtable.h
|
||||
src/libnetdata/endian.h
|
||||
src/libnetdata/onewayalloc/onewayalloc.c
|
||||
src/libnetdata/onewayalloc/onewayalloc.h
|
||||
src/libnetdata/popen/popen.c
|
||||
src/libnetdata/popen/popen.h
|
||||
src/libnetdata/procfile/procfile.c
|
||||
src/libnetdata/procfile/procfile.h
|
||||
src/libnetdata/query_progress/progress.c
|
||||
src/libnetdata/query_progress/progress.h
|
||||
src/libnetdata/required_dummies.h
|
||||
src/libnetdata/socket/security.c
|
||||
src/libnetdata/socket/security.h
|
||||
src/libnetdata/simple_pattern/simple_pattern.c
|
||||
src/libnetdata/simple_pattern/simple_pattern.h
|
||||
src/libnetdata/socket/socket.c
|
||||
src/libnetdata/socket/socket.h
|
||||
src/libnetdata/statistical/statistical.c
|
||||
src/libnetdata/statistical/statistical.h
|
||||
src/libnetdata/storage_number/storage_number.c
|
||||
src/libnetdata/storage_number/storage_number.h
|
||||
src/libnetdata/string/string.c
|
||||
src/libnetdata/string/string.h
|
||||
src/libnetdata/threads/threads.c
|
||||
src/libnetdata/threads/threads.h
|
||||
src/libnetdata/url/url.c
|
||||
src/libnetdata/url/url.h
|
||||
src/libnetdata/uuid/uuid.c
|
||||
src/libnetdata/uuid/uuid.h
|
||||
src/libnetdata/string/utf8.h
|
||||
src/libnetdata/worker_utilization/worker_utilization.c
|
||||
src/libnetdata/worker_utilization/worker_utilization.h
|
||||
src/libnetdata/http/http_access.c
|
||||
src/libnetdata/http/http_access.h
|
||||
src/libnetdata/http/http_defs.c
|
||||
src/libnetdata/http/http_defs.h
|
||||
src/libnetdata/http/content_type.c
|
||||
src/libnetdata/http/content_type.h
|
||||
src/libnetdata/config/dyncfg.c
|
||||
src/libnetdata/config/dyncfg.h
|
||||
src/libnetdata/json/json-c-parser-inline.h
|
||||
src/libnetdata/template-enum.h
|
||||
)
|
||||
|
||||
if(ENABLE_PLUGIN_EBPF)
|
||||
list(APPEND LIBNETDATA_FILES
|
||||
libnetdata/ebpf/ebpf.c
|
||||
libnetdata/ebpf/ebpf.h
|
||||
src/libnetdata/ebpf/ebpf.c
|
||||
src/libnetdata/ebpf/ebpf.h
|
||||
)
|
||||
endif()
|
||||
|
||||
|
|
@ -955,18 +955,18 @@ set(IDLEJITTER_PLUGIN_FILES collectors/idlejitter.plugin/plugin_idlejitter.c)
|
|||
|
||||
if(ENABLE_ML)
|
||||
set(ML_FILES
|
||||
ml/ad_charts.h
|
||||
ml/ad_charts.cc
|
||||
ml/Config.cc
|
||||
ml/dlib/dlib/all/source.cpp
|
||||
ml/ml.h
|
||||
ml/ml.cc
|
||||
ml/ml-private.h
|
||||
src/ml/ad_charts.h
|
||||
src/ml/ad_charts.cc
|
||||
src/ml/Config.cc
|
||||
src/ml/dlib/dlib/all/source.cpp
|
||||
src/ml/ml.h
|
||||
src/ml/ml.cc
|
||||
src/ml/ml-private.h
|
||||
)
|
||||
else()
|
||||
set(ML_FILES
|
||||
ml/ml.h
|
||||
ml/ml-dummy.c
|
||||
src/ml/ml.h
|
||||
src/ml/ml-dummy.c
|
||||
)
|
||||
endif()
|
||||
|
||||
|
|
@ -986,107 +986,107 @@ set(PLUGINSD_PLUGIN_FILES
|
|||
)
|
||||
|
||||
set(RRD_PLUGIN_FILES
|
||||
database/contexts/api_v1.c
|
||||
database/contexts/api_v2.c
|
||||
database/contexts/context.c
|
||||
database/contexts/instance.c
|
||||
database/contexts/internal.h
|
||||
database/contexts/metric.c
|
||||
database/contexts/query_scope.c
|
||||
database/contexts/query_target.c
|
||||
database/contexts/rrdcontext.c
|
||||
database/contexts/rrdcontext.h
|
||||
database/contexts/worker.c
|
||||
database/rrdcollector.c
|
||||
database/rrdcollector.h
|
||||
database/rrddim.c
|
||||
database/rrdfunctions.c
|
||||
database/rrdfunctions.h
|
||||
database/rrdfunctions-inline.c
|
||||
database/rrdfunctions-inline.h
|
||||
database/rrdfunctions-progress.c
|
||||
database/rrdfunctions-progress.h
|
||||
database/rrdfunctions-streaming.c
|
||||
database/rrdfunctions-streaming.h
|
||||
database/rrdhost.c
|
||||
database/rrdlabels.c
|
||||
database/rrd.c
|
||||
database/rrd.h
|
||||
database/rrdset.c
|
||||
database/storage_engine.c
|
||||
database/storage_engine.h
|
||||
database/ram/rrddim_mem.c
|
||||
database/ram/rrddim_mem.h
|
||||
database/sqlite/sqlite_metadata.c
|
||||
database/sqlite/sqlite_metadata.h
|
||||
database/sqlite/sqlite_functions.c
|
||||
database/sqlite/sqlite_functions.h
|
||||
database/sqlite/sqlite_context.c
|
||||
database/sqlite/sqlite_context.h
|
||||
database/sqlite/sqlite_db_migration.c
|
||||
database/sqlite/sqlite_db_migration.h
|
||||
database/sqlite/sqlite_aclk.c
|
||||
database/sqlite/sqlite_aclk.h
|
||||
database/sqlite/sqlite_health.c
|
||||
database/sqlite/sqlite_health.h
|
||||
database/sqlite/sqlite_aclk_node.c
|
||||
database/sqlite/sqlite_aclk_node.h
|
||||
database/sqlite/sqlite_aclk_alert.c
|
||||
database/sqlite/sqlite_aclk_alert.h
|
||||
database/sqlite/sqlite3.c
|
||||
database/sqlite/sqlite3.h
|
||||
database/sqlite/sqlite3recover.c
|
||||
database/sqlite/sqlite3recover.h
|
||||
database/sqlite/dbdata.c
|
||||
database/KolmogorovSmirnovDist.c
|
||||
database/KolmogorovSmirnovDist.h
|
||||
database/rrdfunctions-inflight.c
|
||||
database/rrdfunctions-inflight.h
|
||||
database/rrdfunctions-exporters.c
|
||||
database/rrdfunctions-exporters.h
|
||||
database/rrdfunctions-internals.h
|
||||
database/rrdcollector-internals.h
|
||||
src/database/contexts/api_v1.c
|
||||
src/database/contexts/api_v2.c
|
||||
src/database/contexts/context.c
|
||||
src/database/contexts/instance.c
|
||||
src/database/contexts/internal.h
|
||||
src/database/contexts/metric.c
|
||||
src/database/contexts/query_scope.c
|
||||
src/database/contexts/query_target.c
|
||||
src/database/contexts/rrdcontext.c
|
||||
src/database/contexts/rrdcontext.h
|
||||
src/database/contexts/worker.c
|
||||
src/database/rrdcollector.c
|
||||
src/database/rrdcollector.h
|
||||
src/database/rrddim.c
|
||||
src/database/rrdfunctions.c
|
||||
src/database/rrdfunctions.h
|
||||
src/database/rrdfunctions-inline.c
|
||||
src/database/rrdfunctions-inline.h
|
||||
src/database/rrdfunctions-progress.c
|
||||
src/database/rrdfunctions-progress.h
|
||||
src/database/rrdfunctions-streaming.c
|
||||
src/database/rrdfunctions-streaming.h
|
||||
src/database/rrdhost.c
|
||||
src/database/rrdlabels.c
|
||||
src/database/rrd.c
|
||||
src/database/rrd.h
|
||||
src/database/rrdset.c
|
||||
src/database/storage_engine.c
|
||||
src/database/storage_engine.h
|
||||
src/database/ram/rrddim_mem.c
|
||||
src/database/ram/rrddim_mem.h
|
||||
src/database/sqlite/sqlite_metadata.c
|
||||
src/database/sqlite/sqlite_metadata.h
|
||||
src/database/sqlite/sqlite_functions.c
|
||||
src/database/sqlite/sqlite_functions.h
|
||||
src/database/sqlite/sqlite_context.c
|
||||
src/database/sqlite/sqlite_context.h
|
||||
src/database/sqlite/sqlite_db_migration.c
|
||||
src/database/sqlite/sqlite_db_migration.h
|
||||
src/database/sqlite/sqlite_aclk.c
|
||||
src/database/sqlite/sqlite_aclk.h
|
||||
src/database/sqlite/sqlite_health.c
|
||||
src/database/sqlite/sqlite_health.h
|
||||
src/database/sqlite/sqlite_aclk_node.c
|
||||
src/database/sqlite/sqlite_aclk_node.h
|
||||
src/database/sqlite/sqlite_aclk_alert.c
|
||||
src/database/sqlite/sqlite_aclk_alert.h
|
||||
src/database/sqlite/sqlite3.c
|
||||
src/database/sqlite/sqlite3.h
|
||||
src/database/sqlite/sqlite3recover.c
|
||||
src/database/sqlite/sqlite3recover.h
|
||||
src/database/sqlite/dbdata.c
|
||||
src/database/KolmogorovSmirnovDist.c
|
||||
src/database/KolmogorovSmirnovDist.h
|
||||
src/database/rrdfunctions-inflight.c
|
||||
src/database/rrdfunctions-inflight.h
|
||||
src/database/rrdfunctions-exporters.c
|
||||
src/database/rrdfunctions-exporters.h
|
||||
src/database/rrdfunctions-internals.h
|
||||
src/database/rrdcollector-internals.h
|
||||
)
|
||||
|
||||
if(ENABLE_DBENGINE)
|
||||
list(APPEND RRD_PLUGIN_FILES
|
||||
database/engine/rrdengine.c
|
||||
database/engine/rrdengine.h
|
||||
database/engine/rrddiskprotocol.h
|
||||
database/engine/datafile.c
|
||||
database/engine/datafile.h
|
||||
database/engine/journalfile.c
|
||||
database/engine/journalfile.h
|
||||
database/engine/rrdenginelib.c
|
||||
database/engine/rrdenginelib.h
|
||||
database/engine/rrdengineapi.c
|
||||
database/engine/rrdengineapi.h
|
||||
database/engine/pagecache.c
|
||||
database/engine/pagecache.h
|
||||
database/engine/page_test.cc
|
||||
database/engine/page.c
|
||||
database/engine/page.h
|
||||
database/engine/cache.c
|
||||
database/engine/cache.h
|
||||
database/engine/metric.c
|
||||
database/engine/metric.h
|
||||
database/engine/pdc.c
|
||||
database/engine/pdc.h
|
||||
src/database/engine/rrdengine.c
|
||||
src/database/engine/rrdengine.h
|
||||
src/database/engine/rrddiskprotocol.h
|
||||
src/database/engine/datafile.c
|
||||
src/database/engine/datafile.h
|
||||
src/database/engine/journalfile.c
|
||||
src/database/engine/journalfile.h
|
||||
src/database/engine/rrdenginelib.c
|
||||
src/database/engine/rrdenginelib.h
|
||||
src/database/engine/rrdengineapi.c
|
||||
src/database/engine/rrdengineapi.h
|
||||
src/database/engine/pagecache.c
|
||||
src/database/engine/pagecache.h
|
||||
src/database/engine/page_test.cc
|
||||
src/database/engine/page.c
|
||||
src/database/engine/page.h
|
||||
src/database/engine/cache.c
|
||||
src/database/engine/cache.h
|
||||
src/database/engine/metric.c
|
||||
src/database/engine/metric.h
|
||||
src/database/engine/pdc.c
|
||||
src/database/engine/pdc.h
|
||||
)
|
||||
endif()
|
||||
|
||||
set(REGISTRY_PLUGIN_FILES
|
||||
registry/registry.c
|
||||
registry/registry.h
|
||||
registry/registry_db.c
|
||||
registry/registry_init.c
|
||||
registry/registry_internals.c
|
||||
registry/registry_internals.h
|
||||
registry/registry_log.c
|
||||
registry/registry_machine.c
|
||||
registry/registry_machine.h
|
||||
registry/registry_person.c
|
||||
registry/registry_person.h
|
||||
src/registry/registry.c
|
||||
src/registry/registry.h
|
||||
src/registry/registry_db.c
|
||||
src/registry/registry_init.c
|
||||
src/registry/registry_internals.c
|
||||
src/registry/registry_internals.h
|
||||
src/registry/registry_log.c
|
||||
src/registry/registry_machine.c
|
||||
src/registry/registry_machine.h
|
||||
src/registry/registry_person.c
|
||||
src/registry/registry_person.h
|
||||
)
|
||||
|
||||
set(STATSD_PLUGIN_FILES
|
||||
|
|
@ -1107,23 +1107,23 @@ set(SYSTEMD_JOURNAL_PLUGIN_FILES
|
|||
)
|
||||
|
||||
set(STREAMING_PLUGIN_FILES
|
||||
streaming/rrdpush.c
|
||||
streaming/rrdpush.h
|
||||
streaming/compression.c
|
||||
streaming/compression.h
|
||||
streaming/compression_brotli.c
|
||||
streaming/compression_brotli.h
|
||||
streaming/compression_gzip.c
|
||||
streaming/compression_gzip.h
|
||||
streaming/compression_lz4.c
|
||||
streaming/compression_lz4.h
|
||||
streaming/compression_zstd.c
|
||||
streaming/compression_zstd.h
|
||||
streaming/receiver.c
|
||||
streaming/sender.c
|
||||
streaming/replication.c
|
||||
streaming/replication.h
|
||||
streaming/common.h
|
||||
src/streaming/rrdpush.c
|
||||
src/streaming/rrdpush.h
|
||||
src/streaming/compression.c
|
||||
src/streaming/compression.h
|
||||
src/streaming/compression_brotli.c
|
||||
src/streaming/compression_brotli.h
|
||||
src/streaming/compression_gzip.c
|
||||
src/streaming/compression_gzip.h
|
||||
src/streaming/compression_lz4.c
|
||||
src/streaming/compression_lz4.h
|
||||
src/streaming/compression_zstd.c
|
||||
src/streaming/compression_zstd.h
|
||||
src/streaming/receiver.c
|
||||
src/streaming/sender.c
|
||||
src/streaming/replication.c
|
||||
src/streaming/replication.h
|
||||
src/streaming/common.h
|
||||
)
|
||||
|
||||
set(WEB_PLUGIN_FILES
|
||||
|
|
@ -1138,15 +1138,15 @@ set(WEB_PLUGIN_FILES
|
|||
)
|
||||
|
||||
set(CLAIM_PLUGIN_FILES
|
||||
claim/claim.c
|
||||
claim/claim.h
|
||||
src/claim/claim.c
|
||||
src/claim/claim.h
|
||||
)
|
||||
|
||||
set(SPAWN_PLUGIN_FILES
|
||||
spawn/spawn.c
|
||||
spawn/spawn_server.c
|
||||
spawn/spawn_client.c
|
||||
spawn/spawn.h
|
||||
src/spawn/spawn.c
|
||||
src/spawn/spawn_server.c
|
||||
src/spawn/spawn_client.c
|
||||
src/spawn/spawn.h
|
||||
)
|
||||
|
||||
set(ACLK_ALWAYS_BUILD
|
||||
|
|
@ -1291,8 +1291,8 @@ set(LOGS_MANAGEMENT_PLUGIN_FILES
|
|||
logsmanagement/rrd_api/rrd_api_web_log.c
|
||||
logsmanagement/rrd_api/rrd_api_web_log.h
|
||||
logsmanagement/rrd_api/rrd_api.h
|
||||
database/sqlite/sqlite3.c
|
||||
database/sqlite/sqlite3.h
|
||||
src/database/sqlite/sqlite3.c
|
||||
src/database/sqlite/sqlite3.h
|
||||
)
|
||||
|
||||
set(NETDATA_FILES
|
||||
|
|
@ -1489,15 +1489,15 @@ target_compile_definitions(judy PRIVATE
|
|||
)
|
||||
|
||||
target_include_directories(judy PUBLIC
|
||||
libnetdata/libjudy/src
|
||||
libnetdata/libjudy/src/JudyCommon
|
||||
src/libnetdata/libjudy/src
|
||||
src/libnetdata/libjudy/src/JudyCommon
|
||||
)
|
||||
|
||||
set_source_files_properties(${LIBJUDY_PREV_FILES} PROPERTIES COMPILE_OPTIONS "-DJUDYPREV")
|
||||
set_source_files_properties(${LIBJUDY_NEXT_FILES} PROPERTIES COMPILE_OPTIONS "-DJUDYNEXT")
|
||||
set_source_files_properties(libnetdata/libjudy/src/JudyL/j__udyLGet.c PROPERTIES COMPILE_OPTIONS "-DJUDYGETINLINE")
|
||||
set_source_files_properties(libnetdata/libjudy/src/JudyL/JudyLByCount.c PROPERTIES COMPILE_OPTIONS "-DNOSMARTJBB -DNOSMARTJBU -DNOSMARTJLB")
|
||||
set_source_files_properties(JudyLTables.c PROPERTIES COMPILE_OPTIONS "-I${CMAKE_SOURCE_DIR}/libnetdata/libjudy/src/JudyL")
|
||||
set_source_files_properties(src/libnetdata/libjudy/src/JudyL/j__udyLGet.c PROPERTIES COMPILE_OPTIONS "-DJUDYGETINLINE")
|
||||
set_source_files_properties(src/libnetdata/libjudy/src/JudyL/JudyLByCount.c PROPERTIES COMPILE_OPTIONS "-DNOSMARTJBB -DNOSMARTJBU -DNOSMARTJLB")
|
||||
set_source_files_properties(JudyLTables.c PROPERTIES COMPILE_OPTIONS "-I${CMAKE_SOURCE_DIR}/src/libnetdata/libjudy/src/JudyL")
|
||||
|
||||
#
|
||||
# build libnetdata
|
||||
|
|
@ -1507,7 +1507,7 @@ include(systemd.cmake)
|
|||
|
||||
add_library(libnetdata STATIC ${LIBNETDATA_FILES})
|
||||
|
||||
target_include_directories(libnetdata BEFORE PUBLIC ${CONFIG_H_DIR} ${CMAKE_SOURCE_DIR})
|
||||
target_include_directories(libnetdata BEFORE PUBLIC ${CONFIG_H_DIR} ${CMAKE_SOURCE_DIR} ${CMAKE_SOURCE_DIR}/src)
|
||||
|
||||
# pthread (FIXME: use find_package for this)
|
||||
|
||||
|
|
@ -2083,7 +2083,6 @@ target_compile_definitions(netdata PRIVATE
|
|||
target_include_directories(netdata PRIVATE
|
||||
"$<$<BOOL:${ENABLE_PROTOBUF}>:${PROTOBUF_INCLUDE_DIRS}>"
|
||||
"$<$<BOOL:${ENABLE_ACLK}>:${CMAKE_SOURCE_DIR}/aclk/aclk-schemas>"
|
||||
"$<$<BOOL:${ENABLE_ML}>:${CMAKE_SOURCE_DIR}/ml/dlib>"
|
||||
"$<$<BOOL:${ENABLE_EXPORTER_MONGODB}>:${MONGOC_INCLUDE_DIRS}>"
|
||||
"$<$<BOOL:${ENABLE_EXPORTER_PROMETHEUS_REMOTE_WRITE}>:${SNAPPY_INCLUDE_DIRS}>"
|
||||
)
|
||||
|
|
@ -2104,8 +2103,8 @@ target_link_libraries(netdata PRIVATE
|
|||
#
|
||||
# build systemd-cat-native
|
||||
#
|
||||
set(SYSTEMD_CAT_NATIVE_FILES libnetdata/log/systemd-cat-native.c
|
||||
libnetdata/log/systemd-cat-native.h)
|
||||
set(SYSTEMD_CAT_NATIVE_FILES src/libnetdata/log/systemd-cat-native.c
|
||||
src/libnetdata/log/systemd-cat-native.h)
|
||||
|
||||
add_executable(systemd-cat-native ${SYSTEMD_CAT_NATIVE_FILES})
|
||||
target_link_libraries(systemd-cat-native libnetdata)
|
||||
|
|
@ -2139,7 +2138,7 @@ if(PCRE2_FOUND)
|
|||
)
|
||||
|
||||
add_executable(log2journal ${LOG2JOURNAL_FILES})
|
||||
target_include_directories(log2journal BEFORE PUBLIC ${CONFIG_H_DIR} ${PCRE2_INCLUDE_DIRS})
|
||||
target_include_directories(log2journal BEFORE PUBLIC ${CONFIG_H_DIR} ${CMAKE_SOURCE_DIR}/src ${PCRE2_INCLUDE_DIRS})
|
||||
target_compile_definitions(log2journal PUBLIC ${PCRE2_CFLAGS_OTHER})
|
||||
target_link_libraries(log2journal PUBLIC "${PCRE2_LDFLAGS}")
|
||||
|
||||
|
|
@ -2169,7 +2168,7 @@ set(NETDATACLI_FILES
|
|||
daemon/commands.h
|
||||
daemon/pipename.c
|
||||
daemon/pipename.h
|
||||
cli/cli.c
|
||||
src/cli/cli.c
|
||||
)
|
||||
|
||||
add_executable(netdatacli ${NETDATACLI_FILES})
|
||||
|
|
@ -2265,9 +2264,9 @@ else()
|
|||
set(enable_aclk_POST "no")
|
||||
endif()
|
||||
|
||||
configure_file(claim/netdata-claim.sh.in claim/netdata-claim.sh @ONLY)
|
||||
configure_file(src/claim/netdata-claim.sh.in src/claim/netdata-claim.sh @ONLY)
|
||||
install(PROGRAMS
|
||||
${CMAKE_BINARY_DIR}/claim/netdata-claim.sh
|
||||
${CMAKE_BINARY_DIR}/src/claim/netdata-claim.sh
|
||||
DESTINATION usr/sbin)
|
||||
|
||||
#
|
||||
|
|
@ -2314,7 +2313,7 @@ install(FILES
|
|||
# streaming
|
||||
#
|
||||
install(FILES
|
||||
streaming/stream.conf
|
||||
src/streaming/stream.conf
|
||||
DESTINATION usr/lib/netdata/conf.d)
|
||||
|
||||
#
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ netdata (1.6.0) - 2017-03-20
|
|||
menu on the dashboard.
|
||||
|
||||
For more information check:
|
||||
<https://github.com/netdata/netdata/tree/master/streaming#monitoring-ephemeral-nodes>
|
||||
<https://github.com/netdata/netdata/tree/master/src/streaming#monitoring-ephemeral-nodes>
|
||||
|
||||
- monitoring ephemeral containers and VM guests
|
||||
|
||||
|
|
|
|||
16
README.md
16
README.md
|
|
@ -322,7 +322,7 @@ Each Netdata Agent can perform the following functions:
|
|||
And it also supports synthetic tests / white box tests, so you can ping servers, check API responses, or even check filesystem files and directories to generate metrics, train ML and run alerts and notifications on their status.
|
||||
|
||||
2. **`STORE` metrics to a database**<br/>
|
||||
Uses database engine plugins to store the collected data, either in memory and/or on disk. We have developed our own [`dbengine`](https://github.com/netdata/netdata/tree/master/database/engine#readme) for storing the data in a very efficient manner, allowing Netdata to have less than 1 byte per sample on disk and amazingly fast queries.
|
||||
Uses database engine plugins to store the collected data, either in memory and/or on disk. We have developed our own [`dbengine`](https://github.com/netdata/netdata/tree/master/src/database/engine#readme) for storing the data in a very efficient manner, allowing Netdata to have less than 1 byte per sample on disk and amazingly fast queries.
|
||||
|
||||
3. **`LEARN` the behavior of metrics** (ML)<br/>
|
||||
Trains multiple Machine-Learning (ML) models per metric to learn the behavior of each metric individually. Netdata uses the `kmeans` algorithm and creates by default a model per metric per hour, based on the values collected for that metric over the last 6 hours. The trained models are persisted to disk.
|
||||
|
|
@ -350,28 +350,28 @@ When using Netdata Parents, all the functions of a Netdata Agent (except data co
|
|||
The core of Netdata is developed in C. We have our own `libnetdata`, that provides:
|
||||
|
||||
- **`DICTIONARY`**<br/>
|
||||
A high-performance algorithm to maintain both indexed and ordered pools of structures Netdata needs. It uses JudyHS arrays for indexing, although it is modular: any hashtable or tree can be integrated into it. Despite being in C, dictionaries follow object-oriented programming principles, so there are constructors, destructors, automatic memory management, garbage collection, and more. For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/dictionary).
|
||||
A high-performance algorithm to maintain both indexed and ordered pools of structures Netdata needs. It uses JudyHS arrays for indexing, although it is modular: any hashtable or tree can be integrated into it. Despite being in C, dictionaries follow object-oriented programming principles, so there are constructors, destructors, automatic memory management, garbage collection, and more. For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/dictionary).
|
||||
|
||||
- **`ARAL`**<br/>
|
||||
ARray ALlocator (ARAL) is used to minimize the system allocations made by Netdata. ARAL is optimized for peak performance when multi-threaded. It also allows all structures that use it to be allocated in memory-mapped files (shared memory) instead of RAM. For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/aral).
|
||||
ARray ALlocator (ARAL) is used to minimize the system allocations made by Netdata. ARAL is optimized for peak performance when multi-threaded. It also allows all structures that use it to be allocated in memory-mapped files (shared memory) instead of RAM. For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/aral).
|
||||
|
||||
- **`PROCFILE`**<br/>
|
||||
A high-performance `/proc` (but also any) file parser and text tokenizer. It achieves its performance by keeping files open and adjustings its buffers to read the entire file in one call (which is also required by the Linux kernel). For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/procfile).
|
||||
A high-performance `/proc` (but also any) file parser and text tokenizer. It achieves its performance by keeping files open and adjustings its buffers to read the entire file in one call (which is also required by the Linux kernel). For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/procfile).
|
||||
|
||||
- **`STRING`**<br/>
|
||||
A string internet mechanism, for string deduplication and indexing (using JudyHS arrays), optimized for multi-threaded usage. For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/string).
|
||||
A string internet mechanism, for string deduplication and indexing (using JudyHS arrays), optimized for multi-threaded usage. For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/string).
|
||||
|
||||
- **`ARL`**<br/>
|
||||
Adaptive Resortable List (ARL), is a very fast list iterator, that keeps the expected items on the list in the same order they are found in input list. So, the first iteration is somewhat slower, but all the following iterations are perfectly aligned for best performance. For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/adaptive_resortable_list).
|
||||
Adaptive Resortable List (ARL), is a very fast list iterator, that keeps the expected items on the list in the same order they are found in input list. So, the first iteration is somewhat slower, but all the following iterations are perfectly aligned for best performance. For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/adaptive_resortable_list).
|
||||
|
||||
- **`BUFFER`**<br/>
|
||||
A flexible text buffer management system that allows Netdata to automatically handle dynamically sized text buffer allocations. The same mechanism is used for generating consistent JSON output by the Netdata APIs. For more see [here](https://github.com/netdata/netdata/tree/master/libnetdata/buffer).
|
||||
A flexible text buffer management system that allows Netdata to automatically handle dynamically sized text buffer allocations. The same mechanism is used for generating consistent JSON output by the Netdata APIs. For more see [here](https://github.com/netdata/netdata/tree/master/src/libnetdata/buffer).
|
||||
|
||||
- **`SPINLOCK`**<br/>
|
||||
Like POSIX `MUTEX` and `RWLOCK` but a lot faster, based on atomic operations, with significantly smaller memory impact, while being portable.
|
||||
|
||||
- **`PGC`**<br/>
|
||||
A caching layer that can be used to cache any kind of time-related data, with automatic indexing (based on a tree of JudyL arrays), memory management, evictions, flushing, pressure management. This is extensively used in `dbengine`. For more see [here](https://github.com/netdata/netdata/blob/master/database/engine/README.md).
|
||||
A caching layer that can be used to cache any kind of time-related data, with automatic indexing (based on a tree of JudyL arrays), memory management, evictions, flushing, pressure management. This is extensively used in `dbengine`. For more see [here](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md).
|
||||
|
||||
The above, and many more, allow Netdata developers to work on the application fast and with confidence. Most of the business logic in Netdata is a work of mixing the above.
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ The Cloud App lives at app.netdata.cloud which currently resolves to the followi
|
|||
>This list of IPs can change without notice, we strongly advise you to whitelist following domains `app.netdata.cloud`, `mqtt.netdata.cloud`, if this is not an option in your case always verify the current domain resolution (e.g via the `host` command).
|
||||
|
||||
For a guide to connecting a node using the ACLK, plus additional troubleshooting and reference information, read our [connect to Cloud
|
||||
documentation](https://github.com/netdata/netdata/blob/master/claim/README.md).
|
||||
documentation](https://github.com/netdata/netdata/blob/master/src/claim/README.md).
|
||||
|
||||
## Data privacy
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ configuration uses two settings:
|
|||
```
|
||||
|
||||
If your Agent needs to use a proxy to access the internet, you must [set up a proxy for
|
||||
connecting to cloud](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy).
|
||||
connecting to cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy).
|
||||
|
||||
You can configure following keys in the `netdata.conf` section `[cloud]`:
|
||||
```
|
||||
|
|
@ -118,7 +118,7 @@ If you first disable the ACLK and any Cloud functionality and then decide you wo
|
|||
|
||||
If you passed `--disable-cloud` to `netdata-installer.sh` during installation, you must
|
||||
[reinstall](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) your Agent. Use the same method as before, but pass `--require-cloud` to
|
||||
the installer. When installation finishes you can [connect your node](https://github.com/netdata/netdata/blob/master/claim/README.md#how-to-connect-a-node).
|
||||
the installer. When installation finishes you can [connect your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md#how-to-connect-a-node).
|
||||
|
||||
If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf` file, edit the file again and change
|
||||
`enabled` to `yes`:
|
||||
|
|
@ -128,6 +128,6 @@ If you changed the runtime setting in your `var/lib/netdata/cloud.d/cloud.conf`
|
|||
enabled = yes
|
||||
```
|
||||
|
||||
Restart your Agent and [connect your node](https://github.com/netdata/netdata/blob/master/claim/README.md#how-to-connect-a-node).
|
||||
Restart your Agent and [connect your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md#how-to-connect-a-node).
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -78,7 +78,7 @@ currently unsupported when using unified cgroups.
|
|||
### Enabled cgroups
|
||||
|
||||
To provide a sane default, Netdata uses the
|
||||
following [pattern list](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md):
|
||||
following [pattern list](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md):
|
||||
|
||||
- Checks the pattern against the path of the cgroup
|
||||
|
||||
|
|
|
|||
|
|
@ -316,7 +316,7 @@ You can configure the information shown with function `ebpf_socket` using the se
|
|||
|
||||
When you define a `ports` setting, Netdata will collect network metrics for that specific port. For example, if you
|
||||
write `ports = 19999`, Netdata will collect only connections for itself. The `hostnames` setting accepts
|
||||
[simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). The `ports`, and `ips` settings accept negation (`!`) to deny
|
||||
[simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). The `ports`, and `ips` settings accept negation (`!`) to deny
|
||||
specific values or asterisk alone to define all values.
|
||||
|
||||
In the above example, Netdata will collect metrics for all ports between `1` and `1024`, with the exception of `53` (domain)
|
||||
|
|
|
|||
|
|
@ -215,7 +215,7 @@ extern netdata_fd_stat_t **fd_pid;
|
|||
extern netdata_publish_shm_t **shm_pid;
|
||||
|
||||
// The default value is at least 32 times smaller than maximum number of PIDs allowed on system,
|
||||
// this is only possible because we are using ARAL (https://github.com/netdata/netdata/tree/master/libnetdata/aral).
|
||||
// this is only possible because we are using ARAL (https://github.com/netdata/netdata/tree/master/src/libnetdata/aral).
|
||||
#ifndef NETDATA_EBPF_ALLOC_MAX_PID
|
||||
# define NETDATA_EBPF_ALLOC_MAX_PID 1024
|
||||
#endif
|
||||
|
|
|
|||
|
|
@ -522,7 +522,7 @@ journalctl -f --namespace=nginx-logs
|
|||
|
||||
Netdata will automatically pick the new namespace and present it at the list of sources of the dashboard.
|
||||
|
||||
You can also instruct `systemd-cat-native` to log to a remote system, sending the logs to a `systemd-journal-remote` instance running on another server. Check [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/libnetdata/log/systemd-cat-native.md).
|
||||
You can also instruct `systemd-cat-native` to log to a remote system, sending the logs to a `systemd-journal-remote` instance running on another server. Check [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/src/libnetdata/log/systemd-cat-native.md).
|
||||
|
||||
|
||||
## Performance
|
||||
|
|
@ -909,4 +909,4 @@ You can find the most common fields at 'man systemd.journal-fields'.
|
|||
|
||||
## `systemd-cat-native` options
|
||||
|
||||
Read [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/libnetdata/log/systemd-cat-native.md).
|
||||
Read [the manual of systemd-cat-native](https://github.com/netdata/netdata/blob/master/src/libnetdata/log/systemd-cat-native.md).
|
||||
|
|
|
|||
|
|
@ -86,7 +86,7 @@ static inline void freez(void *ptr) {
|
|||
// ----------------------------------------------------------------------------
|
||||
|
||||
#define XXH_INLINE_ALL
|
||||
#include "../../libnetdata/xxhash.h"
|
||||
#include "libnetdata/xxhash.h"
|
||||
|
||||
#define PCRE2_CODE_UNIT_WIDTH 8
|
||||
#include <pcre2.h>
|
||||
|
|
@ -99,14 +99,14 @@ static inline void freez(void *ptr) {
|
|||
// hashtable for HASHED_KEY
|
||||
|
||||
// cleanup hashtable defines
|
||||
#include "../../libnetdata/simple_hashtable_undef.h"
|
||||
#include "libnetdata/simple_hashtable_undef.h"
|
||||
|
||||
struct hashed_key;
|
||||
static inline int compare_keys(struct hashed_key *k1, struct hashed_key *k2);
|
||||
#define SIMPLE_HASHTABLE_SORT_FUNCTION compare_keys
|
||||
#define SIMPLE_HASHTABLE_VALUE_TYPE struct hashed_key
|
||||
#define SIMPLE_HASHTABLE_NAME _KEY
|
||||
#include "../../libnetdata/simple_hashtable.h"
|
||||
#include "libnetdata/simple_hashtable.h"
|
||||
|
||||
// ----------------------------------------------------------------------------
|
||||
|
||||
|
|
|
|||
|
|
@ -220,7 +220,7 @@ Netdata can visualize StatsD collected metrics in 2 ways:
|
|||
|
||||
### Private metric charts
|
||||
|
||||
Private charts are controlled with `create private charts for metrics matching = *`. This setting accepts a space-separated list of [simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). Netdata will create private charts for all metrics **by default**.
|
||||
Private charts are controlled with `create private charts for metrics matching = *`. This setting accepts a space-separated list of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). Netdata will create private charts for all metrics **by default**.
|
||||
|
||||
For example, to render charts for all `myapp.*` metrics, except `myapp.*.badmetric`, use:
|
||||
|
||||
|
|
@ -228,7 +228,7 @@ For example, to render charts for all `myapp.*` metrics, except `myapp.*.badmetr
|
|||
create private charts for metrics matching = !myapp.*.badmetric myapp.*
|
||||
```
|
||||
|
||||
You can specify Netdata StatsD to have a different `memory mode` than the rest of the Netdata Agent. You can read more about `memory mode` in the [documentation](https://github.com/netdata/netdata/blob/master/database/README.md).
|
||||
You can specify Netdata StatsD to have a different `memory mode` than the rest of the Netdata Agent. You can read more about `memory mode` in the [documentation](https://github.com/netdata/netdata/blob/master/src/database/README.md).
|
||||
|
||||
The default behavior is to use the same settings as the rest of the Netdata Agent. If you wish to change them, edit the following settings:
|
||||
- `private charts memory mode`
|
||||
|
|
@ -341,7 +341,7 @@ Using the above configuration `myapp` should get its own section on the dashboar
|
|||
`[app]` starts a new application definition. The supported settings in this section are:
|
||||
|
||||
- `name` defines the name of the app.
|
||||
- `metrics` is a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). This pattern should match all the possible StatsD metrics that will be participating in the application `myapp`.
|
||||
- `metrics` is a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). This pattern should match all the possible StatsD metrics that will be participating in the application `myapp`.
|
||||
- `private charts = yes|no`, enables or disables private charts for the metrics matched.
|
||||
- `gaps when not collected = yes|no`, enables or disables gaps on the charts of the application in case that no metrics are collected.
|
||||
- `memory mode` sets the memory mode for all charts of the application. The default is the global default for Netdata (not the global default for StatsD private charts). We suggest not to use this (we have commented it out in the example) and let your app use the global default for Netdata, which is our dbengine.
|
||||
|
|
@ -367,7 +367,7 @@ So, the format is this:
|
|||
dimension = [pattern] METRIC NAME TYPE MULTIPLIER DIVIDER OPTIONS
|
||||
```
|
||||
|
||||
`pattern` is a keyword. When set, `METRIC` is expected to be a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) that will be used to match all the StatsD metrics to be added to the chart. So, `pattern` automatically matches any number of StatsD metrics, all of which will be added as separate chart dimensions.
|
||||
`pattern` is a keyword. When set, `METRIC` is expected to be a Netdata [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) that will be used to match all the StatsD metrics to be added to the chart. So, `pattern` automatically matches any number of StatsD metrics, all of which will be added as separate chart dimensions.
|
||||
|
||||
`TYPE`, `MULTIPLIER`, `DIVIDER` and `OPTIONS` are optional.
|
||||
|
||||
|
|
@ -845,7 +845,7 @@ metrics into different charts. This is particularly important, since we decide:
|
|||
The dimension option has this syntax: `dimension = [pattern] METRIC NAME TYPE MULTIPLIER DIVIDER OPTIONS`
|
||||
|
||||
- **pattern**: A keyword that tells the StatsD server the `METRIC` string is actually a
|
||||
[simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md).
|
||||
[simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
|
||||
We don't use simple patterns in the example, but if we wanted to visualize all the `http_req` metrics, we
|
||||
could have a single dimension: `dimension = pattern 'k6.http_req*' last 1 1`. Find detailed examples with
|
||||
patterns in [dimension patterns](https://github.com/netdata/netdata/blob/master/collectors/statsd.plugin/README.md#dimension-patterns).
|
||||
|
|
|
|||
|
|
@ -114,7 +114,7 @@ The command line options of the Netdata 1.10.0 version are the following:
|
|||
- USR2 Reload health configuration.
|
||||
```
|
||||
|
||||
You can send commands during runtime via [netdatacli](https://github.com/netdata/netdata/blob/master/cli/README.md).
|
||||
You can send commands during runtime via [netdatacli](https://github.com/netdata/netdata/blob/master/src/cli/README.md).
|
||||
|
||||
## Log files
|
||||
|
||||
|
|
@ -373,7 +373,7 @@ When you compile Netdata with debugging:
|
|||
2. a lot of code is added all over netdata, to log debug messages to `/var/log/netdata/debug.log`. However, nothing is
|
||||
printed by default. Netdata allows you to select which sections of Netdata you want to trace. Tracing is activated
|
||||
via the config option `debug flags`. It accepts a hex number, to enable or disable specific sections. You can find
|
||||
the options supported at [log.h](https://raw.githubusercontent.com/netdata/netdata/master/libnetdata/log/log.h).
|
||||
the options supported at [log.h](https://raw.githubusercontent.com/netdata/netdata/master/src/libnetdata/log/log.h).
|
||||
They are the `D_*` defines. The value `0xffffffffffffffff` will enable all possible debug flags.
|
||||
|
||||
Once Netdata is compiled with debugging and tracing is enabled for a few sections, the file `/var/log/netdata/debug.log`
|
||||
|
|
|
|||
|
|
@ -36,11 +36,11 @@ the [web server access lists](https://github.com/netdata/netdata/blob/master/web
|
|||
5. `[environment variables]` to [configure](#environment-variables-section-options) the environment variables used
|
||||
Netdata.
|
||||
6. `[sqlite]` to [configure](#sqlite-section-options) the [Netdata daemon](https://github.com/netdata/netdata/blob/master/daemon/README.md) SQLite settings.
|
||||
7. `[ml]` to configure settings for [machine learning](https://github.com/netdata/netdata/blob/master/ml/README.md).
|
||||
7. `[ml]` to configure settings for [machine learning](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
|
||||
8. `[health]` to [configure](#health-section-options) general settings for [health monitoring](https://github.com/netdata/netdata/blob/master/health/README.md).
|
||||
9. `[web]` to [configure the web server](https://github.com/netdata/netdata/blob/master/web/server/README.md).
|
||||
10. `[registry]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/registry/README.md).
|
||||
11. `[global statistics]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/registry/README.md).
|
||||
10. `[registry]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
|
||||
11. `[global statistics]` for the [Netdata registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
|
||||
12. `[statsd]` for the general settings of the [stats.d.plugin](https://github.com/netdata/netdata/blob/master/collectors/statsd.plugin/README.md).
|
||||
13. `[plugins]` to [configure](#plugins-section-options) which [collectors](https://github.com/netdata/netdata/blob/master/collectors/README.md) to use and PATH
|
||||
settings.
|
||||
|
|
@ -89,17 +89,17 @@ Please note that your data history will be lost if you have modified `history` p
|
|||
| setting | default | info |
|
||||
|:---------------------------------------------:|:----------:|:---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| mode | `dbengine` | `dbengine`: The default for long-term metrics storage with efficient RAM and disk usage. Can be extended with `dbengine page cache size MB` and `dbengine disk space MB`. <br />`ram`: The round-robin database will be temporary and it will be lost when Netdata exits. <br />`alloc`: Similar to `ram`, but can significantly reduce memory usage, when combined with a low retention and does not support KSM. <br />`none`: Disables the database at this host, and disables health monitoring entirely, as that requires a database of metrics. Not to be used together with streaming. |
|
||||
| retention | `3600` | Used with `mode = ram/alloc`, not the default `mode = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](https://github.com/netdata/netdata/blob/master/database/README.md) for more information. |
|
||||
| storage tiers | `1` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/database/engine/README.md#tiering). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. |
|
||||
| retention | `3600` | Used with `mode = ram/alloc`, not the default `mode = dbengine`. This number reflects the number of entries the `netdata` daemon will by default keep in memory for each chart dimension. Check [Memory Requirements](https://github.com/netdata/netdata/blob/master/src/database/README.md) for more information. |
|
||||
| storage tiers | `1` | The number of storage tiers you want to have in your dbengine. Check the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering). You can have up to 5 tiers of data (including the _Tier 0_). This number ranges between 1 and 5. |
|
||||
| dbengine page cache size MB | `32` | Determines the amount of RAM in MiB that is dedicated to caching for _Tier 0_ Netdata metric values. |
|
||||
| dbengine tier **`N`** page cache size MB | `32` | Determines the amount of RAM in MiB that is dedicated for caching Netdata metric values of the **`N`** tier. <br /> `N belongs to [1..4]` |
|
||||
| dbengine disk space MB | `256` | Determines the amount of disk space in MiB that is dedicated to storing _Tier 0_ Netdata metric values and all related metadata describing them. This option is available **only for legacy configuration** (`Agent v1.23.2 and prior`). |
|
||||
| dbengine multihost disk space MB | `256` | Same functionality as `dbengine disk space MB`, but includes support for storing metrics streamed to a parent node by its children. Can be used in single-node environments as well. This setting is only for _Tier 0_ metrics. |
|
||||
| dbengine tier **`N`** multihost disk space MB | `256` | Same functionality as `dbengine multihost disk space MB`, but stores metrics of the **`N`** tier (both parent node and its children). Can be used in single-node environments as well. <br /> `N belongs to [1..4]` |
|
||||
| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](https://github.com/netdata/netdata/blob/master/docs/guides/configure/performance.md). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/database/engine/README.md#tiering). |
|
||||
| update every | `1` | The frequency in seconds, for data collection. For more information see the [performance guide](https://github.com/netdata/netdata/blob/master/docs/guides/configure/performance.md). These metrics stored as _Tier 0_ data. Explore the tiering mechanism in the [dbengine's reference](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering). |
|
||||
| dbengine tier **`N`** update every iterations | `60` | The down sampling value of each tier from the previous one. For each Tier, the greater by one Tier has N (equal to 60 by default) less data points of any metric it collects. This setting can take values from `2` up to `255`. <br /> `N belongs to [1..4]` |
|
||||
| dbengine tier **`N`** back fill | `New` | Specifies the strategy of recreating missing data on each Tier from the exact lower Tier. <br /> `New`: Sees the latest point on each Tier and save new points to it only if the exact lower Tier has available points for it's observation window (`dbengine tier N update every iterations` window). <br /> `none`: No back filling is applied. <br /> `N belongs to [1..4]` |
|
||||
| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. For more information check [Memory Deduplication - Kernel Same Page Merging - KSM](https://github.com/netdata/netdata/blob/master/database/README.md#ksm) |
|
||||
| memory deduplication (ksm) | `yes` | When set to `yes`, Netdata will offer its in-memory round robin database and the dbengine page cache to kernel same page merging (KSM) for deduplication. For more information check [Memory Deduplication - Kernel Same Page Merging - KSM](https://github.com/netdata/netdata/blob/master/src/database/README.md#ksm) |
|
||||
| cleanup obsolete charts after secs | `3600` | See [monitoring ephemeral containers](https://github.com/netdata/netdata/blob/master/collectors/cgroups.plugin/README.md#monitoring-ephemeral-containers), also sets the timeout for cleaning up obsolete dimensions |
|
||||
| gap when lost iterations above | `1` | |
|
||||
| cleanup orphan hosts after secs | `3600` | How long to wait until automatically removing from the DB a remote Netdata host (child) that is no longer sending data. |
|
||||
|
|
@ -126,7 +126,7 @@ Please note that your data history will be lost if you have modified `history` p
|
|||
| plugins | `"/usr/libexec/netdata/plugins.d" "/etc/netdata/custom-plugins.d"` | The directory plugin programs are kept. This setting supports multiple directories, space separated. If any directory path contains spaces, enclose it in single or double quotes. |
|
||||
| health config | `/etc/netdata/health.d` | The directory containing the user alert configuration files, to override the stock configurations |
|
||||
| stock health config | `/usr/lib/netdata/conf.d/health.d` | Contains the stock alert configuration files for each collector |
|
||||
| registry | `/opt/netdata/var/lib/netdata/registry` | Contains the [registry](https://github.com/netdata/netdata/blob/master/registry/README.md) database and GUID that uniquely identifies each Netdata Agent |
|
||||
| registry | `/opt/netdata/var/lib/netdata/registry` | Contains the [registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md) database and GUID that uniquely identifies each Netdata Agent |
|
||||
|
||||
### [logs] section options
|
||||
|
||||
|
|
@ -177,7 +177,7 @@ monitoring](https://github.com/netdata/netdata/blob/master/health/README.md).
|
|||
| run at least every seconds | `10` | Controls how often all alert conditions should be evaluated. |
|
||||
| postpone alarms during hibernation for seconds | `60` | Prevents false alerts. May need to be increased if you get alerts during hibernation. |
|
||||
| health log history | `432000` | Specifies the history of alert events (in seconds) kept in the agent's sqlite database. |
|
||||
| enabled alarms | * | Defines which alerts to load from both user and stock directories. This is a [simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) list of alert or template names. Can be used to disable specific alerts. For example, `enabled alarms = !oom_kill *` will load all alerts except `oom_kill`. |
|
||||
| enabled alarms | * | Defines which alerts to load from both user and stock directories. This is a [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) list of alert or template names. Can be used to disable specific alerts. For example, `enabled alarms = !oom_kill *` will load all alerts except `oom_kill`. |
|
||||
|
||||
### [web] section options
|
||||
|
||||
|
|
@ -201,7 +201,7 @@ Additionally, there will be the following options:
|
|||
### [registry] section options
|
||||
|
||||
To understand what this section is and how it should be configured, please refer to
|
||||
the [registry documentation](https://github.com/netdata/netdata/blob/master/registry/README.md).
|
||||
the [registry documentation](https://github.com/netdata/netdata/blob/master/src/registry/README.md).
|
||||
|
||||
## Per-plugin configuration
|
||||
|
||||
|
|
|
|||
|
|
@ -4,10 +4,10 @@
|
|||
#define NETDATA_DYNCFG_INTERNALS_H
|
||||
|
||||
#include "../common.h"
|
||||
#include "../../database/rrd.h"
|
||||
#include "../../database/rrdfunctions.h"
|
||||
#include "../../database/rrdfunctions-internals.h"
|
||||
#include "../../database/rrdcollector-internals.h"
|
||||
#include "database/rrd.h"
|
||||
#include "database/rrdfunctions.h"
|
||||
#include "database/rrdfunctions-internals.h"
|
||||
#include "database/rrdcollector-internals.h"
|
||||
|
||||
typedef struct dyncfg {
|
||||
UUID host_uuid;
|
||||
|
|
|
|||
|
|
@ -4,8 +4,8 @@
|
|||
#define NETDATA_DYNCFG_H
|
||||
|
||||
#include "../common.h"
|
||||
#include "../../database/rrd.h"
|
||||
#include "../../database/rrdfunctions.h"
|
||||
#include "database/rrd.h"
|
||||
#include "database/rrdfunctions.h"
|
||||
|
||||
void dyncfg_add_streaming(BUFFER *wb);
|
||||
bool dyncfg_available_for_rrdhost(RRDHOST *host);
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@
|
|||
<mxGeometry x="1022" y="1032" width="208" height="158" as="geometry" />
|
||||
</mxCell>
|
||||
</UserObject>
|
||||
<UserObject label="<b><font style="font-size: 16px">Streaming</font></b><div>Database Replication</div>" link="https://github.com/netdata/netdata/tree/master/streaming" id="10">
|
||||
<UserObject label="<b><font style="font-size: 16px">Streaming</font></b><div>Database Replication</div>" link="https://github.com/netdata/netdata/tree/master/src/streaming" id="10">
|
||||
<mxCell style="whiteSpace=wrap;html=1;strokeColor=#59DE9C;fillColor=#FFFFFF;fontSize=14;align=center;" parent="1" vertex="1">
|
||||
<mxGeometry x="1034" y="690" width="202" height="97" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
@ -38,7 +38,7 @@
|
|||
<mxGeometry x="163" y="1034" width="110" height="60" as="geometry" />
|
||||
</mxCell>
|
||||
</UserObject>
|
||||
<UserObject label="<span>To another</span><div>netdata</div>" link="https://github.com/netdata/netdata/tree/master/streaming#options-for-the-sending-node" id="15">
|
||||
<UserObject label="<span>To another</span><div>netdata</div>" link="https://github.com/netdata/netdata/tree/master/src/streaming#options-for-the-sending-node" id="15">
|
||||
<mxCell style="ellipse;shape=cloud;whiteSpace=wrap;html=1;strokeColor=#59DE9C;fillColor=#FFFFFF;fontSize=14;align=center;" parent="1" vertex="1">
|
||||
<mxGeometry x="1090" y="557" width="150" height="120" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
@ -73,7 +73,7 @@
|
|||
<mxCell id="30" value="" style="whiteSpace=wrap;html=1;fillColor=#FFFFFF;strokeColor=#59DE9C;" parent="1" vertex="1">
|
||||
<mxGeometry x="674" y="887" width="557" height="130" as="geometry" />
|
||||
</mxCell>
|
||||
<UserObject label="<font style="font-size: 20px">metrics database</font><div><span style="font-weight: normal"><font style="font-size: 15px">(organized in hosts, charts and dimensions)</font></span></div>" link="https://github.com/netdata/netdata/tree/master/database#netdata-database" id="31">
|
||||
<UserObject label="<font style="font-size: 20px">metrics database</font><div><span style="font-weight: normal"><font style="font-size: 15px">(organized in hosts, charts and dimensions)</font></span></div>" link="https://github.com/netdata/netdata/tree/master/src/database#netdata-database" id="31">
|
||||
<mxCell style="whiteSpace=wrap;html=1;fontSize=18;fontStyle=1;fillColor=#FFFFFF;strokeColor=#59DE9C;" parent="1" vertex="1">
|
||||
<mxGeometry x="254" y="690" width="770" height="93" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
@ -129,7 +129,7 @@
|
|||
<mxGeometry x="404" y="1119" width="110" height="60" as="geometry" />
|
||||
</mxCell>
|
||||
</UserObject>
|
||||
<UserObject label="<b>remote netdata servers</b><div>database replication, streaming metrics in realtime<br>over TCP</div>" link="https://github.com/netdata/netdata/tree/master/streaming" id="43">
|
||||
<UserObject label="<b>remote netdata servers</b><div>database replication, streaming metrics in realtime<br>over TCP</div>" link="https://github.com/netdata/netdata/tree/master/src/streaming" id="43">
|
||||
<mxCell style="whiteSpace=wrap;html=1;fontSize=16;fillColor=#FFFFFF;strokeColor=#59DE9C;" parent="1" vertex="1">
|
||||
<mxGeometry x="706" y="1200" width="420" height="90" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
@ -219,7 +219,7 @@
|
|||
<mxGeometry x="1106" y="300" width="114" height="40" as="geometry" />
|
||||
</mxCell>
|
||||
</UserObject>
|
||||
<UserObject label="netdata<div><b><font style="font-size: 16px">registry</font></b></div><div><font style="font-size: 14px">my-netdata menu</font></div>" link="https://github.com/netdata/netdata/tree/master/registry#netdata-registry" id="89">
|
||||
<UserObject label="netdata<div><b><font style="font-size: 16px">registry</font></b></div><div><font style="font-size: 14px">my-netdata menu</font></div>" link="https://github.com/netdata/netdata/tree/master/src/registry#netdata-registry" id="89">
|
||||
<mxCell style="whiteSpace=wrap;html=1;strokeColor=#59DE9C;fillColor=#FFFFFF;fontSize=14;align=center;" parent="1" vertex="1">
|
||||
<mxGeometry x="74" y="607" width="170" height="176" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
@ -239,7 +239,7 @@
|
|||
<mxCell id="98" value="store &amp;<div>forward</div>" style="text;html=1;resizable=0;points=[];autosize=1;align=center;verticalAlign=top;spacingTop=-4;fontSize=14;" parent="1" vertex="1">
|
||||
<mxGeometry x="953" y="721" width="60" height="30" as="geometry" />
|
||||
</mxCell>
|
||||
<UserObject label="<span>from another</span><div>netdata</div>" link="https://github.com/netdata/netdata/tree/master/streaming#options-for-the-receiving-node" id="99">
|
||||
<UserObject label="<span>from another</span><div>netdata</div>" link="https://github.com/netdata/netdata/tree/master/src/streaming#options-for-the-receiving-node" id="99">
|
||||
<mxCell style="ellipse;shape=cloud;whiteSpace=wrap;html=1;strokeColor=#59DE9C;fillColor=#FFFFFF;fontSize=14;align=center;" parent="1" vertex="1">
|
||||
<mxGeometry x="1083" y="1184" width="150" height="120" as="geometry" />
|
||||
</mxCell>
|
||||
|
|
|
|||
|
|
@ -342,7 +342,7 @@ If your apache server is not on localhost, you can set:
|
|||
|
||||
*note: Netdata v1.9+ support `allow connections from`*
|
||||
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to match against the connection IP address.
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against the connection IP address.
|
||||
|
||||
## Prevent the double access.log
|
||||
|
||||
|
|
|
|||
|
|
@ -173,7 +173,7 @@ If your H2O server is not on localhost, you can set:
|
|||
|
||||
*note: Netdata v1.9+ support `allow connections from`*
|
||||
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to match against
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against
|
||||
the connection IP address.
|
||||
|
||||
## Prevent the double access.log
|
||||
|
|
|
|||
|
|
@ -236,7 +236,7 @@ If your Nginx server is not on localhost, you can set:
|
|||
|
||||
*note: Netdata v1.9+ support `allow connections from`*
|
||||
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to match against the
|
||||
`allow connections from` accepts [Netdata simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match against the
|
||||
connection IP address.
|
||||
|
||||
## Prevent the double access.log
|
||||
|
|
|
|||
|
|
@ -68,7 +68,7 @@ Starting with v1.21, we additionally collect information about:
|
|||
|
||||
- Failures to build the dependencies required to use Cloud features.
|
||||
- Unavailability of Cloud features in an agent.
|
||||
- Failures to connect to the Cloud in case the [connection process](https://github.com/netdata/netdata/blob/master/claim/README.md) has been completed. This includes error codes
|
||||
- Failures to connect to the Cloud in case the [connection process](https://github.com/netdata/netdata/blob/master/src/claim/README.md) has been completed. This includes error codes
|
||||
to inform the Netdata team about the reason why the connection failed.
|
||||
|
||||
To see exactly what and how is collected, you can review the script template `daemon/anonymous-statistics.sh.in`. The
|
||||
|
|
|
|||
|
|
@ -39,7 +39,7 @@ This section provides a quick overview of a few common deployment options. The n
|
|||
To help our users have a complete experience of Netdata when they install it for the first time, a Netdata Agent with default configuration
|
||||
is a complete monitoring solution out of the box, having all these features enabled and available.
|
||||
|
||||
The Agent will act as a _stand-alone_ Agent by default, and this is great to start out with for small setups and home labs. By [connecting each Agent to Cloud](https://github.com/netdata/netdata/blob/master/claim/README.md), you can see an overview of all your nodes, with aggregated charts and centralized alerting, without setting up a Parent.
|
||||
The Agent will act as a _stand-alone_ Agent by default, and this is great to start out with for small setups and home labs. By [connecting each Agent to Cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md), you can see an overview of all your nodes, with aggregated charts and centralized alerting, without setting up a Parent.
|
||||
|
||||
|
||||
|
||||
|
|
@ -71,7 +71,7 @@ The stand-alone setup is configured out of the box with reasonable defaults, but
|
|||
|
||||
### Parent – Child Deployment
|
||||
|
||||
For setups involving Child and Parent Agents, the Agents need to be configured for [_streaming_](https://github.com/netdata/netdata/blob/master/streaming/README.md), through the configuration file `stream.conf`. This will instruct the Child to stream data to the Parent and the Parent to accept streaming connections for one or more Child Agents. To secure this connection, both need set up a shared API key (to replace the string `API_KEY` in the examples below). Additionally, the Child is configured with one or more addresses of Parent Agents (`PARENT_IP_ADDRESS`).
|
||||
For setups involving Child and Parent Agents, the Agents need to be configured for [_streaming_](https://github.com/netdata/netdata/blob/master/src/streaming/README.md), through the configuration file `stream.conf`. This will instruct the Child to stream data to the Parent and the Parent to accept streaming connections for one or more Child Agents. To secure this connection, both need set up a shared API key (to replace the string `API_KEY` in the examples below). Additionally, the Child is configured with one or more addresses of Parent Agents (`PARENT_IP_ADDRESS`).
|
||||
|
||||
An API key is a key created with `uuidgen` and is used for authentication and/or customization in the Parent side. I.e. a Child will stream using the API key, and a Parent is configured to accept connections from Child, but can also apply different options for children by using multiple different API keys. The easiest setup uses just one API key for all Child Agents.
|
||||
|
||||
|
|
@ -130,7 +130,7 @@ Set the following parameters:
|
|||
|
||||
#### Parent config
|
||||
|
||||
For the Parent, besides setting up streaming, the example will also provide an example configuration of multiple [tiers](https://github.com/netdata/netdata/blob/master/database/engine/README.md#tiering) of metrics [storage](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md), for 10 children, with about 2k metrics each.
|
||||
For the Parent, besides setting up streaming, the example will also provide an example configuration of multiple [tiers](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiering) of metrics [storage](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md), for 10 children, with about 2k metrics each.
|
||||
|
||||
- 1s granularity at tier 0 for 1 week
|
||||
- 1m granularity at tier 1 for 1 month
|
||||
|
|
@ -242,7 +242,7 @@ We strongly recommend the following configuration changes for production deploym
|
|||
|
||||
To safeguard your infrastructure and comply with your organization's security policies.
|
||||
|
||||
2. Set up [streaming and replication](https://github.com/netdata/netdata/blob/master/streaming/README.md) to:
|
||||
2. Set up [streaming and replication](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) to:
|
||||
|
||||
- Offload Netdata Agents running on production systems and free system resources for the production applications running on them.
|
||||
- Isolate production systems from the rest of the world and improve security.
|
||||
|
|
|
|||
|
|
@ -24,7 +24,7 @@ either centrally, via the
|
|||
|
||||
We designed Netdata with interoperability in mind. The Agent collects thousands of metrics every second, and then what
|
||||
you do with them is up to you. You can
|
||||
[store metrics in the database engine](https://github.com/netdata/netdata/blob/master/database/README.md),
|
||||
[store metrics in the database engine](https://github.com/netdata/netdata/blob/master/src/database/README.md),
|
||||
or send them to another time series database for long-term storage or further analysis using
|
||||
Netdata's [exporting engine](https://github.com/netdata/netdata/edit/master/exporting/README.md).
|
||||
|
||||
|
|
|
|||
|
|
@ -107,7 +107,7 @@ static IP, only `localhost`, or connections from behind a management LAN.
|
|||
|
||||
By default, this setting is `localhost *`. This setting allows connections from `localhost` in addition to _all_
|
||||
connections, using the `*` wildcard. You can change this setting using Netdata's [simple
|
||||
patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md).
|
||||
patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
|
||||
|
||||
```conf
|
||||
[web]
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ To enable ML on your Netdata Agent, you need to edit the `[ml]` section in your
|
|||
enabled = yes
|
||||
```
|
||||
|
||||
At a minimum you just need to set `enabled = yes` to enable ML with default params. More details about configuration can be found in the [Netdata Agent ML docs](https://github.com/netdata/netdata/blob/master/ml/README.md#configuration).
|
||||
At a minimum you just need to set `enabled = yes` to enable ML with default params. More details about configuration can be found in the [Netdata Agent ML docs](https://github.com/netdata/netdata/blob/master/src/ml/README.md#configuration).
|
||||
|
||||
When you have finished your configuration, restart Netdata with a command like `sudo systemctl restart netdata` for the config changes to take effect. You can find more info on restarting Netdata [here](https://github.com/netdata/netdata/blob/master/docs/configure/start-stop-restart.md).
|
||||
|
||||
|
|
@ -52,7 +52,7 @@ The aim here is to surface the most anomalous metrics in the space or room for t
|
|||
|
||||
The "Anomaly Rate" chart shows the percentage of anomalous metrics over time per node. For example, in the following image, 3.21% of the metrics on the "ml-demo-ml-disabled" node were considered anomalous. This elevated anomaly rate could be a sign of something worth investigating.
|
||||
|
||||
**Note**: in this example the anomaly rates for this node are actually being calculated on the parent it streams to, you can run ml on the Agent itselt or on a parent the Agent stream to. Read more about the various configuration options in the [Agent docs](https://github.com/netdata/netdata/blob/master/ml/README.md).
|
||||
**Note**: in this example the anomaly rates for this node are actually being calculated on the parent it streams to, you can run ml on the Agent itselt or on a parent the Agent stream to. Read more about the various configuration options in the [Agent docs](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
|
||||
|
||||
|
||||
|
||||
|
|
@ -77,7 +77,7 @@ On the lower right hand side of the page an index of anomaly rates is displayed
|
|||
- If you are interested in a subset of specific nodes then filtering to just those nodes before highlighting tends to give better results. This is because when you highlight a region, Netdata Cloud will ask the Agents for a ranking over all metrics so if you can filter this early to just the subset of nodes you are interested in, less 'averaging' will occur and so you might be a less noisy ranking.
|
||||
- Ideally try and highlight close to a spike or window of interest so that the resulting ranking can narrow in more easily on the timeline you are interested in.
|
||||
|
||||
You can read more detail on how anomaly detection in the Netdata Agent works in our [Agent docs](https://github.com/netdata/netdata/blob/master/ml/README.md).
|
||||
You can read more detail on how anomaly detection in the Netdata Agent works in our [Agent docs](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
|
||||
|
||||
🚧 **Note**: This functionality is still **under active development** and considered experimental. We dogfood it internally and among early adopters within the Netdata community to build the feature. If you would like to get involved and help us with feedback, you can reach us through any of the following channels:
|
||||
|
||||
|
|
|
|||
|
|
@ -53,9 +53,9 @@ Behind the scenes, Netdata will aggregate the raw data as needed such that arbit
|
|||
|
||||
### Data
|
||||
|
||||
Netdata is different from typical observability agents since, in addition to just collecting raw metric values, it will by default also assign an "[Anomaly Bit](https://github.com/netdata/netdata/tree/master/ml#anomaly-bit---100--anomalous-0--normal)" related to each collected metric each second. This bit will be 0 for "normal" and 1 for "anomalous". This means that each metric also natively has an "[Anomaly Rate](https://github.com/netdata/netdata/tree/master/ml#anomaly-rate---averageanomaly-bit)" associated with it and, as such, MC can be run against the raw metric values or their corresponding anomaly rates.
|
||||
Netdata is different from typical observability agents since, in addition to just collecting raw metric values, it will by default also assign an "[Anomaly Bit](https://github.com/netdata/netdata/tree/master/src/ml#anomaly-bit---100--anomalous-0--normal)" related to each collected metric each second. This bit will be 0 for "normal" and 1 for "anomalous". This means that each metric also natively has an "[Anomaly Rate](https://github.com/netdata/netdata/tree/master/src/ml#anomaly-rate---averageanomaly-bit)" associated with it and, as such, MC can be run against the raw metric values or their corresponding anomaly rates.
|
||||
|
||||
**Note**: Read more [here](https://github.com/netdata/netdata/blob/master/ml/README.md) to learn more about the native anomaly detection features within netdata.
|
||||
**Note**: Read more [here](https://github.com/netdata/netdata/blob/master/src/ml/README.md) to learn more about the native anomaly detection features within netdata.
|
||||
|
||||
- `Metrics` - Run MC on the raw metric values.
|
||||
- `Anomaly Rate` - Run MC on the corresponding anomaly rate for each metric.
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@ will open a side tab in which you can:
|
|||
2. _Edit the War Rooms*_, click on the **War rooms** tab to add or remove War Rooms.
|
||||
|
||||
3. _Connect nodes*_, click on **Nodes** tab. Copy the claiming script to your node and run it. See the
|
||||
[connect to Cloud doc](https://github.com/netdata/netdata/blob/master/claim/README.md) for details.
|
||||
[connect to Cloud doc](https://github.com/netdata/netdata/blob/master/src/claim/README.md) for details.
|
||||
|
||||
4. _Manage the users*_, click on **Users**.
|
||||
The [invitation doc](#invite-your-team)
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ Inside the filter, the nodes get categorized into three groups:
|
|||
|
||||
| Group | Description |
|
||||
|---------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| Live | Nodes that are currently online, collecting and streaming metrics to Cloud. Live nodes display raised [Alert](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alerts.md) counters, [Machine Learning](https://github.com/netdata/netdata/blob/master/ml/README.md) availability, and [Functions](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-functions.md) availability |
|
||||
| Live | Nodes that are currently online, collecting and streaming metrics to Cloud. Live nodes display raised [Alert](https://github.com/netdata/netdata/blob/master/docs/monitor/view-active-alerts.md) counters, [Machine Learning](https://github.com/netdata/netdata/blob/master/src/ml/README.md) availability, and [Functions](https://github.com/netdata/netdata/blob/master/docs/cloud/netdata-functions.md) availability |
|
||||
| Stale | Nodes that are offline and not streaming metrics to Cloud. Only historical data can be presented from a parent node. For these nodes you can only see their ML status, as they are not online to provide more information |
|
||||
| Offline | Nodes that are offline, not streaming metrics to Cloud and not available in any parent node. Offline nodes are automatically deleted after 30 days and can also be deleted manually. |
|
||||
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ exist.
|
|||
- `health.d/` is a directory that contains [health configuration files](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md).
|
||||
- `health_alarm_notify.conf` enables and configures [alert notifications](https://github.com/netdata/netdata/blob/master/docs/monitor/enable-notifications.md).
|
||||
- `statsd.d/` is a directory for configuring Netdata's [statsd collector](https://github.com/netdata/netdata/blob/master/collectors/statsd.plugin/README.md).
|
||||
- `stream.conf` configures [parent-child streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md) between separate nodes running the Agent.
|
||||
- `stream.conf` configures [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) between separate nodes running the Agent.
|
||||
- `.environment` is a hidden file that describes the environment in which the Netdata Agent is installed, including the
|
||||
`PATH` and any installation options. Useful for [reinstalling](https://github.com/netdata/netdata/blob/master/packaging/installer/REINSTALL.md) or
|
||||
[uninstalling](https://github.com/netdata/netdata/blob/master/packaging/installer/UNINSTALL.md) the Agent.
|
||||
|
|
|
|||
|
|
@ -34,7 +34,7 @@ If you start the daemon this way, close it with `sudo killall netdata`.
|
|||
|
||||
## Using `netdatacli`
|
||||
|
||||
The Netdata Agent also comes with a [CLI tool](https://github.com/netdata/netdata/blob/master/cli/README.md) capable of performing shutdowns. Start the Agent back up
|
||||
The Netdata Agent also comes with a [CLI tool](https://github.com/netdata/netdata/blob/master/src/cli/README.md) capable of performing shutdowns. Start the Agent back up
|
||||
using your preferred method listed above.
|
||||
|
||||
```bash
|
||||
|
|
|
|||
|
|
@ -466,7 +466,7 @@ The following tables describe the standard spelling, capitalization, and usage o
|
|||
|
||||
| Term | Definition |
|
||||
|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](https://github.com/netdata/netdata/blob/master/claim/README.md). The claimed node will then appear in your Space and any War Rooms you added it to. |
|
||||
| **claimed node** | A node that you've proved ownership of by completing the [connecting to Cloud process](https://github.com/netdata/netdata/blob/master/src/claim/README.md). The claimed node will then appear in your Space and any War Rooms you added it to. |
|
||||
| **Netdata** | The company behind the open-source Netdata Agent and the Netdata Cloud web application. Never use _netdata_ or _NetData_. <br /><br />In general, focus on the user's goals, actions, and solutions rather than what the company provides. For example, write _Learn more about enabling alert notifications on your preferred platforms_ instead of _Netdata sends alert notifications to your preferred platforms_. |
|
||||
| **Netdata Agent** | The free and open source [monitoring agent](https://github.com/netdata/netdata) that you can install on all of your distributed systems, whether they're physical, virtual, containerized, ephemeral, and more. The Agent monitors systems running Linux, Docker, Kubernetes, macOS, FreeBSD, and more, and collects metrics from hundreds of popular services and applications. |
|
||||
| **Netdata Cloud** | The web application hosted at [https://app.netdata.cloud](https://app.netdata.cloud) that helps you monitor an entire infrastructure of distributed systems in real time. <br /><br />Never use _Cloud_ without the preceding _Netdata_ to avoid ambiguity. |
|
||||
|
|
|
|||
|
|
@ -142,9 +142,9 @@ metrics, troubleshoot complex performance problems, and make data interoperable
|
|||
|
||||
## R
|
||||
|
||||
- [**Registry**](https://github.com/netdata/netdata/blob/master/registry/README.md): Registry that allows Netdata to provide unified cross-server dashboards.
|
||||
- [**Registry**](https://github.com/netdata/netdata/blob/master/src/registry/README.md): Registry that allows Netdata to provide unified cross-server dashboards.
|
||||
|
||||
- [**Replication Streaming**](https://github.com/netdata/netdata/blob/master/streaming/README.md): Streaming configuration where child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
|
||||
- [**Replication Streaming**](https://github.com/netdata/netdata/blob/master/src/streaming/README.md): Streaming configuration where child `A`, _with_ a database and web dashboard, streams metrics to parent `B`.
|
||||
|
||||
- [**Room** or **War Room**](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-war-rooms): War Rooms organize your connected nodes and provide infrastructure-wide dashboards using real-time metrics and visualizations.
|
||||
|
||||
|
|
@ -160,7 +160,7 @@ metrics, troubleshoot complex performance problems, and make data interoperable
|
|||
|
||||
- [**Template Entity Type**](https://github.com/netdata/netdata/blob/master/health/REFERENCE.md#entity-types): Entity type that defines rules that apply to all charts of a specific context, and use the template label. Templates help you apply one entity to all disks, all network interfaces, all MySQL databases, and so on.
|
||||
|
||||
- [**Tiers**](https://github.com/netdata/netdata/blob/master/database/engine/README.md#tiers): Tiering is a mechanism of providing multiple tiers of data with different granularity of metrics (the frequency they are collected and stored, i.e. their resolution).
|
||||
- [**Tiers**](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#tiers): Tiering is a mechanism of providing multiple tiers of data with different granularity of metrics (the frequency they are collected and stored, i.e. their resolution).
|
||||
|
||||
## U
|
||||
|
||||
|
|
|
|||
|
|
@ -20,7 +20,7 @@ Optimization | CPU | RAM | Disk IO
|
|||
[Disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors) | :heavy_check_mark: | :heavy_check_mark: | :heavy_check_mark:
|
||||
[Reduce data collection frequency](#reduce-collection-frequency) | :heavy_check_mark: | | :heavy_check_mark:
|
||||
[Change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) | | :heavy_check_mark: | :heavy_check_mark:
|
||||
[Use a different metric storage database](https://github.com/netdata/netdata/blob/master/database/README.md) | | :heavy_check_mark: | :heavy_check_mark:
|
||||
[Use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md) | | :heavy_check_mark: | :heavy_check_mark:
|
||||
[Disable machine learning](#disable-machine-learning) | :heavy_check_mark: | |
|
||||
[Use a reverse proxy](#run-netdata-behind-a-proxy) | :heavy_check_mark: | |
|
||||
[Disable/lower gzip compression for the agent dashboard](#disablelower-gzip-compression-for-the-dashboard) | :heavy_check_mark: | |
|
||||
|
|
@ -57,7 +57,7 @@ To reduce CPU usage you can [disable machine learning](#disable-machine-learning
|
|||
|
||||
The memory footprint of Netdata is mainly influenced by the number of metrics concurrently being collected. Expect about 150MB of RAM for a typical 64-bit server collecting about 2000 to 3000 metrics.
|
||||
|
||||
To estimate and control memory consumption, you can [disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors), [change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md), or [use a different metric storage database](https://github.com/netdata/netdata/blob/master/database/README.md).
|
||||
To estimate and control memory consumption, you can [disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors), [change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md), or [use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md).
|
||||
|
||||
|
||||
### Disk footprint and I/O
|
||||
|
|
@ -67,7 +67,7 @@ By default, Netdata should not use more than 1GB of disk space, most of which is
|
|||
Netdata spreads I/O operations across time. For typical standalone installations there should be a few write operations every 5-10 seconds of a few kilobytes each, occasionally up to 1MB. In addition, under heavy load, collectors that require disk I/O may stop and show gaps in charts.
|
||||
|
||||
To configure retention, you can [change how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md).
|
||||
To control disk I/O [use a different metric storage database](https://github.com/netdata/netdata/blob/master/database/README.md), avoid querying the
|
||||
To control disk I/O [use a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md), avoid querying the
|
||||
production system [using streaming and replication](#use-streaming-and-replication), [reduce the data collection frequency](#reduce-collection-frequency), and [disable unneeded plugins or collectors](#disable-unneeded-plugins-or-collectors).
|
||||
|
||||
## Use streaming and replication
|
||||
|
|
@ -90,7 +90,7 @@ On the child nodes you should add to `netdata.conf` the following:
|
|||
|
||||
### Use memory mode ram or save for the child nodes
|
||||
|
||||
See [using a different metric storage database](https://github.com/netdata/netdata/blob/master/database/README.md).
|
||||
See [using a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md).
|
||||
|
||||
## Disable unneeded plugins or collectors
|
||||
|
||||
|
|
@ -180,7 +180,7 @@ See how to [change how long Netdata stores metrics](https://github.com/netdata/n
|
|||
|
||||
## Use a different metric storage database
|
||||
|
||||
Consider [using a different metric storage database](https://github.com/netdata/netdata/blob/master/database/README.md) when running Netdata on IoT devices,
|
||||
Consider [using a different metric storage database](https://github.com/netdata/netdata/blob/master/src/database/README.md) when running Netdata on IoT devices,
|
||||
and for children in a parent-child set up based on [streaming and replication](https://github.com/netdata/netdata/blob/master/docs/metrics-storage-management/enable-streaming.md).
|
||||
|
||||
## Disable machine learning
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ learn_rel_path: "Operations"
|
|||
|
||||
As of [`v1.32.0`](https://github.com/netdata/netdata/releases/tag/v1.32.0), Netdata comes with some ML powered [anomaly detection](https://en.wikipedia.org/wiki/Anomaly_detection) capabilities built into it and available to use out of the box, with zero configuration required (ML was enabled by default in `v1.35.0-29-nightly` in [this PR](https://github.com/netdata/netdata/pull/13158), previously it required a one line config change).
|
||||
|
||||
This means that in addition to collecting raw value metrics, the Netdata agent will also produce an [`anomaly-bit`](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-bit---100--anomalous-0--normal) every second which will be `100` when recent raw metric values are considered anomalous by Netdata and `0` when they look normal. Once we aggregate beyond one second intervals this aggregated `anomaly-bit` becomes an ["anomaly rate"](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate---averageanomaly-bit).
|
||||
This means that in addition to collecting raw value metrics, the Netdata agent will also produce an [`anomaly-bit`](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-bit---100--anomalous-0--normal) every second which will be `100` when recent raw metric values are considered anomalous by Netdata and `0` when they look normal. Once we aggregate beyond one second intervals this aggregated `anomaly-bit` becomes an ["anomaly rate"](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate---averageanomaly-bit).
|
||||
|
||||
To be as concrete as possible, the below api call shows how to access the raw anomaly bit of the `system.cpu` chart from the [london.my-netdata.io](https://london.my-netdata.io) Netdata demo server. Passing `options=anomaly-bit` returns the anomaly bit instead of the raw metric value.
|
||||
|
||||
|
|
@ -23,19 +23,19 @@ To be as concrete as possible, the below api call shows how to access the raw an
|
|||
https://london.my-netdata.io/api/v1/data?chart=system.cpu&options=anomaly-bit
|
||||
```
|
||||
|
||||
If we aggregate the above to just 1 point by adding `points=1` we get an "[Anomaly Rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate---averageanomaly-bit)":
|
||||
If we aggregate the above to just 1 point by adding `points=1` we get an "[Anomaly Rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate---averageanomaly-bit)":
|
||||
|
||||
```
|
||||
https://london.my-netdata.io/api/v1/data?chart=system.cpu&options=anomaly-bit&points=1
|
||||
```
|
||||
|
||||
The fundamentals of Netdata's anomaly detection approach and implementation are covered in lots more detail in the [agent ML documentation](https://github.com/netdata/netdata/blob/master/ml/README.md).
|
||||
The fundamentals of Netdata's anomaly detection approach and implementation are covered in lots more detail in the [agent ML documentation](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
|
||||
|
||||
This guide will explain how to get started using these ML based anomaly detection capabilities within Netdata.
|
||||
|
||||
## Anomaly Advisor
|
||||
|
||||
The [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/anomaly-advisor.md) is the flagship anomaly detection feature within Netdata. In the "Anomalies" tab of Netdata you will see an overall "Anomaly Rate" chart that aggregates node level anomaly rate for all nodes in a space. The aim of this chart is to make it easy to quickly spot periods of time where the overall "[node anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#node-anomaly-rate)" is elevated in some unusual way and for what node or nodes this relates to.
|
||||
The [Anomaly Advisor](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/anomaly-advisor.md) is the flagship anomaly detection feature within Netdata. In the "Anomalies" tab of Netdata you will see an overall "Anomaly Rate" chart that aggregates node level anomaly rate for all nodes in a space. The aim of this chart is to make it easy to quickly spot periods of time where the overall "[node anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#node-anomaly-rate)" is elevated in some unusual way and for what node or nodes this relates to.
|
||||
|
||||
|
||||
|
||||
|
|
@ -66,7 +66,7 @@ You can see some example ML based alert configurations below:
|
|||
|
||||
Check out the resources below to learn more about how Netdata is approaching ML:
|
||||
|
||||
- [Agent ML documentation](https://github.com/netdata/netdata/blob/master/ml/README.md).
|
||||
- [Agent ML documentation](https://github.com/netdata/netdata/blob/master/src/ml/README.md).
|
||||
- [Anomaly Advisor documentation](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/anomaly-advisor.md).
|
||||
- [Metric Correlations documentation](https://github.com/netdata/netdata/blob/master/docs/cloud/insights/metric-correlations.md).
|
||||
- Anomaly Advisor [launch blog post](https://www.netdata.cloud/blog/introducing-anomaly-advisor-unsupervised-anomaly-detection-in-netdata/).
|
||||
|
|
|
|||
|
|
@ -159,7 +159,7 @@ If the Netdata Agent isn't already open in your browser, open a new tab and navi
|
|||
|
||||
> If you [signed up](https://app.netdata.cloud/sign-up?cloudRoute=/spaces) for Netdata Cloud earlier, you can also view
|
||||
> the exact same LAMP stack metrics there, plus additional features, like drag-and-drop custom dashboards. Be sure to
|
||||
> [connecting your node](https://github.com/netdata/netdata/blob/master/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
|
||||
> [connecting your node](https://github.com/netdata/netdata/blob/master/src/claim/README.md) to start streaming metrics to your browser through Netdata Cloud.
|
||||
|
||||
Netdata automatically organizes all metrics and charts onto a single page for easy navigation. Peek at gauges to see
|
||||
overall system performance, then scroll down to see more. Click-and-drag with your mouse to pan _all_ charts back and
|
||||
|
|
|
|||
|
|
@ -125,7 +125,7 @@ Raspberry Pi temperature sensor monitoring.
|
|||
### Storing historical metrics on your Raspberry Pi
|
||||
|
||||
By default, Netdata allocates 256 MiB in disk space to store historical metrics inside the [database
|
||||
engine](https://github.com/netdata/netdata/blob/master/database/engine/README.md). On the Raspberry Pi used for this guide, Netdata collects 1,500 metrics every
|
||||
engine](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md). On the Raspberry Pi used for this guide, Netdata collects 1,500 metrics every
|
||||
second, which equates to storing 3.5 days worth of historical metrics.
|
||||
|
||||
You can increase this allocation by editing `netdata.conf` and increasing the `dbengine multihost disk space` setting to
|
||||
|
|
@ -138,5 +138,5 @@ more than 256.
|
|||
|
||||
Use our [database sizing
|
||||
calculator](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md#calculate-the-system-resources-ram-disk-space-needed-to-store-metrics)
|
||||
and the [Database configuration documentation](https://github.com/netdata/netdata/blob/master/database/README.md) to help you determine the right
|
||||
and the [Database configuration documentation](https://github.com/netdata/netdata/blob/master/src/database/README.md) to help you determine the right
|
||||
setting for your Raspberry Pi.
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ and firewall settings for outbound connections.
|
|||
|
||||
If your firewall is configured to completely prevent outbound connections, you need to whitelist `app.netdata.cloud` and `mqtt.netdata.cloud`. If you can't whitelist domains in your firewall, you can whitelist the IPs that the hostnames resolve to, but keep in mind that they can change without any notice.
|
||||
|
||||
If you use an outbound proxy, you need to [take some extra steps]( https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy).
|
||||
If you use an outbound proxy, you need to [take some extra steps]( https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy).
|
||||
|
||||
### Troubleshoot claiming with kickstart.sh
|
||||
|
||||
|
|
@ -48,7 +48,7 @@ and can be executed.
|
|||
First verify that the NETDATA_CLAIM_TOKEN parameter is correctly configured and then check for any errors during
|
||||
initialization of the container.
|
||||
|
||||
The most common issue we have seen claiming nodes in Docker is [running on older hosts with seccomp enabled](https://github.com/netdata/netdata/blob/master/claim/README.md#known-issues-on-older-hosts-with-seccomp-enabled).
|
||||
The most common issue we have seen claiming nodes in Docker is [running on older hosts with seccomp enabled](https://github.com/netdata/netdata/blob/master/src/claim/README.md#known-issues-on-older-hosts-with-seccomp-enabled).
|
||||
|
||||
## The Agent was claimed but can not connect
|
||||
|
||||
|
|
|
|||
|
|
@ -139,7 +139,7 @@ child system. It's a vastly simplified way of accessing critical information abo
|
|||
|
||||
> ⚠️ Because automatic labels for child nodes are accessible via API calls, and contain sensitive information like
|
||||
> kernel and operating system versions, you should secure streaming connections with SSL. See the [streaming
|
||||
> documentation](https://github.com/netdata/netdata/blob/master/streaming/README.md#securing-streaming-communications) for details. You may also want to use
|
||||
> documentation](https://github.com/netdata/netdata/blob/master/src/streaming/README.md#securing-streaming-communications) for details. You may also want to use
|
||||
> [access lists](https://github.com/netdata/netdata/blob/master/web/server/README.md#access-lists) or [expose the API only to LAN/localhost
|
||||
> connections](https://github.com/netdata/netdata/blob/master/docs/netdata-security.md#expose-netdata-only-in-a-private-lan).
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ Streaming lets you decide exactly how you want to store and maintain metrics dat
|
|||
ideal for speed and scale, streaming provides centralization options and high data availability.
|
||||
|
||||
This document will get you started quickly with streaming. More advanced concepts and suggested production deployments
|
||||
can be found in the [streaming and replication reference](https://github.com/netdata/netdata/blob/master/streaming/README.md).
|
||||
can be found in the [streaming and replication reference](https://github.com/netdata/netdata/blob/master/src/streaming/README.md).
|
||||
|
||||
## Streaming basics
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
# Change how long Netdata stores metrics
|
||||
|
||||
The Netdata Agent uses a custom made time-series database (TSDB), named the
|
||||
[`dbengine`](https://github.com/netdata/netdata/blob/master/database/engine/README.md), to store metrics.
|
||||
[`dbengine`](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md), to store metrics.
|
||||
|
||||
To see the number of metrics stored and the retention in days per tier, use the `/api/v1/dbengine_stats` endpoint.
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ The DBENGINE memory is related to the number of metrics concurrently being colle
|
|||
on disk in relation with the queries running, and the number of metrics for which retention is maintained.
|
||||
|
||||
The precise analysis of how much memory will be used by the DBENGINE itself is described in
|
||||
[DBENGINE memory requirements](https://github.com/netdata/netdata/blob/master/database/engine/README.md#memory-requirements).
|
||||
[DBENGINE memory requirements](https://github.com/netdata/netdata/blob/master/src/database/engine/README.md#memory-requirements).
|
||||
|
||||
In addition to the DBENGINE, Netdata uses memory for contexts, metric labels (e.g. in a Kubernetes setup),
|
||||
other Netdata structures/processes (e.g. Health) and system overhead.
|
||||
|
|
|
|||
|
|
@ -52,7 +52,7 @@ appropriate amount of RAM and disk space.
|
|||
Read our document on changing [how long Netdata stores metrics](https://github.com/netdata/netdata/blob/master/docs/store/change-metrics-storage.md) on your nodes for
|
||||
details.
|
||||
|
||||
You can also stream between nodes using [streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md), allowing to replicate databases and create
|
||||
You can also stream between nodes using [streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md), allowing to replicate databases and create
|
||||
your own centralized data lake of metrics, if you choose to do so.
|
||||
|
||||
While a distributed data architecture is the default when monitoring infrastructure with Netdata, you can also configure
|
||||
|
|
|
|||
|
|
@ -76,7 +76,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 2 * update_every * 1000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@ setup:
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -98,7 +98,7 @@
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 2 * update_every * 1000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -91,7 +91,7 @@ setup:
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 2 * update_every * 1000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -97,7 +97,7 @@ setup:
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -62,7 +62,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 2 * update_every * 1000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to OpenTSDB. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to OpenTSDB. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -96,7 +96,7 @@ setup:
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to OpenTSDB. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to OpenTSDB. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -223,7 +223,7 @@ Netdata can filter the metrics it sends to Prometheus with this setting:
|
|||
```
|
||||
|
||||
This settings accepts a space separated list
|
||||
of [simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to match the
|
||||
of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to match the
|
||||
**charts** to be sent to Prometheus. Each pattern can use `*` as wildcard, any number of times (e.g `*a*b*c*` is valid).
|
||||
Patterns starting with `!` give a negative match (e.g `!*.bad users.* groups.*` will send all the users and groups
|
||||
except `bad` user and `bad` group). The order is important: the first match (positive or negative) left to right, is
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -67,7 +67,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 20000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -99,7 +99,7 @@
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -64,7 +64,7 @@ The following options can be defined for this exporter.
|
|||
| update every | Frequency of sending sending data to the external database, in seconds. | 10 | no |
|
||||
| buffer on failures | The number of iterations (`update every` seconds) to buffer data, when the external database server is not available. | 10 | no |
|
||||
| timeout ms | The timeout in milliseconds to wait for the external database server to process the data. | 2 * update_every * 1000 | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send hosts matching | Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns). | localhost * | no |
|
||||
| send charts matching | One or more space separated patterns (use * as wildcard) checked against both chart id and chart name. | * | no |
|
||||
| send names instead of ids | Controls the metric names Netdata should send to the external database (yes/no). | | no |
|
||||
| send configured labels | Controls if host labels defined in the `[host labels]` section in `netdata.conf` should be sent to the external database (yes/no). | | no |
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@ setup:
|
|||
- name: 'send hosts matching'
|
||||
default_value: 'localhost *'
|
||||
description: |
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/libnetdata/simple_pattern#simple-patterns).
|
||||
Hosts filter. Determines which hosts will be sent to the external database. The syntax is [simple patterns](https://github.com/netdata/netdata/tree/master/src/libnetdata/simple_pattern#simple-patterns).
|
||||
required: false
|
||||
detailed_description: |
|
||||
Includes one or more space separated patterns, using * as wildcard (any number of times within each pattern).
|
||||
|
|
|
|||
|
|
@ -82,7 +82,7 @@ In the `netdata.conf` `[health]` section, set `enabled` to `no`, and restart the
|
|||
### Disable some alerts
|
||||
|
||||
In the `netdata.conf` `[health]` section, set `enabled alarms` to a
|
||||
[simple pattern](https://github.com/netdata/netdata/edit/master/libnetdata/simple_pattern/README.md) that
|
||||
[simple pattern](https://github.com/netdata/netdata/edit/master/src/libnetdata/simple_pattern/README.md) that
|
||||
excludes one or more alerts. e.g. `enabled alarms = !oom_kill *` will load all alerts except `oom_kill`.
|
||||
|
||||
You can also [edit the file where the alert is defined](#edit-individual-alerts), comment out its definition,
|
||||
|
|
@ -216,7 +216,7 @@ Netdata parses the following lines. Beneath the table is an in-depth explanation
|
|||
- The `every` line is **required** if not using `lookup`.
|
||||
- Each entity **must** have at least one of the following lines: `lookup`, `calc`, `warn`, or `crit`.
|
||||
- A few lines use space-separated lists to define how the entity behaves. You can use `*` as a wildcard or prefix with
|
||||
`!` for a negative match. Order is important, too! See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) for
|
||||
`!` for a negative match. Order is important, too! See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for
|
||||
more examples.
|
||||
- Lines terminated by a `\` are spliced together with the next line. The backslash is removed and the following line is
|
||||
joined with the current one. No space is inserted, so you may split a line anywhere, even in the middle of a word.
|
||||
|
|
@ -402,7 +402,7 @@ hosts: server1 server2 database* !redis3 redis*
|
|||
#### Alert line `plugin`
|
||||
|
||||
The `plugin` line filters which plugin within the context this alert should apply to. The value is a space-separated
|
||||
list of [simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). For example,
|
||||
list of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). For example,
|
||||
you can create a filter for an alert that applies specifically to `python.d.plugin`:
|
||||
|
||||
```yaml
|
||||
|
|
@ -416,7 +416,7 @@ comprehensive example using both.
|
|||
#### Alert line `module`
|
||||
|
||||
The `module` line filters which module within the context this alert should apply to. The value is a space-separated
|
||||
list of [simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). For
|
||||
list of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). For
|
||||
example, you can create an alert that applies only on the `isc_dhcpd` module started by `python.d.plugin`:
|
||||
|
||||
```yaml
|
||||
|
|
@ -428,7 +428,7 @@ module: isc_dhcpd
|
|||
|
||||
The `charts` line filters which chart this alert should apply to. It is only available on entities using the
|
||||
[`template`](#alert-line-alarm-or-template) line.
|
||||
The value is a space-separated list of [simple patterns](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md). For
|
||||
The value is a space-separated list of [simple patterns](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md). For
|
||||
example, a template that applies to `disk.svctm` (Average Service Time) context, but excludes the disk `sdb` from alerts:
|
||||
|
||||
```yaml
|
||||
|
|
@ -685,7 +685,7 @@ that will be applied to all hosts installed in the last decade with the followin
|
|||
host labels: installed = 201*
|
||||
```
|
||||
|
||||
See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) for more examples.
|
||||
See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for more examples.
|
||||
|
||||
#### Alert line `chart labels`
|
||||
|
||||
|
|
@ -714,7 +714,7 @@ chart labels: mount_point=/mnt/disk1 device=sda
|
|||
Will create the alert if the `mount_point` is `/mnt/disk1` or the `device` is `sda`. Furthermore, if a chart label name
|
||||
is specified that does not exist in the chart, the chart won't be matched.
|
||||
|
||||
See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) for more examples.
|
||||
See our [simple patterns docs](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) for more examples.
|
||||
|
||||
#### Alert line `summary`
|
||||
|
||||
|
|
@ -1141,9 +1141,9 @@ lookup: mean -10s of user
|
|||
|
||||
Since [`z = (x - mean) / stddev`](https://en.wikipedia.org/wiki/Standard_score) we create two input alerts, one for `mean` and one for `stddev` and then use them both as inputs in our final `cpu_user_zscore` alert.
|
||||
|
||||
### Example 8 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) based CPU dimensions alert
|
||||
### Example 8 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) based CPU dimensions alert
|
||||
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) for any CPU dimension is above 5%, critical if it goes above 20%:
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) for any CPU dimension is above 5%, critical if it goes above 20%:
|
||||
|
||||
```yaml
|
||||
template: ml_5min_cpu_dims
|
||||
|
|
@ -1162,9 +1162,9 @@ template: ml_5min_cpu_dims
|
|||
The `lookup` line will calculate the average anomaly rate of each `system.cpu` dimension over the last 5 minues. In this case
|
||||
Netdata will create alerts for all dimensions of the chart.
|
||||
|
||||
### Example 9 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) based CPU chart alert
|
||||
### Example 9 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) based CPU chart alert
|
||||
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) averaged across all CPU dimensions is above 5%, critical if it goes above 20%:
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) averaged across all CPU dimensions is above 5%, critical if it goes above 20%:
|
||||
|
||||
```yaml
|
||||
template: ml_5min_cpu_chart
|
||||
|
|
@ -1183,9 +1183,9 @@ template: ml_5min_cpu_chart
|
|||
The `lookup` line will calculate the average anomaly rate across all `system.cpu` dimensions over the last 5 minues. In this case
|
||||
Netdata will create one alert for the chart.
|
||||
|
||||
### Example 10 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) based node level alert
|
||||
### Example 10 - [Anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) based node level alert
|
||||
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#anomaly-rate) averaged across all ML enabled dimensions is above 5%, critical if it goes above 20%:
|
||||
Warning if 5 minute rolling [anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#anomaly-rate) averaged across all ML enabled dimensions is above 5%, critical if it goes above 20%:
|
||||
|
||||
```yaml
|
||||
template: ml_5min_node
|
||||
|
|
@ -1201,7 +1201,7 @@ template: ml_5min_node
|
|||
info: rolling 5min anomaly rate for all ML enabled dims
|
||||
```
|
||||
|
||||
The `lookup` line will use the `anomaly_rate` dimension of the `anomaly_detection.anomaly_rate` ML chart to calculate the average [node level anomaly rate](https://github.com/netdata/netdata/blob/master/ml/README.md#node-anomaly-rate) over the last 5 minues.
|
||||
The `lookup` line will use the `anomaly_rate` dimension of the `anomaly_detection.anomaly_rate` ML chart to calculate the average [node level anomaly rate](https://github.com/netdata/netdata/blob/master/src/ml/README.md#node-anomaly-rate) over the last 5 minues.
|
||||
|
||||
## Use dimension templates to create dynamic alerts
|
||||
|
||||
|
|
@ -1222,7 +1222,7 @@ is where the magic happens.
|
|||
|
||||
You use the `foreach` parameter to specify which dimensions you want to monitor with this single alert. You can separate
|
||||
them with a comma (`,`) or a pipe (`|`). You can also use
|
||||
a [Netdata simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md) to create
|
||||
a [Netdata simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md) to create
|
||||
many alerts with a regex-like syntax.
|
||||
|
||||
The `foreach` parameter _has_ to be the last parameter in your `lookup` line, and if you have both `of` and `foreach` in
|
||||
|
|
@ -1293,7 +1293,7 @@ Let's look at some other examples of how `foreach` works, so you can best apply
|
|||
In the last example, we used `foreach system,user,nice` to create three distinct alerts using dimension templates. But
|
||||
what if you want to quickly create alerts for _all_ the dimensions of a given chart?
|
||||
|
||||
Use a [simple pattern](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md)! One example of a simple pattern is a single wildcard
|
||||
Use a [simple pattern](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md)! One example of a simple pattern is a single wildcard
|
||||
(`*`).
|
||||
|
||||
Instead of monitoring system CPU usage, let's monitor per-application CPU usage using the `apps.cpu` chart. Passing a
|
||||
|
|
@ -1312,7 +1312,7 @@ This entity will now create alerts for every dimension in the `apps.cpu` chart.
|
|||
10 or more dimensions, using the wildcard ensures you catch every CPU-hogging process.
|
||||
|
||||
To learn more about how to use simple patterns with dimension templates, see
|
||||
our [simple patterns documentation](https://github.com/netdata/netdata/blob/master/libnetdata/simple_pattern/README.md).
|
||||
our [simple patterns documentation](https://github.com/netdata/netdata/blob/master/src/libnetdata/simple_pattern/README.md).
|
||||
|
||||
### Using `foreach` with alert templates
|
||||
|
||||
|
|
|
|||
|
|
@ -113,7 +113,7 @@ export NETDATA_ALARM_NOTIFY_DEBUG=1
|
|||
/usr/libexec/netdata/plugins.d/alarm-notify.sh test "ROLE"
|
||||
```
|
||||
|
||||
If you are [running your own registry](https://github.com/netdata/netdata/blob/master/registry/README.md#run-your-own-registry), add `export NETDATA_REGISTRY_URL=[YOUR_URL]` before calling `alarm-notify.sh`.
|
||||
If you are [running your own registry](https://github.com/netdata/netdata/blob/master/src/registry/README.md#run-your-own-registry), add `export NETDATA_REGISTRY_URL=[YOUR_URL]` before calling `alarm-notify.sh`.
|
||||
|
||||
> If you need to dig even deeper, you can trace the execution with `bash -x`. Note that in test mode, `alarm-notify.sh` calls itself with many more arguments. So first do:
|
||||
>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
// SPDX-License-Identifier: GPL-3.0-or-later
|
||||
|
||||
#include "../database/rrd.h"
|
||||
#include "../web/api/queries/rrdr.h"
|
||||
#include "database/rrd.h"
|
||||
#include "web/api/queries/rrdr.h"
|
||||
#include "health_prototypes.h"
|
||||
|
||||
#ifndef NETDATA_RRDCALC_H
|
||||
|
|
|
|||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
|
|
@ -7,7 +7,7 @@
|
|||
#ifndef DB_API_H_
|
||||
#define DB_API_H_
|
||||
|
||||
#include "../database/sqlite/sqlite3.h"
|
||||
#include "database/sqlite/sqlite3.h"
|
||||
#include <uv.h>
|
||||
#include "query.h"
|
||||
#include "file_info.h"
|
||||
|
|
|
|||
|
|
@ -9,7 +9,7 @@
|
|||
#define FILE_INFO_H_
|
||||
|
||||
#include <uv.h>
|
||||
#include "../database/sqlite/sqlite3.h"
|
||||
#include "database/sqlite/sqlite3.h"
|
||||
#include "defaults.h"
|
||||
#include "parser.h"
|
||||
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@
|
|||
#ifndef FUNCTIONS_H_
|
||||
#define FUNCTIONS_H_
|
||||
|
||||
#include "../database/rrdfunctions.h"
|
||||
#include "database/rrdfunctions.h"
|
||||
|
||||
#define LOGS_MANAG_FUNC_NAME "logs-management"
|
||||
#define FUNCTION_LOGSMANAGEMENT_HELP_SHORT "View, search and analyze logs monitored through the logs management engine."
|
||||
|
|
@ -19,4 +19,4 @@ int logsmanagement_function_execute_cb( BUFFER *dest_wb, int timeout,
|
|||
|
||||
struct functions_evloop_globals *logsmanagement_func_facets_init(bool *p_logsmanagement_should_exit);
|
||||
|
||||
#endif // FUNCTIONS_H_
|
||||
#endif // FUNCTIONS_H_
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ learn_rel_path: "Installation/Install on specific environments"
|
|||
|
||||
Netdata is fully compatible with Amazon Web Services (AWS).
|
||||
You can install Netdata on cloud instances to monitor the apps/services running there, or use
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md) configuration.
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
|
||||
|
||||
## Recommended installation method
|
||||
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ learn_rel_path: "Installation/Install on specific environments"
|
|||
|
||||
Netdata is fully compatible with Azure.
|
||||
You can install Netdata on cloud instances to monitor the apps/services running there, or use
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md) configuration.
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
|
||||
|
||||
## Recommended installation method
|
||||
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ learn_rel_path: "Installation/Install on specific environments"
|
|||
|
||||
Netdata is fully compatible with the Google Cloud Platform (GCP).
|
||||
You can install Netdata on cloud instances to monitor the apps/services running there, or use
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/streaming/README.md) configuration.
|
||||
multiple instances in a [parent-child streaming](https://github.com/netdata/netdata/blob/master/src/streaming/README.md) configuration.
|
||||
|
||||
## Recommended installation method
|
||||
|
||||
|
|
|
|||
|
|
@ -147,7 +147,7 @@ By default, the kickstart script will provide a Netdata agent installation that
|
|||
- `--claim-rooms`
|
||||
Specify a comma-separated list of tokens for each War Room this node should appear in.
|
||||
- `--claim-proxy`
|
||||
Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy. See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy) for details.
|
||||
Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy. See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy) for details.
|
||||
- `--claim-only`
|
||||
If there is an existing install, only try to claim it without attempting to update it. If there is no existing install, install and claim Netdata normally.
|
||||
- `--require-cloud`
|
||||
|
|
|
|||
|
|
@ -10,7 +10,7 @@ learn_rel_path: "Installation/Install on specific environments"
|
|||
|
||||
Netdata works on macOS, albeit with some limitations.
|
||||
The number of charts displaying system metrics is limited, but you can use any of Netdata's [external plugins](https://github.com/netdata/netdata/blob/master/collectors/plugins.d/README.md) to monitor any services you might have installed on your macOS system.
|
||||
You could also use a macOS system as the parent node in a [streaming configuration](https://github.com/netdata/netdata/blob/master/streaming/README.md).
|
||||
You could also use a macOS system as the parent node in a [streaming configuration](https://github.com/netdata/netdata/blob/master/src/streaming/README.md).
|
||||
|
||||
You can install Netdata in one of the three following ways:
|
||||
|
||||
|
|
@ -35,7 +35,7 @@ The Netdata Agent is installed under `/usr/local/netdata`. Dependencies are hand
|
|||
|
||||
**Automatically connect to Netdata Cloud during installation**
|
||||
|
||||
The `kickstart.sh` script accepts additional parameters to automatically [connect](https://github.com/netdata/netdata/blob/master/claim/README.md) your node to Netdata
|
||||
The `kickstart.sh` script accepts additional parameters to automatically [connect](https://github.com/netdata/netdata/blob/master/src/claim/README.md) your node to Netdata
|
||||
Cloud immediately after installation. Find the `token` and `rooms` strings by [signing in to Netdata
|
||||
Cloud](https://app.netdata.cloud/sign-in?cloudRoute=/spaces), then clicking on **Connect Nodes** in the [Spaces management
|
||||
area](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-your-infrastrucutre-invite-your-team.md#netdata-cloud-spaces).
|
||||
|
|
@ -44,7 +44,7 @@ area](https://github.com/netdata/netdata/blob/master/docs/cloud/manage/organize-
|
|||
after the install.
|
||||
- `--claim-rooms`: Specify a comma-separated list of tokens for each War Room this node should appear in.
|
||||
- `--claim-proxy`: Specify a proxy to use when connecting to the cloud in the form of `http://[user:pass@]host:ip` for an HTTP(S) proxy.
|
||||
See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/claim/README.md#connect-through-a-proxy) for details.
|
||||
See [connecting through a proxy](https://github.com/netdata/netdata/blob/master/src/claim/README.md#connect-through-a-proxy) for details.
|
||||
- `--claim-url`: Specify a URL to use when connecting to the cloud. Defaults to `https://app.netdata.cloud`.
|
||||
|
||||
For example:
|
||||
|
|
@ -53,7 +53,7 @@ curl https://get.netdata.cloud/kickstart.sh > /tmp/netdata-kickstart.sh && sh /t
|
|||
```
|
||||
The Netdata Agent is installed under `/usr/local/netdata` on your machine. Your machine will also show up as a node in your Netdata Cloud.
|
||||
|
||||
If you experience issues while claiming your node, follow the steps in our [Troubleshooting](https://github.com/netdata/netdata/blob/master/claim/README.md#troubleshooting) documentation.
|
||||
If you experience issues while claiming your node, follow the steps in our [Troubleshooting](https://github.com/netdata/netdata/blob/master/src/claim/README.md#troubleshooting) documentation.
|
||||
## Install Netdata via Homebrew
|
||||
|
||||
### For macOS Intel
|
||||
|
|
|
|||
|
|
@ -218,9 +218,9 @@ cd netdata
|
|||
### Connect node to Netdata Cloud during installation
|
||||
|
||||
Unlike the [`kickstart.sh`](https://github.com/netdata/netdata/blob/master/packaging/installer/methods/kickstart.md), the `netdata-installer.sh` script does
|
||||
not allow you to automatically [connect](https://github.com/netdata/netdata/blob/master/claim/README.md) your node to Netdata Cloud immediately after installation.
|
||||
not allow you to automatically [connect](https://github.com/netdata/netdata/blob/master/src/claim/README.md) your node to Netdata Cloud immediately after installation.
|
||||
|
||||
See the [connect to cloud](https://github.com/netdata/netdata/blob/master/claim/README.md) doc for details on connecting a node with a manual installation of Netdata.
|
||||
See the [connect to cloud](https://github.com/netdata/netdata/blob/master/src/claim/README.md) doc for details on connecting a node with a manual installation of Netdata.
|
||||
|
||||
### 'nonrepresentable section on output' errors
|
||||
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue