Querying Tracing Configuration
Function
This API is used to query the tracing configuration of a function.
URI
GET /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). |
Response Parameters
Status code: 200
|
Parameter |
Type |
Description |
|---|---|---|
|
tracing_ak |
String |
AK of APM. |
|
tracing_sk |
String |
SK of APM. |
Status code: 403
|
Parameter |
Type |
Description |
|---|---|---|
|
error_code |
String |
Error code. |
|
error_msg |
String |
Error message. |
Status code: 404
|
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
Query the tracing configuration of a function.
GET /v2/{project_id}/fgs/functions/{function_urn}/tracing
Example Responses
Status code: 200
ok
{
"tracing_ak" : "xxx",
"tracing_sk" : "******"
}
Status code: 403
FORBIDDEN
{
"error_code" : "FSS.0403",
"error_msg" : "invalid token"
}
Status code: 404
Not Found
{
"error_code" : "FSS.0404",
"error_msg" : "can not find tracing aksk"
}
Status code: 500
Internal error.
{
"error_code" : "FSS.0500",
"error_msg" : "xxx"
}
Status Codes
|
Status Code |
Description |
|---|---|
|
200 |
ok |
|
403 |
FORBIDDEN |
|
404 |
Not Found |
|
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.