๐ŸŽฏAPI Stability
Long-TermThis API is stable and will remain supported across versions with minimal breaking changes.

Summary

The enableLegacyAlert() mutation reactivates a disabled legacy alert in a LogScale repository or view. Legacy alerts run a scheduled query over a configured time window. They trigger associated actions when the query returns results. While disabled, an alert does not execute its query or fire its actions. Use this mutation to restore scheduled execution after a maintenance window or planned suppression period. To disable a legacy alert, use disableLegacyAlert().

Syntax

graphql
enableLegacyAlert(
      input: EnableAlert!
   ): Alert

The required input argument accepts an EnableAlert input object with two required fields: the repository or view name in viewName, and the unique identifier of the legacy alert in id. Use the Show Alerts Query in the Related section to retrieve alert identifiers. See Input Parameters for details on the EnableAlert input type.

The mutation returns an Alert object on success. The object includes the alert's query string, triggered actions, and any error messages from the most recent execution. The return value is nullable; a null result indicates the alert was not found in the specified repository or view.

Example

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

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 {
  enableLegacyAlert( input: 
    { viewName: \"humio\",
      id: \"abc123\" } )
  { id, enabled }
}"
}
);


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": {
    "enableLegacyAlert": {
      "id": "abc123",
      "enabled": true
    }
  }
}

Input Parameters

Provide the repository or view name in viewName and the unique identifier of the legacy alert in id. Both fields are required. Use the Show Alerts Query in the Related section to retrieve alert identifiers for a given repository or view. The following table describes the EnableAlert input type:

Returned Values

The mutation returns an Alert object reflecting the alert's current configuration and state. The object includes the alert's query string, the actions triggered when the query returns results, and any error messages from the most recent execution. Inspect error message fields to diagnose alerts that were not firing as expected before they were disabled. The return value is nullable; a null result indicates the alert was not found in the specified repository or view.