Deleting a Tracker
Function
This API is used to delete trackers. Only data trackers can be deleted. Deleting a tracker has no impact on the collected traces. When you enable CTS again, you can still view those traces.
URI
DELETE /v3/{project_id}/trackers
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details, see section "Obtaining the Account ID and Project ID" in Cloud Trace Service API Reference. |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
tracker_name |
No |
String |
Tracker name. If this parameter is not specified, all data trackers of a tenant will be deleted. |
tracker_type |
No |
String |
Tracker type. Only data trackers can be deleted. The default value is data. Enumeration values:
|
Request Parameters
None
Response Parameters
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code, in the format of CTS.XXX. |
error_msg |
String |
Error message. |
Example Requests
DELETE https://{endpoint}/v3/{project_id}/trackers?tracker_name=data-tracker-name
Example Responses
None
Status Codes
Status Code |
Description |
---|---|
204 |
The tracker is deleted. |
400 |
The server failed to process the request. |
401 |
The request is rejected due to authentication failure. |
403 |
The server understood the request but refused to authorize it. |
404 |
The server failed to find the requested resource or some trackers failed to be deleted. |
500 |
The server has received the request but encountered an internal error, or some trackers failed to be deleted. |
503 |
The requested service is unavailable. The client should not repeat the request without modifications. |
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot