3 ms·
The need to overload hostnames like that to me just says you haven't got your inventory system in order. For the price of actually using my asset DB, my alerts
by XorNot 9y ago
The need to overload hostnames like that to me just says you haven't got your inventory system in order.
For the price of actually using my asset DB, my alerts can be sliced and diced exactly by the datacentre/rack/whatever because I'm properly tagging everything.
Whereas for all the times I've heard "oh we won't move servers and if we do we'll re-image them..." just last month (and still ongoing) people have been dragging racks between floors, plugging them in and that's it - so fixed names like that get stuck.
- mugsie 9y agoSure - but from the easy of human pattern matching looking a list of hostnames in a monitoring system without needing to click to a different page I think it is worth it. If you are in the habit of moving racks, then I would agree keeping it only in an inventory system makes sense, but that also requires the asset system to be updated when a rack moves - at which point changing a hostname (which can be autogenerated by dhcp based on that system) an easy step to add.