create_device_input
Create or rotate an authenticated collector channel for this device. Ownership is checked before the app asks the input central. The server chooses the channel id and authenticates batches only against a hash of the collector credential. The whole setup this call returns — credential included — is also saved, encrypted with a key only the input central holds and bound to that credential, so the owner can read it again with GET /api/ambientes/:id/inputs/:collector/setup. The credential does not expire: a device that stays off for weeks reconnects with it. It stops working only when a new configuration rotates it or the channel is removed. A repeated call for the same collector rotates the credential, replaces the saved setup and replaces monitoring with the list sent — that is how the monitored scope is edited — so the configuration on the device stops authenticating until it is replaced; a paused channel stays paused. DNS selects the receiver; it never authenticates the device.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Device environment UUID v4; the report URL is a one-hour write capability. | |
| collector | Yes | alloy, telegraf, opentelemetry, ncpa, collectd or snmp. | |
| monitoring | Yes | One or more of system (the whole machine), host (CPU, memory, load and uptime), disk, network, mysql and asterisk. `system` already includes host, disk and network, and those three together are stored as `system`. Items the collector cannot collect (see `collects` on the channel) are not measured. |