Summary

The deleteRemoteTableConfig() mutation permanently removes a named remote table configuration from your organization. Deleting a configuration does not automatically disconnect it from any views; you must call disconnectRemoteTableConfig() for each attached view before calling this mutation. Once deleted, the configuration name becomes available for reuse. The mutation returns true when the deletion completes. LogScale returns a GraphQL error if the configuration name does not exist or if the configuration still has connected views.

API Stability Preview

Syntax

graphql
deleteRemoteTableConfig(
       input: DeleteRemoteTableConfigInput!
    ): Boolean!

The required input argument takes a DeleteRemoteTableConfigInput object containing the connectionName of the configuration to delete. See the Input Parameters section for the fields in that object.

The mutation returns a non-null Boolean!. A successful deletion returns true. LogScale does not return false — failed operations return a GraphQL error instead of a boolean value.

Example

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

Input Parameters

The input argument requires a DeleteRemoteTableConfigInput object. Provide the connectionName of the configuration to delete. This name uniquely identifies the configuration within your organization and must match an existing configuration exactly.

Table: DeleteRemoteTableConfigInput 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 12, 2026 
connectionNameStringyes Preview The name of the remote table configuration to delete.

Returned Values

The mutation returns Boolean!. A return value of true confirms that the configuration was removed from the organization. LogScale never returns false — if the deletion fails (for example, because the configuration has active view connections or the name does not exist), LogScale returns a GraphQL error instead. After a successful deletion, any subsequent queries against views that referenced this configuration will fail until a new configuration is created and connected.