Summary

The deleteAggregateAlert() mutation deletes an aggregate alert from a LogScale repository. On success, it returns true. This mutation is deprecated. Use deleteAggregateAlertV2() instead. LogScale will remove deleteAggregateAlert() at the earliest in version 1.267.

API Stability Deprecated

Syntax

graphql
deleteAggregateAlert(
      input: DeleteAggregateAlert!
   ): Boolean!

The input argument accepts a required DeleteAggregateAlert object containing the unique identifier of the aggregate alert and the name of the associated view. The mutation returns a non-null Boolean!. It returns true on success or throws an error on failure. See the Input Parameters section for field details.

Example

Raw
graphql
mutation {
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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 { ^
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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 {
  deleteAggregateAlert(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": {
    "deleteAggregateAlert": true
  }
}

Input Parameters

The input argument requires a DeleteAggregateAlert object. Provide the unique identifier of the alert and the name of the associated view. Select Show Aggregate Alerts Query in the Related section to retrieve alert identifiers.

Table: DeleteAggregateAlert Input Datatype

ParameterTypeRequiredDefaultStabilityAvailabilityDescription
Some input parameters may be required, as indicated in the Required column. For return values, this indicates that you are assured a value if the field is requested for the results. 
Table last updated: Oct 14, 2026 
idStringyes Long-Term The unique identifier of the aggregate alert.
viewNameRepoOrViewNameyes Long-Term The name of the view of the aggregate alert. RepoOrViewName is a scalar.