Fictional example · not a customer case study
Example server inventory for a small software project
This sample uses documentation-only IP addresses and made-up names. It contains no real infrastructure, customers, or credentials.
| Name | IP Address | Ports | Tags | Project | Environment | Cloud Provider | OS |
|---|---|---|---|---|---|---|---|
| api-edge-01 | 192.0.2.10 | 22, 443 | production, api | Northstar | Production | Example Cloud | Ubuntu LTS |
| worker-stage-01 | 198.51.100.24 | 22, 8080 | staging, worker | Northstar | Staging | Example Cloud | Debian |
| db-dev-01 | 203.0.113.18 | 22, 5432 | development, database | Northstar | Development | Example Cloud | Ubuntu LTS |
Why this example uses both tags and fields
Project, Environment, Cloud Provider, and OS have one consistent meaning across rows, so they work well as structured fields. Tags are more flexible: they capture concerns that can overlap, such as production, api, worker, or database.
Keep sensitive details out
This example deliberately has no usernames, passwords, private keys, access tokens, or real server addresses. Put secrets in a dedicated secrets manager, not in an inventory table.
See the server inventory guide, tags and custom fields guide, or spreadsheet import guide.