Skip to content

Commit 886e47a

Browse files
cnorris-cscnorris-cs
authored
Merge pull request fluent#1311 from stratusjerry/typo
fix typos
2 parents f287567 + 326015d commit 886e47a

File tree

7 files changed

+18
-18
lines changed

7 files changed

+18
-18
lines changed

‎administration/backpressure.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ The setting behaves similarly to the above scenario with `Mem_Buf_Limit` when th
4444

4545
When (default) `storage.pause_on_chunks_overlimit` is disabled, the input will not pause when the memory limit is reached. Instead, it will switch to only buffering logs in the filesystem. The disk spaced used for filesystem buffering can be limited with `storage.total_limit_size`.
4646

47-
Please consule the [Buffering & Storage](buffering-and-storage.md) docs for more information.
47+
See the [Buffering & Storage](buffering-and-storage.md) docs for more information.
4848

4949
## About pause and resume Callbacks
5050

‎administration/monitoring.md

+10-10
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ $ curl -s http://127.0.0.1:2020 | jq
7878
}
7979
```
8080

81-
Note that we are sending the _curl_ command output to the _jq_ program which helps to make the JSON data easy to read from the terminal. Fluent Bit don't aim to do JSON pretty-printing.
81+
Note that we are sending the _curl_ command output to the _jq_ program which helps to make the JSON data easy to read from the terminal. Fluent Bit doesn't aim to do JSON pretty-printing.
8282

8383
### REST API Interface
8484

@@ -110,15 +110,15 @@ The following definitions are key to understand:
110110
|----------------------------------------|-------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|---------|
111111
| fluentbit_input_bytes_total | name: the name or alias for the input instance | The number of bytes of log records that this input instance has successfully ingested | counter | bytes |
112112
| fluentbit_input_records_total | name: the name or alias for the input instance | The number of log records this input has successfully ingested | counter | records |
113-
| fluentbit_output_dropped_records_total | name: the name or alias for the output instance | The number of log records that have been dropped by the output. This means they met an unrecoverable error or retries expired for their chunk. | counter | records |
114-
| fluentbit_output_errors_total | name: the name or alias for the output instance | The number of chunks that have faced an error (either unrecoverable or retriable). This is the number of times a chunk has failed, and does not correspond with the number of error messages you see in the Fluent Bit log output. | counter | chunks |
115-
| fluentbit_output_proc_bytes_total | name: the name or alias for the output instance | The number of bytes of log records that this output instance has *successfully* sent. This is the total byte size of all unique chunks sent by this output. If a record is not sent due to some error, then it will not count towards this metric. | counter | bytes |
116-
| fluentbit_output_proc_records_total | name: the name or alias for the output instance | The number of log records that this output instance has *successfully* sent. This is the total record count of all unique chunks sent by this output. If a record is not successfully sent, it does not count towards this metric. | counter | records |
117-
| fluentbit_output_retried_records_total | name: the name or alias for the output instance | The number of log records that experienced a retry. Note that this is calculated at the chunk level, the count increased when an entire chunk is marked for retry. An output plugin may or may not perform multiple actions that generate many error messages when uploading a single chunk. | counter | records |
118-
| fluentbit_output_retries_failed_total | name: the name or alias for the output instance | The number of times that retries expired for a chunk. Each plugin configures a Retry_Limit which applies to chunks. Once the Retry_Limit has been reached for a chunk it is discarded and this metric is incremented. | counter | chunks |
119-
| fluentbit_output_retries_total | name: the name or alias for the output instance | The number of times this output instance requested a retry for a chunk. | counter | chunks |
120-
| fluentbit_uptime | | The number of seconds that Fluent Bit has been running. | counter | seconds |
121-
| process_start_time_seconds | | The Unix Epoch time stamp for when Fluent Bit started.. | guage | seconds |
113+
| fluentbit_output_dropped_records_total | name: the name or alias for the output instance | The number of log records that have been dropped by the output. This means they met an unrecoverable error or retries expired for their chunk. | counter | records |
114+
| fluentbit_output_errors_total | name: the name or alias for the output instance | The number of chunks that have faced an error (either unrecoverable or retriable). This is the number of times a chunk has failed, and does not correspond with the number of error messages you see in the Fluent Bit log output. | counter | chunks |
115+
| fluentbit_output_proc_bytes_total | name: the name or alias for the output instance | The number of bytes of log records that this output instance has *successfully* sent. This is the total byte size of all unique chunks sent by this output. If a record is not sent due to some error, then it will not count towards this metric. | counter | bytes |
116+
| fluentbit_output_proc_records_total | name: the name or alias for the output instance | The number of log records that this output instance has *successfully* sent. This is the total record count of all unique chunks sent by this output. If a record is not successfully sent, it does not count towards this metric. | counter | records |
117+
| fluentbit_output_retried_records_total | name: the name or alias for the output instance | The number of log records that experienced a retry. Note that this is calculated at the chunk level, the count increased when an entire chunk is marked for retry. An output plugin may or may not perform multiple actions that generate many error messages when uploading a single chunk. | counter | records |
118+
| fluentbit_output_retries_failed_total | name: the name or alias for the output instance | The number of times that retries expired for a chunk. Each plugin configures a Retry_Limit which applies to chunks. Once the Retry_Limit has been reached for a chunk it is discarded and this metric is incremented. | counter | chunks |
119+
| fluentbit_output_retries_total | name: the name or alias for the output instance | The number of times this output instance requested a retry for a chunk. | counter | chunks |
120+
| fluentbit_uptime | | The number of seconds that Fluent Bit has been running. | counter | seconds |
121+
| process_start_time_seconds | | The Unix Epoch time stamp for when Fluent Bit started. | gauge | seconds |
122122

123123

124124
The following are detailed descriptions for the metrics outputted in JSON format by `/api/v1/storage`.

‎development/wasm-filter-plugins.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -170,8 +170,8 @@ These examples can be applied in our demo and can serve as an ideal starting poi
170170
### Optimize execution of WASM programs
171171

172172
To optimize WASM program execution, there is the option of using `flb-wamrc`.
173-
`flb-wamrc` will reduce runtime footprint and to be best perforemance for filtering operations.
174-
This tool will be built when `-DFLB_WAMRC=On` cmake option is specififed and llvm infrastructure is installed on the building box.
173+
`flb-wamrc` will reduce runtime footprint and to be best performance for filtering operations.
174+
This tool will be built when `-DFLB_WAMRC=On` cmake option is specified and llvm infrastructure is installed on the building box.
175175

176176
```shell
177177
$ flb-wamrc -o /path/to/built_wasm.aot /path/to/built_wasm.wasm

