Influxdata
/
docs-v2
mirror of https://github.com/influxdata/docs-v2.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

fix(telegraf): replace grok tool link, typo, and style (#4757) (#4793)

pull/4794/head^2
Jason Stirnaman 2023-03-13 12:34:42 -05:00 committed by GitHub
parent f346a1c13d
commit 8522def052
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
17 changed files with 119 additions and 136 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
content/telegraf/v1.10/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.11/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.12/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.13/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.14/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats (parsers) parent: Input data formats (parsers)
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.15/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.16/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.17/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.18/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.19/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.20/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.21/data_formats/input/grok.md
View File

@ -9,10 +9,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -66,12 +66,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -169,8 +168,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.22/data_formats/input/grok.md
View File

@ -9,10 +9,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -66,12 +66,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -169,8 +168,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.23/data_formats/input/grok.md
View File

@ -9,10 +9,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -66,12 +66,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -169,8 +168,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.24/data_formats/input/grok.md
View File

@ -9,10 +9,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -66,12 +66,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -169,8 +168,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.25/data_formats/input/grok.md
View File

@ -9,10 +9,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -66,12 +66,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -169,8 +168,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file:

15
content/telegraf/v1.9/data_formats/input/grok.md
View File

@ -8,10 +8,10 @@ menu:
parent: Input data formats parent: Input data formats
--- ---
The grok data format parses line delimited data using a regular expression-like The grok data format parses line-delimited data using a regular expression-like
language. language.
If you need to become familiar with grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics) For an introduction to grok patterns, see [Grok Basics](https://www.elastic.co/guide/en/logstash/current/plugins-filters-grok.html#_grok_basics)
in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok" in the Logstash documentation. The grok parser uses a slightly modified version of logstash "grok"
patterns, using the format: patterns, using the format:
@ -65,12 +65,11 @@ See https://golang.org/pkg/time/#Parse for more details.
Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go), Telegraf has many of its own [built-in patterns](https://github.com/influxdata/telegraf/blob/master/plugins/parsers/grok/influx_patterns.go),
as well as support for most of as well as support for most of
[logstash's builtin patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns. [Logstash's core patterns](https://github.com/logstash-plugins/logstash-patterns-core/blob/main/patterns/ecs-v1/grok-patterns).
_Golang regular expressions do not support lookahead or lookbehind. _Golang regular expressions do not support lookahead or lookbehind.
logstash patterns that depend on these are not supported._ Logstash patterns that depend on these are not supported._
If you need help building patterns to match your logs, the If you need help building patterns to match your logs, [Grok Constructor](https://grokconstructor.appspot.com/) might be helpful.
[Grok Debugger application](https://grokdebug.herokuapp.com) might be helpful.
## Configuration ## Configuration
@ -168,8 +167,8 @@ grok will offset the timestamp accordingly.
When saving patterns to the configuration file, keep in mind the different TOML When saving patterns to the configuration file, keep in mind the different TOML
[string](https://github.com/toml-lang/toml#string) types and the escaping [string](https://github.com/toml-lang/toml#string) types and the escaping
rules for each. These escaping rules must be applied in addition to the rules for each. These escaping rules must be applied in addition to the
escaping required by the grok syntax. Using the Multi-line line literal escaping required by the grok syntax. Using the TOML multi-line literal
syntax with `'''` may be useful. syntax (`'''`) may be useful.
The following config examples will parse this input file: The following config examples will parse this input file: