Modifying Tracing Configuration
Function
This API is used to modify the tracing configuration of a function. You can enable or modify the AK/SK or disable the AK/SK.
URI
PUT /v2/{project_id}/fgs/functions/{function_urn}/tracing
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
project_id |
Yes |
String |
Project ID. For details, see Obtaining a Project ID. |
function_urn |
Yes |
String |
Function URN. For details, see the function model description. |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
X-Auth-Token |
Yes |
String |
User token. It can be obtained by calling the IAM API used to obtain a user token. The value of X-Subject-Token in the response header is the user token. |
Content-Type |
Yes |
String |
Message body type (format). |
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
tracing_ak |
No |
String |
AK of APM. |
tracing_sk |
No |
String |
SK of APM. |
Response Parameters
Status code: 400
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Status code: 403
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Status code: 500
Parameter |
Type |
Description |
---|---|---|
error_code |
String |
Error code. |
error_msg |
String |
Error message. |
Example Requests
Modify the AK/SK in a function's tracing configuration.
PUT /v2/{project_id}/fgs/functions/{function_urn}/tracing { "tracing_ak" : "xxx", "tracing_sk" : "yyy" }
Example Responses
Status code: 400
Bad Request
{ "error_code" : "FSS.1128", "error_msg" : "function[xxx] not existed" }
Status code: 403
FORBIDDEN
{ "error_code" : "FSS.0403", "error_msg" : "invalid token" }
Status code: 500
Internal error.
{ "error_code" : "FSS.0500", "error_msg" : "xxx" }
Status Codes
Status Code |
Description |
---|---|
200 |
OK |
400 |
Bad Request |
403 |
FORBIDDEN |
500 |
Internal error. |
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.