Sander, thanks for pointing that out. I hadn't seen that in the config options yet and we tested some of them out yesterday. Between that and tweaking some of the descriptions on the ports (transit, core, cust, etc) we may be able to make some work.
Adam, it looks like you guys are planning to do custom parsers for port types, at least reading into the documentationhttp://www.observium.org/wiki/Interface_Description_Parsingit looks like that. That would get us some of the flexibility in structuring as well. Is that still on the roadmap?
Robbie Wright Siuslaw Broadband http://siuslawbroadband.com 541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
On Tue, Oct 8, 2013 at 2:42 AM, Sander Steffann sander@steffann.nl wrote:
Hi Robbie,
Honestly, the bigger use case is organization of devices. Trying to find
the balance between locations and devices types. The only down side with geography-based locations in SNMP is naming conventions. For example, we have dozens of devices spread around the same city (and cities) so simply putting in the city/state doesn't work, we need the full address. Putting a legit address in an snmp location for the map to work is acceptable, but we had historically put in our own naming location conventions (ie phx-r1, iad-sw1) etc, similar to CLLI codes.
You can still use that naming convention if you want. You can map your own naming to full addresses in the config:
$config['location_map']['phx-r1'] = "120 East Van Buren St, Phoenix, Arizona 85004, US";
The web interface will always show the 'new' location, not the original one. Also see http://www.observium.org/wiki/Configuration_Options#Map_overview_settings
Cheers, Sander
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium