Help Center/ Cloud Search Service/ API Reference/ APIs/ Logstash/ Querying the Template List
Updated on 2024-10-17 GMT+08:00

Querying the Template List

Function

This API is used to query the template list.

Debugging

You can debug this API through automatic authentication in API Explorer.

URI

GET /v1.0/{project_id}/lgsconf/template

Table 1 Path Parameters

Parameter

Mandatory

Type

Description

project_id

Yes

String

Project ID. For details about how to obtain the project ID and name, see Obtaining the Project ID and Name.

Table 2 Query Parameters

Parameter

Mandatory

Type

Description

type

No

String

Template type. custom indicates a user-defined template, and system indicates a system template. If this parameter is not specified, the system searches for both user-defined templates and system templates by default.

Request Parameters

None

Response Parameters

Status code: 200

Table 3 Response body parameters

Parameter

Type

Description

systemTemplates

Array of systemTemplates objects

System template list.

customTemplates

Array of customTemplates objects

Custom template list.

Table 4 systemTemplates

Parameter

Type

Description

id

String

Configuration file ID.

name

String

Configuration file name.

confContent

String

Configuration file content.

desc

String

Description.

Table 5 customTemplates

Parameter

Type

Description

id

String

Configuration file ID.

name

String

Configuration file name.

confContent

String

Configuration file content.

desc

String

Description.

Example Requests

None

Example Responses

Status code: 200

Request succeeded.

{
  "systemTemplates" : [ {
    "id" : "a03b1791-6dc6-453d-961d-88939adc82aa",
    "name" : "elasticsearch",
    "confContent" : "xxxxxxxx",
    "desc" : "logstash config for es"
  } ],
  "customTemplates" : [ {
    "id" : "2e16fbba-49bf-4690-93af-3f89025c6523",
    "name" : "es_to_https_es",
    "confContent" : "xxxxxxxx",
    "desc" : "From ES to an ES security cluster"
  } ]
}

Status Codes

Status Code

Description

200

Request succeeded.

400

Invalid request.

The client should modify the request instead of re-initiating it.

409

The request cannot be processed due to a conflict.

This status code indicates that the resource that the client attempts to create already exits, or the requested update failed due to a conflict.

412

The server did not meet one of the preconditions contained in the request.

Error Codes

See Error Codes.