-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Typo fix * [4.1] Adds minimal sdata-parser docs * Minor fixes
- Loading branch information
Showing
3 changed files
with
26 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,24 @@ | ||
--- | ||
title: "Structured data (SDATA) parser" | ||
weight: 1850 | ||
--- | ||
<!-- This file is under the copyright of Axoflow, and licensed under Apache License 2.0, except for using the Axoflow and AxoSyslog trademarks. --> | ||
|
||
Available in {{% param "product.abbrev" %}} 4.1 and later. | ||
|
||
The `sdata-parser()` allows you to parse an RFC5424-style structured data string. You can use it to parse this relatively complex format separately, for example, to process malformatted messages. You can use the optional `prefix` option to add a specific string before the names of the parsed name-value pairs. | ||
|
||
## Declaration | ||
|
||
```shell | ||
parser parser_name { | ||
sdata-parser( | ||
template("<string-or-template-to-parse>") | ||
prefix("<prefix-for-parsed-name-value-pairs>") | ||
); | ||
}; | ||
``` | ||
|
||
{{% include-headless "chunk/option-parser-prefix.md" %}} | ||
|
||
{{% include-headless "chunk/option-parser-template.md" %}} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters