Update a private location
- Base URL
-
https://{kibana_url}
Refer to Spaces for more information.
Update an existing private location's label, tags, or agent policy.
You must have all privileges for the Synthetics and Uptime feature in the Observability section of the Kibana feature privileges.
When a private location's label is updated, all monitors using this location are also updated to maintain data consistency.
When a private location's agent policy is changed, the package policies of all monitors using this location are deleted and recreated on the new agent policy. Monitors stop running on the previous agents until agents on the new policy pick them up. The new agent policy must be available in all spaces of the private location and must not be used by another private location.
Required authorization
- Privileges uptime-read and private-location-write and uptime-write
Request body
-
agentPolicyIdstring · min length: 1 · max length: 1024 -
The ID of the Fleet agent policy to move the private location to.
-
labelstring · min length: 1 · max length: 1024 -
A new label for the private location. Monitors using this location are updated to match.
-
An array of tags to categorize the private location.
Responses
A successful response.
-
isInvalidboolean -
Indicates whether the location is invalid. If
true, the location is invalid, which means the agent policy associated with the location is deleted. -
namespacestring -
The namespace of the location, which is the same as the namespace of the agent policy associated with the location.
-
An array of tags to categorize the private location.
If the label is shorter than 1 character, or the agentPolicyId is not available in the current space, does not cover all spaces of the private location, or is already used by another private location, the API returns a 400 Bad Request response with a corresponding error message.
If the private location with the specified ID does not exist, the API returns a 404 Not Found response.