‎installation/linux/README.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
# Linux Packages
22

3-
The most secure option is to create the repositories acccording to the instructions for your specific OS.
3+
The most secure option is to create the repositories according to the instructions for your specific OS.
44

55
A simple installation script is provided to be used for most Linux targets.
66
This will by default install the most recent version released.

‎pipeline/outputs/splunk.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ This will create a payload that looks like:
125125
}
126126
```
127127

128-
For more information on the Splunk HEC payload format and all event meatadata Splunk accepts, see here: [http://docs.splunk.com/Documentation/Splunk/latest/Data/AboutHEC](http://docs.splunk.com/Documentation/Splunk/latest/Data/AboutHEC)
128+
For more information on the Splunk HEC payload format and all event metadata Splunk accepts, see here: [http://docs.splunk.com/Documentation/Splunk/latest/Data/AboutHEC](http://docs.splunk.com/Documentation/Splunk/latest/Data/AboutHEC)
129129

130130
### Sending Raw Events
131131

‎pipeline/outputs/stackdriver.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -189,7 +189,7 @@ Do following check:
189189

190190
> Github reference: [#7552](https://github.com/fluent/fluent-bit/issues/7552)
191191
192-
When the number of Workers is greater than 1, Fluent Bit may interimittently crash.
192+
When the number of Workers is greater than 1, Fluent Bit may intermittently crash.
193193

194194
## Other implementations
195195

‎pipeline/outputs/websocket.md

+2-2
Original file line numberDiff line numberDiff line change
@@ -6,8 +6,8 @@ The **websocket** output plugin allows to flush your records into a WebSocket en
66

77
| Key | Description | default |
88
| :--- | :--- | :--- |
9-
| Host | IP address or hostname of the target WebScoket Server | 127.0.0.1 |
10-
| Port | TCP port of the target WebScoket Server | 80 |
9+
| Host | IP address or hostname of the target WebSocket Server | 127.0.0.1 |
10+
| Port | TCP port of the target WebSocket Server | 80 |
1111
| URI | Specify an optional HTTP URI for the target websocket server, e.g: /something | / |
1212
| Header | Add a HTTP header key/value pair. Multiple headers can be set. | |
1313
| Format | Specify the data format to be used in the HTTP request body, by default it uses _msgpack_. Other supported formats are _json_, _json\_stream_ and _json\_lines_ and _gelf_. | msgpack |

0 commit comments

Comments
 (0)