You can include labels with aggregate alerts, but you may have only ten labels for each. Therefore, you may want to delete some labels as you go along. You can use the removeAggregateAlertLabel() GraphQL mutation to remove a label from an aggregate alert. However, this mutation is deprecated since it doesn't support multiple labels. It will be removed at the earliest in version 1.273. Use instead removeAggregateAlertLabels().

There's no mutation for changing labels. Instead, you'll have to use this mutation or the new one, and then use addAggregateAlertLabels() to add new labels.

Hide Query Example

Show Aggregate Alert Labels Query

For more information on saved queries, see the Aggregate alerts documentation page. To manage labels through the UI, see the Manage Triggers page of the main documentation.

Stability Level Deprecated

Syntax

graphql
removeAggregateAlertLabel(
       input: RemoveAggregateAlertLabel!
    ): boolean

For the input, you have to give the name of the view or repository, and the unique identifier of the aggregate alert from which you want to remove a label (click on Show Query below). And, you'll have to provide the label to remove.

There isn't a special return datatype for this mutation field. You'll get only confirmation of success or failure. The new mutation, removeAggregateAlertLabels() will return details on the aggregate alert, including a list of labels for it. That's much more useful.

Hide Query Example

Show Aggregate Alert Identifiers Query

Example

Raw
graphql
mutation {
  removeAggregateAlertLabel(
    input: { 
      viewName: "humio",
      id: "abc123",
      label: "aggie-alert-1"  }
  )
}
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 {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}"
}
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 {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}"
}
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 { ^
  removeAggregateAlertLabel( ^
    input: {  ^
      viewName: \"humio\", ^
      id: \"abc123\", ^
      label: \"aggie-alert-1\"  } ^
  ) ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}"
}'
    "$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 {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}";
$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 {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}"
}'''

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 {
  removeAggregateAlertLabel(
    input: { 
      viewName: \"humio\",
      id: \"abc123\",
      label: \"aggie-alert-1\"  }
  )
}"
}
);


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": {
    "removeAggregateAlertLabel": true
  }
}

Given Datatype

For this input datatype, you'll have to give the unique identifier of the aggregate alert, the name of the related view or repository, and the label you want to remove from the aggregate alert. The table below describes this. Click on the Show Query link under the Syntax section above for an example of how to get the aggregate alert identifiers.

Table: RemoveAggregateAlertLabel

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: Aug 11, 2025
idstringyes Long-TermThe unique identifier of the aggregate alert.
labelstringyes Long-TermThe label to remove from the aggregate alert.
viewNameRepoOrViewNameyes Long-TermThe name of the view of the aggregate alert. RepoOrViewName is a scalar.