Merge pull request #1885 from fluent/alexakreizinger/sc-141445/fix-formatting-errors-from-fluent-bit-docs

Author: alexakreizinger

administration/monitoring.md

@@ -71,10 +71,10 @@ Start Fluent bit with the corresponding configuration chosen above:
 
 ```shell
 # For YAML configuration.
-$ ./bin/fluent-bit --config fluent-bit.yaml
+./bin/fluent-bit --config fluent-bit.yaml
 
 # For classic configuration.
-$ ./bin/fluent-bit --config fluent-bit.conf
+./bin/fluent-bit --config fluent-bit.conf
 ```
 
 Fluent Bit starts and generates output in your terminal:
@@ -282,7 +282,7 @@ The command prints a similar output like this:
 Query internal metrics in JSON format with the following command:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/metrics | jq
+curl -s http://127.0.0.1:2020/api/v1/metrics | jq
 ```
 
 The command prints a similar output like this:
@@ -312,7 +312,7 @@ The command prints a similar output like this:
 Query internal metrics in Prometheus Text 0.0.4 format:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/metrics/prometheus
+curl -s http://127.0.0.1:2020/api/v1/metrics/prometheus
 ```
 
 This command returns the same metrics in Prometheus format instead of JSON:
@@ -506,7 +506,7 @@ pipeline:
 Use the following command to call the health endpoint:
 
 ```shell
-$ curl -s http://127.0.0.1:2020/api/v1/health
+curl -s http://127.0.0.1:2020/api/v1/health
 ```
 
 With the example configuration, the health status is determined by the following equation:

development/msgpack-format.md

@@ -16,7 +16,7 @@ This section provides an overview of the specific types used by Fluent Bit withi
 Set up Fluent Bit to send in `msgpack` format to a specific port.
 
 ```bash
-$ docker run --rm -it --network=host fluent/fluent-bit /fluent-bit/bin/fluent-bit -i cpu -o tcp://127.0.0.1:5170 -p format=msgpack -v
+docker run --rm -it --network=host fluent/fluent-bit /fluent-bit/bin/fluent-bit -i cpu -o tcp://127.0.0.1:5170 -p format=msgpack -v
 
 ```
 

development/wasm-filter-plugins.md

@@ -35,9 +35,9 @@ Currently, Fluent Bit supports the following Wasm tool chains:
 As described in the general options in the [source installation](../installation/sources/build-and-install.md) guide, Wasm support is enabled by default. Compile Fluent Bit with Wasm support, for example:
 
 ```text
-$ cd build/
-$ cmake .. [-DFLB_WAMRC=On]
-$ make
+cd build/
+cmake .. [-DFLB_WAMRC=On]
+make
 ```
 
 To support AOT-compiled Wasm execution as filter plugins, build Fluent Bit with `-DFLB_WAMRC=On`.
@@ -65,7 +65,7 @@ The Fluent Bit Wasm filter assumes C ABI, also known as `wasm32-unknown-unknown`
 TinyGo and WASI SDK support Wasm target by default. When using Rust's `wasm32-unknown-unknown` target, you must install `wasm32-unknown-unknown` by using [rustup](https://rustup.rs/). Then, install the target components as follows:
 
 ```text
-$ rustup target add wasm32-unknown-unknown
+rustup target add wasm32-unknown-unknown
 ```
 
 ### Requirements of Wasm programs
@@ -228,13 +228,13 @@ To optimize Wasm program execution, there is the option of using `flb-wamrc`. Th
 This tool will be built when the `-DFLB_WAMRC=On` CMake option is specified and LLVM infrastructure is installed on the building box.
 
 ```shell
-$ flb-wamrc -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
+flb-wamrc -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
 ```
 
 For further optimizations to the specific CPU, such as Cortex-A57 series:
 
 ```text
-$ flb-wamrc --size-level=3 --target=aarch64v8 --cpu=cortex-a57 -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
+flb-wamrc --size-level=3 --target=aarch64v8 --cpu=cortex-a57 -o /path/to/built_wasm.aot /path/to/built_wasm.wasm
 ```
 
 Then, when AOT (Ahead Of Time) compiling has succeeded:

