Skip to content

Commit 4871322

Browse files
remove $ from select commands in filters
Signed-off-by: Alexa Kreizinger <[email protected]>
1 parent 3bb85a2 commit 4871322

File tree

12 files changed

+17
-17
lines changed

12 files changed

+17
-17
lines changed

pipeline/filters/aws-metadata.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ If you run Fluent Bit in a container, you might need to use instance metadata v1
2929
Run Fluent Bit from the command line:
3030

3131
```shell
32-
$ ./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
32+
./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
3333
```
3434

3535
You should see results like this:

pipeline/filters/grep.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ When using the command line, pay close attention to quote the regular expression
4242
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`:
4343

4444
```shell
45-
$ ./fluent-bit -i tail -p 'path=lines.txt' -F grep -p 'regex=log aa' -m '*' -o stdout
45+
./fluent-bit -i tail -p 'path=lines.txt' -F grep -p 'regex=log aa' -m '*' -o stdout
4646
```
4747

4848
### Configuration file

pipeline/filters/lua.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ To test the Lua filter, you can run the plugin from the command line or through
3131
From the command line you can use the following options:
3232

3333
```shell
34-
$ ./fluent-bit -i dummy -F lua -p script=test.lua -p call=cb_print -m '*' -o null
34+
./fluent-bit -i dummy -F lua -p script=test.lua -p call=cb_print -m '*' -o null
3535
```
3636

3737
### Configuration file

pipeline/filters/modify.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ which outputs data similar to the following:
9595
Using the command line mode requires quotes parse the wildcard properly. The use of a configuration file is recommended.
9696

9797
```shell
98-
$ ./fluent-bit -i mem \
98+
./fluent-bit -i mem \
9999
-p 'tag=mem.local' \
100100
-F modify \
101101
-p 'Add=Service1 SOMEVALUE' \

pipeline/filters/multiline-stacktrace.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ one more line, no multiline
246246
Running Fluent Bit with the given configuration file:
247247

248248
```shell
249-
$ ./fluent-bit -c fluent-bit.conf
249+
./fluent-bit -c fluent-bit.conf
250250
```
251251

252252
Should return something like the following:

pipeline/filters/nest.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ wildcard rule to the keys and nests the keys matching `Mem.*` under the new key
9191
`NEST`.
9292

9393
```shell
94-
$ ./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
94+
./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
9595
```
9696

9797
### Nest configuration file

pipeline/filters/nightfall.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -81,10 +81,10 @@ After you configure the filter, you can use it from the command line by running
8181

8282
```shell
8383
# For YAML configuration.
84-
$ ./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.yaml
84+
./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.yaml
8585

8686
# For classic configuration.
87-
$ ./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
87+
./fluent-bit -c /PATH_TO_CONF_FILE/fluent-bit.conf
8888
```
8989

9090
Replace _`PATH_TO_CONF_FILE`_ with the path for where your filter configuration file

pipeline/filters/record-modifier.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ pipeline:
7676
You can run the filter from command line:
7777

7878
```shell
79-
$ ./fluent-bit -i mem -o stdout -F record_modifier -p 'Record=hostname ${HOSTNAME}' -p 'Record=product Awesome_Tool' -m '*'
79+
./fluent-bit -i mem -o stdout -F record_modifier -p 'Record=hostname ${HOSTNAME}' -p 'Record=product Awesome_Tool' -m '*'
8080
```
8181

8282
The output looks something like:
@@ -137,7 +137,7 @@ pipeline:
137137
You can also run the filter from command line.
138138

139139
```shell
140-
$ ./fluent-bit -i mem -o stdout -F record_modifier -p 'Remove_key=Swap.total' -p 'Remove_key=Swap.free' -p 'Remove_key=Swap.used' -m '*'
140+
./fluent-bit -i mem -o stdout -F record_modifier -p 'Remove_key=Swap.total' -p 'Remove_key=Swap.free' -p 'Remove_key=Swap.used' -m '*'
141141
```
142142

143143
The output looks something like:
@@ -198,7 +198,7 @@ pipeline:
198198
You can also run the filter from command line:
199199

200200
```shell
201-
$ ./fluent-bit -i mem -o stdout -F record_modifier -p 'Allowlist_key=Mem.total' -p 'Allowlist_key=Mem.free' -p 'Allowlist_key=Mem.used' -m '*'
201+
./fluent-bit -i mem -o stdout -F record_modifier -p 'Allowlist_key=Mem.total' -p 'Allowlist_key=Mem.free' -p 'Allowlist_key=Mem.used' -m '*'
202202
```
203203

204204
The output looks something like:

pipeline/filters/rewrite-tag.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ The `rewrite_tag` filter emits new records that go through the beginning of the
209209
Using the previously provided configuration, when you query the metrics exposed in the HTTP interface:
210210

211211
```shell
212-
$ ./curl http://127.0.0.1:2020/api/v1/metrics/ | jq
212+
./curl http://127.0.0.1:2020/api/v1/metrics/ | jq
213213
```
214214

215215
You will see metrics output similar to the following:

pipeline/filters/tensorflow.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ To create a Tensorflow Lite shared library:
2929
1. Run the following command to create the shared library:
3030

3131
```shell
32-
$ ./bazel build -c opt //tensorflow/lite/c:tensorflowlite_c # see https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/c
32+
./bazel build -c opt //tensorflow/lite/c:tensorflowlite_c # see https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/c
3333
```
3434

3535
The script creates the shared library
@@ -41,7 +41,7 @@ To create a Tensorflow Lite shared library:
4141
The Tensorflow filter plugin is disabled by default. You must build Fluent Bit with the Tensorflow plugin enabled. In addition, it requires access to Tensorflow Lite header files to compile. Therefore, you must pass the address of the Tensorflow source code on your machine to the [build script](https://github.com/fluent/fluent-bit#build-from-scratch):
4242

4343
```shell
44-
$ ./cmake -DFLB_FILTER_TENSORFLOW=On -DTensorflow_DIR=<AddressOfTensorflowSourceCode> ...
44+
./cmake -DFLB_FILTER_TENSORFLOW=On -DTensorflow_DIR=<AddressOfTensorflowSourceCode> ...
4545
```
4646

4747
### Command line
@@ -51,7 +51,7 @@ If the Tensorflow plugin initializes correctly, it reports successful creation o
5151
The command:
5252

5353
```shell
54-
$ ./fluent-bit -i mqtt -p 'tag=mqtt.data' -F tensorflow -m '*' -p 'input_field=image' -p 'model_file=/home/user/model.tflite' -p
54+
./fluent-bit -i mqtt -p 'tag=mqtt.data' -F tensorflow -m '*' -p 'input_field=image' -p 'model_file=/home/user/model.tflite' -p
5555
```
5656

5757
produces an output like:

0 commit comments

Comments
 (0)