The stopHistoricalQueries() GraphQL mutation is used to stop all historical queries. It ignores live and streaming queries. It requires ManageCluster permission.

To stop all queries running, use the stopAllQueries() mutation. To stop only streaming queries, use stopStreamingQueries(). To stop a specific query, use the killQuery() mutation.

To get a list of running queries, use the runningQueries() query. To see a list of blocked ones, use blockedQueries().

For more information on queries, see the Query Language Syntax reference page. You may also want to look at Live Queries.

API Stability Short-Term

Syntax

graphql
stopHistoricalQueries(
      input: StopQueriesInput
   ): boolean

For the input, you have to indicate whether to stop all historical queries. See the Given Datatype section.

For the results, you'll receive confirmation if successful.

Example

Raw
graphql
mutation {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}
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 {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}"
}
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 {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}"
}
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 { ^
  stopHistoricalQueries( input: ^
    { ^
      clusterWide: True ^
    } ^
  ) ^
}" ^
} '
Windows Powershell and curl
powershell
curl.exe -X POST 
    -H "Authorization: Bearer $TOKEN"
    -H "Content-Type: application/json"
    -d '{"query" : "mutation {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}"
}'
    "$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 {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}";
$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 {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}"
}'''

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 {
  stopHistoricalQueries( input:
    {
      clusterWide: True
    }
  )
}"
}
);


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

Given Datatype

For this input datatype, you only have to indicate whether to stop all historical queries. This is described in the table here:

Table: StopQueriesInput

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: Mar 28, 2025
clusterWideboolean falseShort-TermWhether to stop queries globally. Requires the ManageCluster permission.