API Stability Deprecated

The removeParser() GraphQL mutation may be used to remove a parser. This is deprecated, and will be removed in version 1.142, in favor of newer version that's more consistent with the rest of the GraphQL API. Use instead deleteParser().

For more information on parsers, see the Parsing Data documentation page.

Syntax

Below is the syntax for the removeParser() mutation field:

graphql
removeParser(
      input: RemoveParserInput!
   ): RemoveParserMutation!

Below is an example of how this mutation field might be used:

Show:
graphql
mutation {
  removeParser(input: 
    { repositoryName: "humio",
      id: "123abc"
    }
  )
  { parser { name } }
}
Example Responses
Show:
json
{
  "data": {
    "removeParser": {
      "result": true,
      "name": "my-parser"
    }
  }
}

Given Datatypes

For RemoveParserInput, there are a couple of parameters. Below is a list of them along with a description of each:

Table: RemoveParserInput

ParameterTypeRequiredDefaultStabilityDescription
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: Sep 19, 2024
idstringyes DeprecatedThe unique identifier of the parser.
repositoryNamestringyes DeprecatedThe name of the repository to which the parser is associated.

Returned Datatypes

The returned datatype RemoveParserMutation has one parameter, which in turn has many sub-parameters. Below is a link to another table with the sub-parameters.

Table: RemoveParserMutation

ParameterTypeRequiredDefaultStabilityDescription
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: Oct 3, 2024
parserParseryes Long-TermThe parser to remove from the mutation. See Parser.