The platform and data_region attributes are immutable and cannot be changed after a collector is created. A custom bucket can only be added when creating a collector.
Explore documentation
Update a collector
Updates an existing collector. Only the provided parameters will be changed.
URL parameters
The unique identifier of the collector to update.
Headers
Bearer $TOKEN
Body parameters
A new unique name for the collector.
A new note for the collector. Send null to clear the existing note.
Custom retention period for logs, in days. This is only available on select plans.
Custom retention period for metrics, in days. This is only available on select plans.
Set to true to pause data ingestion, or false to resume.
The ID of the resource group to assign the collector's associated sources to. Send 0 or null to remove the assignment.
A custom format for messages displayed in live tail, with columns wrapped in {column} brackets. Example: "PID: {message_json.pid} {level} {message}". Send null to clear.
For details, see Live tail docs.
A VRL program to be applied to logs server-side. Send null to remove.
A custom Vector configuration in YAML format. Send null to remove.
An object containing detailed configuration options to update. Only the keys provided in this object will be modified, including inside components. For a full list of options, see the configuration object section in the Create collector API documentation. Send false in components to turn a component off. If you send the legacy metrics_databases without metrics_cluster, it can also set whichever of metrics_postgres, metrics_mysql, metrics_elasticsearch and metrics_pgbouncer you leave out, so send those four explicitly.
An array of database objects to add, update, or remove. To remove a database, include its id and set _destroy: true.
Rotates the key pair of the custom bucket the collector already uses. Send only access_key_id and secret_access_key. We verify the new pair against the bucket first; if that fails, the whole request is rejected with a 422 and nothing is changed. A bucket shared with other collectors or sources is rotated for all of them. Send the new pair before deactivating the old one to rotate without downtime.
Updating Databases
To manage monitored databases, provide an array to the databases parameter. Each object in the array can either update an existing database (by providing its id) or create a new one (by omitting the id). To delete a database, include its id and set _destroy: true.
The collector was updated successfully.
Response body
A collector with the specified ID was not found.
Validation failed due to invalid or unsupported parameters.
Response body
Example Request