The CreateParserInputV2
is
the input for creating a parser. It includes various settings.
Table: CreateParserInputV2
Parameter | Type | Required | Default | Stability | Description |
---|---|---|---|---|---|
Some arguments may be required, as indicated in the Required column. For some fields, this column indicates that a result will always be returned for this column. | |||||
Table last updated: Mar 28, 2025 | |||||
allowOverwritingExistingParser | boolean | false | Long-Term | Allows saving a parser with a name that is already in use, by overwriting the parser that previously had the name. | |
fieldsToTag | [string] | yes | Long-Term | Fields that are used as tags. | |
fieldsToBeRemovedBeforeParsing | [string] | yes | Long-Term | A list of fields that will be removed from the event before it's parsed. These fields will not be included when calculating usage. | |
languageVersion | multiple | {name: ”legacy“} | Long-Term | A specific language version. The multiple datatype consists of LanguageVersionInputType = {name: 'legacy'} . See LanguageVersionInputType . | |
name | string | yes | Long-Term | The name to use for the parser. | |
repositoryName | repoOrViewName | yes | Long-Term | The repository where the parser is located. repoOrViewName is a scalar. | |
script | string | yes | Long-Term | The parser script that is executed for every incoming event. | |
testCases | [ParserTestCaseInput ] | yes | Long-Term | Test cases that can be used to help verify that the parser works as expected. See ParserTestCaseInput . |