Summary

The createRemoteTableConfig() GraphQL mutation is used to create a remote table configuration.

Stability Level Preview

Syntax

graphql
createRemoteTableConfig(
      input: CreateOrUpdateRemoteTableConfigInput!
   ): RemoteTableConfig!

For the input, you'll have to give the name of the remote table configuration, and any additional parameters needed or that you want to change for an existing one. See the Input Parameters section for details.

For the results, you can get information on the remote table configuration. See the Returned Values section for what's available.

Example

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

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 {
  createRemoteTableConfig(
    input: { 
      connectionName: \"some-table\",
      connectionDescription: \"Some Table\"
    }
  ) { connectionName }
}"
}
);


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": {
    "createRemoteTableConfig": {
      "connectionName": "some-table"
    }
  }
}

Input Parameters

For the input, you would give the name of the remote table configuration, and any additional parameters needed for you situation when creating the configuration item — or that you want to change for an existing one. These parameters are listed and described below:

Table: CreateOrUpdateRemoteTableConfigInput Input Datatype

ParameterTypeRequiredDefaultStabilityDescription
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: May 8, 2026
connectionConfigGenericGenericConnectionConfigInput  PreviewThe configuration of a generic remote table. See GenericConnectionConfigInput.
connectionConfigLogscaleLogScaleConnectionConfigInput  PreviewThe configuration of a LogScale remote table. See LogScaleConnectionConfigInput.
connectionDescriptionstringyes PreviewThe description of the remote table configuration.
connectionNamestringyes PreviewThe name of the remote table configuration. This must be unique in the organization.
accessRequirementAccessRequirementInput  PreviewAn access requirement that must be fulfilled to run a remote table query based on this configuration. See AccessRequirementInput.

Returned Values

For the results, you can get the URL and the configuration of a remote table. These are partly described in the table below, but you'll have to click on the one special datatype and further for more details.

Table: RemoteTableConfig Datatype

ParameterTypeRequiredDefaultStabilityDescription
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: Feb 16, 2026
accessRequirementRemoteTableAccessRequirementyes PreviewAn access requirement needed to run a remote table query based on this configuration. See RemoteTableAccessRequirement.
connectionConfigRemoteTableGenericConnectionSensitiveConfigyes PreviewThe configuration of the remote table connection. See RemoteTableGenericConnectionSensitiveConfig.
connectionDescriptionstringyes PreviewThe description of the remote table configuration.
connectionNamestringyes PreviewThe name of the remote table connection.
viewIds[string]yes PreviewThe identifiers for the views to which the configuration is connected.