CL-Softwares
/
telegraf
8
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs: Resolve table column count lint issues (#14637)

This commit is contained in:
Joshua Powers 2024-01-29 11:25:03 -07:00 committed by GitHub
parent f678b8c6c2
commit 8a50d75127
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 29 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

56
plugins/aggregators/derivative/README.md
View File

@ -140,21 +140,21 @@ To avoid thinking about border values, we consider periods to be inclusive at
the start but exclusive in the end. Using `period = "10s"` and `max_roll_over = the start but exclusive in the end. Using `period = "10s"` and `max_roll_over =
0` we would get the following aggregates: 0` we would get the following aggregates:
| timestamp | value | aggregate | explanation | | timestamp | value | aggregate | explanation |
|-----------|-------|-----------|--------------| |-----------|-------|-----------|--------------|
| 0 | 0.0 | | 0 | 0.0 | | |
| 2 | 2.0 | | 2 | 2.0 | | |
| 4 | 4.0 | | 4 | 4.0 | | |
| 6 | 6.0 | | 6 | 6.0 | | |
| 8 | 8.0 | | 8 | 8.0 | | |
||| 1.0 | (8.0 - 0.0) / (8 - 0) | ||| 1.0 | (8.0 - 0.0) / (8 - 0) |
| 10 | 10.0 | | 10 | 10.0 | | |
| 12 | 8.0 | | 12 | 8.0 | | |
| 14 | 6.0 | | 14 | 6.0 | | |
| 16 | 4.0 | | 16 | 4.0 | | |
| 18 | 2.0 | | 18 | 2.0 | | |
||| -1.0 | (2.0 - 10.0) / (18 - 10) ||| -1.0 | (2.0 - 10.0) / (18 - 10) |
| 20 | 0.0 | | 20 | 0.0 | | |
If we now decrease the period with `period = 2s`, no derivative could be If we now decrease the period with `period = 2s`, no derivative could be
calculated since there would only one measurement for each period. The calculated since there would only one measurement for each period. The
@ -163,8 +163,8 @@ skipping.`. This changes, if we use `max_roll_over = 1`, since now end
measurements of a period are taking as start for the next period. measurements of a period are taking as start for the next period.
| timestamp | value | aggregate | explanation | | timestamp | value | aggregate | explanation |
|-----------|-------|-----------|--------------| |-----------|-------|-----------|-------------|
| 0 | 0.0 | | 0 | 0.0 | | |
| 2 | 2.0 | 1.0 | (2.0 - 0.0) / (2 - 0) | | 2 | 2.0 | 1.0 | (2.0 - 0.0) / (2 - 0) |
| 4 | 4.0 | 1.0 | (4.0 - 2.0) / (4 - 2) | | 4 | 4.0 | 1.0 | (4.0 - 2.0) / (4 - 2) |
| 6 | 6.0 | 1.0 | (6.0 - 4.0) / (6 - 4) | | 6 | 6.0 | 1.0 | (6.0 - 4.0) / (6 - 4) |
@ -185,19 +185,19 @@ for `period = "7s"`.
| timestamp | value | `max_roll_over = 0` | explanation | `max_roll_over = 1` | explanation | | timestamp | value | `max_roll_over = 0` | explanation | `max_roll_over = 1` | explanation |
|-----------|-------|---------------------|-------------|---------------------|-------------| |-----------|-------|---------------------|-------------|---------------------|-------------|
| 0 | 0.0 | | 0 | 0.0 | | | | |
| 2 | 2.0 | | 2 | 2.0 | | | | |
| 4 | 4.0 | | 4 | 4.0 | | | | |
| 6 | 6.0 | | 6 | 6.0 | | | | |
| 7 | | 0.8571... | (6-0) / (7-0) | 0.8571... | (6-0) / (7-0) | 7 | | 0.8571... | (6-0) / (7-0) | 0.8571... | (6-0) / (7-0) |
| 8 | 8.0 | | 8 | 8.0 | | | | |
| 10 | 10.0 | | 10 | 10.0 | | | | |
| 12 | 8.0 | | 12 | 8.0 | | | | |
| 14 | 8.0 | 0.0 | (8-8) / (14-7) | 0.2857... | (8-6) / (14-7) | 14 | 8.0 | 0.0 | (8-8) / (14-7) | 0.2857... | (8-6) / (14-7) |
| 16 | 4.0 | | 16 | 4.0 | | | | |
| 18 | 2.0 | | 18 | 2.0 | | | | |
| 20 | 0.0 | | 20 | 0.0 | | | | |
||| -1.0 | -1.0 | ||| -1.0 | -1.0 | | |
The difference stems from the change of the value between periods, e.g. from 6.0 The difference stems from the change of the value between periods, e.g. from 6.0
to 8.0 between first and second period. Those changes are omitted with to 8.0 between first and second period. Those changes are omitted with

2
plugins/inputs/http_response/README.md
View File

@ -136,7 +136,7 @@ This tag is used to expose network and plugin errors. HTTP errors are considered
a successful connection. a successful connection.
|Tag value |Corresponding field value|Description| |Tag value |Corresponding field value|Description|
-------------------------------|-------------------------|-----------| |------------------------------|-------------------------|-----------|
|success | 0 |The HTTP request completed, even if the HTTP code represents an error| |success | 0 |The HTTP request completed, even if the HTTP code represents an error|
|response_string_mismatch | 1 |The option `response_string_match` was used, and the body of the response didn't match the regex. HTTP errors with content in their body (like 4xx, 5xx) will trigger this error| |response_string_mismatch | 1 |The option `response_string_match` was used, and the body of the response didn't match the regex. HTTP errors with content in their body (like 4xx, 5xx) will trigger this error|
|body_read_error | 2 |The option `response_string_match` was used, but the plugin wasn't able to read the body of the response. Responses with empty bodies (like 3xx, HEAD, etc) will trigger this error. Or the option `response_body_field` was used and the content of the response body was not a valid utf-8. Or the size of the body of the response exceeded the `response_body_max_size` | |body_read_error | 2 |The option `response_string_match` was used, but the plugin wasn't able to read the body of the response. Responses with empty bodies (like 3xx, HEAD, etc) will trigger this error. Or the option `response_body_field` was used and the content of the response body was not a valid utf-8. Or the size of the body of the response exceeded the `response_body_max_size` |