Spaces method and path for this operation:
put /s/{space_id}/api/apm/settings/agent-configuration
Refer to Spaces for more information.
Create or update an agent configuration. You must have all privileges for the APM and User Experience feature in Kibana. When updating an existing configuration, the ?overwrite=true query parameter is required. If the configuration already exists and overwrite is not set to true, the API returns a 400 error. When successful and Fleet is enabled, APM package policies are synchronized accordingly.
Headers
-
The version of the API to use
Value is
2023-10-31. Default value is2023-10-31. -
A required header to protect against CSRF attacks
PUT
/api/apm/settings/agent-configuration
curl \
--request PUT 'https://<KIBANA_URL>/api/apm/settings/agent-configuration' \
--header "Authorization: $API_KEY" \
--header "Content-Type: application/json" \
--header "elastic-api-version: 2023-10-31" \
--header "kbn-xsrf: true" \
--data '{"agent_name":"nodejs","service":{"environment":"production","name":"frontend"},"settings":{"capture_body":"off","transaction_max_spans":"500","transaction_sample_rate":"0.4"}}'
Request example
Run `PUT /api/apm/settings/agent-configuration` to create or update configuration details.
{
"agent_name": "nodejs",
"service": {
"environment": "production",
"name": "frontend"
},
"settings": {
"capture_body": "off",
"transaction_max_spans": "500",
"transaction_sample_rate": "0.4"
}
}
Response examples (200)
An example of a successful response from `PUT /api/apm/settings/agent-configuration`. The response body is intentionally empty.
{
"$ref": "#/components/examples/APM_UI_agent_configuration_intake_object_put_200_response1"
}
Response examples (400)
An example of a 400 Bad Request response, returned when the request payload or query parameters fail validation.
{
"error": "Bad Request",
"message": "[request body]: expected value of type [string] but got [undefined]",
"statusCode": 400
}
Response examples (401)
An example of a 401 Unauthorized response, returned when the request is missing valid authentication credentials.
{
"error": "Unauthorized",
"message": "[security_exception]: missing authentication credentials for REST request",
"statusCode": 401
}
Response examples (403)
An example of a 403 Forbidden response, returned when the authenticated user lacks the required APM and User Experience privileges.
{
"error": "Forbidden",
"message": "Insufficient privileges to perform this action. The APM and User Experience feature requires `all` privileges.",
"statusCode": 403
}
Response examples (404)
An example of a 404 Not Found response, returned when the requested resource does not exist or the feature is not available on the current deployment.
{
"error": "Not Found",
"message": "Not Found",
"statusCode": 404
}