diff options
author | Fotis Voutsas <fotis@netdata.cloud> | 2023-02-28 16:52:53 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-02-28 06:52:53 -0800 |
commit | e9af6180814ea456cabc424880cd80f7a23d1e23 (patch) | |
tree | e7b0592f1026ade672a6f61835ab423eb5b63331 /libnetdata | |
parent | 380e2b261b38677747c9f09ac9bc2d2550846fb2 (diff) |
Make the title metadata H1 in all markdown files (#14625)
* make the title metadta the H1
* Update collectors/python.d.plugin/zscores/README.md
* Update libnetdata/ebpf/README.md
* Update ml/README.md
* Update libnetdata/string/README.md
---------
Co-authored-by: Chris Akritidis <43294513+cakrit@users.noreply.github.com>
Diffstat (limited to 'libnetdata')
-rw-r--r-- | libnetdata/clocks/README.md | 2 | ||||
-rw-r--r-- | libnetdata/locks/README.md | 2 | ||||
-rw-r--r-- | libnetdata/parser/README.md | 4 |
3 files changed, 7 insertions, 1 deletions
diff --git a/libnetdata/clocks/README.md b/libnetdata/clocks/README.md index ed45e7ebb8..33b0f0e85c 100644 --- a/libnetdata/clocks/README.md +++ b/libnetdata/clocks/README.md @@ -6,3 +6,5 @@ learn_status: "Published" learn_topic_type: "References" learn_rel_path: "Developers/libnetdata" --> + +# Clocks
\ No newline at end of file diff --git a/libnetdata/locks/README.md b/libnetdata/locks/README.md index ccf9684e64..5560832b7a 100644 --- a/libnetdata/locks/README.md +++ b/libnetdata/locks/README.md @@ -7,6 +7,8 @@ learn_topic_type: "Tasks" learn_rel_path: "Developers/libnetdata" --> +# Locks + ## How to trace netdata locks To enable tracing rwlocks in netdata, compile netdata by setting `CFLAGS="-DNETDATA_TRACE_RWLOCKS=1"`, like this: diff --git a/libnetdata/parser/README.md b/libnetdata/parser/README.md index 7fcc176aed..136c23c692 100644 --- a/libnetdata/parser/README.md +++ b/libnetdata/parser/README.md @@ -7,7 +7,9 @@ learn_topic_type: "References" learn_rel_path: "Developers/Database" --> -#### Introduction +# Parser + +## Introduction Generic parser that is used to register keywords and a corresponding function that will be executed when that keyword is encountered in the command stream (either from plugins or via streaming) |