The deleteEventForwardingRule() GraphQL mutation may be used to delete an event forwarding rule on a repository in LogScale.

To create an event forwarding rule, you can use the createEventForwardingRule() mutation. To update an event forwarding rule, you can use the updateEventForwardingRule() mutation.

Hide Query Example

Show Event Forwarding Rules Query

For more information on event forwarding rules, see the Event Forwarding Rules documentation page. You may also want to look at the Event Forwarding and the Events page for related information.

API Stability Long-Term

Syntax

graphql
deleteEventForwardingRule(
     input: DeleteEventForwardingRule!
   ): boolean

There are no special return datatypes for this mutation field.

Example

Raw
graphql
mutation {
  deleteEventForwardingRule( input: 
       { viewName: "humio", 
         id: "abc123"}
  )
}
Mac OS or Linux (curl)
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}"
}
EOF
Mac OS or Linux (curl) One-line
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql \
    -H "Authorization: Bearer $TOKEN" \
    -H "Content-Type: application/json" \
    -d @- << EOF
{"query" : "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}"
}
EOF
Windows Cmd and curl
shell
curl -v -X POST $YOUR_LOGSCALE_URL/graphql ^
    -H "Authorization: Bearer $TOKEN" ^
    -H "Content-Type: application/json" ^
    -d @'{"query" : "mutation { ^
  deleteEventForwardingRule( input:  ^
       { viewName: \"humio\",  ^
         id: \"abc123\"} ^
  ) ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}"
}'
    "$YOUR_LOGSCALE_URL/graphql"
Perl
perl
#!/usr/bin/perl

use HTTP::Request;
use LWP;

my $TOKEN = "TOKEN";

my $uri = '$YOUR_LOGSCALE_URL/graphql';

my $query = "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}";
$query =~ s/\n/ /g;
my $json = sprintf('{"query" : "%s"}',$query);
my $req = HTTP::Request->new("POST", $uri );

$req->header("Authorization" => "Bearer $TOKEN");
$req->header("Content-Type" => "application/json");

$req->content( $json );

my $lwp = LWP::UserAgent->new;

my $result = $lwp->request( $req );

print $result->{"_content"},"\n";
Python
python
#! /usr/local/bin/python3

import requests

url = '$YOUR_LOGSCALE_URL/graphql'
mydata = r'''{"query" : "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}"
}'''

resp = requests.post(url,
                     data = mydata,
                     headers = {
   "Authorization" : "Bearer $TOKEN",
   "Content-Type" : "application/json"
}
)

print(resp.text)
Node.js
javascript
const https = require('https');

const data = JSON.stringify(
    {"query" : "mutation {
  deleteEventForwardingRule( input: 
       { viewName: \"humio\", 
         id: \"abc123\"}
  )
}"
}
);


const options = {
  hostname: '$YOUR_LOGSCALE_URL',
  path: 'graphql',
  port: 443,
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Content-Length': data.length,
    Authorization: 'BEARER ' + process.env.TOKEN,
    'User-Agent': 'Node',
  },
};

const req = https.request(options, (res) => {
  let data = '';
  console.log(`statusCode: ${res.statusCode}`);

  res.on('data', (d) => {
    data += d;
  });
  res.on('end', () => {
    console.log(JSON.parse(data).data);
  });
});

req.on('error', (error) => {
  console.error(error);
});

req.write(data);
req.end();
Example Responses
Success (HTTP Response Code 200 OK)
json
{
  "data": {
    "deleteEventForwardingRule": true
  }
}

Given Datatype

For this input datatype, you would give the unique identifier of the event forwarding rule to delete, and the name of the associated repository. This is described in the table here:

Table: DeleteEventForwardingRule

ParameterTypeRequiredDefaultStabilityDescription
Some arguments may be required, as indicated in the Required column. For return datatypes, this indicates that you must specify which fields you want returned in the results.
Table last updated: Sep 18, 2024
idstringyes Long-TermUnique identifier of the event forwarding rule.
repoNamestringyes Long-TermThe name of the repository associated with the event forwarding rule.