The endpoint of a Lindorm TSDB instance

You can view the endpoint of an ApsaraDB for Lindorm (Lindorm) TSDB instance on the Instance Details page. For example, the endpoint may be ts-xxx.hitsdb.rds.aliyuncs.com:8242.

Protocols

You can send requests by using HTTP.

Request methods

You can send requests by using the HTTP POST method.

Request paths

You must specify the path for the operation in each request. For example, enter /api/delete_data.

Request parameters

You can specify request parameters for each write request on Lindorm TSDB. The request parameters specify the expected content in the response and the timeout period of the write request.

Requested content

You must specify the requested content for each request on Lindorm TSDB. Specify the data that you need to query and the operation that you need to perform.

Standard

The HTTP API of Lindorm TSDB is RESTful. This means that you must use an HTTP method to specify an operation and comply with REST. If you use the GET method, the system only returns data. If you use the PUT or POST method, you can only modify data. If you sue the DELETE method, you can only delete data.

However, in some cases, methods such as DELETE and PUT are blocked by firewalls or proxies, or not implemented in a client. In addition, most developers use GET and POST to send requests. The Lindorm TSDB API allows you to add the method_override parameter to a query string instead of using HTTP methods. This parameter allows the client to use query strings instead of the HTTP request body to call most API operations. For example, you do not need to use the GET method to delete data. Instead, you can use the following query string: /api/delete_meta?m=cpu.usage&method_override=delete. The following table lists HTTP methods and corresponding values of the method_override parameter.

HTTP METHOD Description method_override
GET Queries data. N/A
POST Submits data. method_override=post
PUT Overwrites data. method_override=put
DELETE Deletes data. method_override=delete