Hetzner
Reads Hetzner Cloud projects and counts servers per customer. Since Hetzner has no notion of a customer structure, your own mapping decides which project belongs to which customer.
Setup
- In the Hetzner Cloud console, generate an API token per project (read access is sufficient).
- In the Hetzner view, store the tokens via the gear icon — several projects = several tokens.
- In the "Mapping" dialog, assign each project (or label) to a customer with a click.
Customer mapping
The mapping follows the uniform merge-list mechanics: a list of all projects with server count and current customer, assign/edit/detach with a click; several projects can point to the same customer. Unmapped projects are shown as a hint in the view (their servers do not count).
Metrics
| Metric | Count |
|---|---|
servers | cloud servers of the mapped projects |
Specifics
- The mappings count as a customer source in the customer view and are automatically renamed along with merges.
- Customer name = own mapping → automatic rename detection is not needed here.