development/wasm-input-plugins.md

@@ -25,9 +25,9 @@ Fluent Bit supports the following Wasm toolchains:
 Compile Fluent Bit with Wasm support. For example:
 
 ```text
-$ cd build/
-$ cmake ..
-$ make
+cd build/
+cmake ..
+make
 ```
 
 Once compiled, you can see new plugins that handle `wasm`. For example:
@@ -53,7 +53,7 @@ Wasm input in Fluent Bit assumes WASI ABI, also known as `wasm32-wasi` on Rust t
 TinyGo and WASI SDK support Wasm target by default. When using Rust's `wasm32-wasi` target, you must install `wasm32-wasi` by using [rustup](https://rustup.rs/). Then, install the target components as:
 
 ```text
-$ rustup target add wasm32-wasi
+rustup target add wasm32-wasi
 ```
 
 ### Requirements of Wasm/WASI programs

pipeline/filters/aws-metadata.md

@@ -29,7 +29,7 @@ If you run Fluent Bit in a container, you might need to use instance metadata v1
 Run Fluent Bit from the command line:
 
 ```shell
-$ ./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
+./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
 ```
 
 You should see results like this:

pipeline/filters/grep.md

@@ -42,7 +42,7 @@ When using the command line, pay close attention to quote the regular expression
 The following command loads the [tail](../../pipeline/inputs/tail) plugin and reads the content of `lines.txt`. Then the `grep` filter applies a regular expression rule over the `log` field created by the `tail` plugin and only passes records with a field value starting with `aa`:
 
 ```shell
-$ ./fluent-bit -i tail -p 'path=lines.txt' -F grep -p 'regex=log aa' -m '*' -o stdout
+./fluent-bit -i tail -p 'path=lines.txt' -F grep -p 'regex=log aa' -m '*' -o stdout
 ```
 
 ### Configuration file

pipeline/filters/lua.md

@@ -31,7 +31,7 @@ To test the Lua filter, you can run the plugin from the command line or through
 From the command line you can use the following options:
 
 ```shell
-$ ./fluent-bit -i dummy -F lua -p script=test.lua -p call=cb_print -m '*' -o null
+./fluent-bit -i dummy -F lua -p script=test.lua -p call=cb_print -m '*' -o null
 ```
 
 ### Configuration file

pipeline/filters/modify.md

@@ -95,7 +95,7 @@ which outputs data similar to the following:
 Using the command line mode requires quotes parse the wildcard properly. The use of a configuration file is recommended.
 
 ```shell
-$ ./fluent-bit -i mem \
+./fluent-bit -i mem \
               -p 'tag=mem.local' \
               -F modify \
               -p 'Add=Service1 SOMEVALUE' \

pipeline/filters/multiline-stacktrace.md

@@ -246,7 +246,7 @@ one more line, no multiline
 Running Fluent Bit with the given configuration file:
 
 ```shell
-$ ./fluent-bit -c fluent-bit.conf
+./fluent-bit -c fluent-bit.conf
 ```
 
 Should return something like the following:

pipeline/filters/nest.md

@@ -91,7 +91,7 @@ wildcard rule to the keys and nests the keys matching `Mem.*` under the new key
 `NEST`.
 
 ```shell
-$ ./fluent-bit -i mem -p 'tag=mem.local' -F nest -p 'Operation=nest' -p 'Wildcard=Mem.*' -p 'Nest_under=Memstats' -p 'Remove_prefix=Mem.' -m '*' -o stdout
+./fluent-bit -i mem -p 'tag=mem.local' -F nest -p 'Operation=nest' -p 'Wildcard=Mem.*' -p 'Nest_under=Memstats' -p 'Remove_prefix=Mem.' -m '*' -o stdout
 ```
 
 ### Nest configuration file