Re: [Observium] Custom device types
You probably don't want to change any of that...
What are you trying to accomplish?
Adam.
Robbie Wright robbie@siuslawbroadband.com wrote:
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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.
Since we're still trying to find the right balance in the location (and yes, I know you can customize/overwrite them, but I'm with you, automation is your friend) and device type, we went down the path of organizing, for instances, switches into core, distribution, and access switch device types. Having fast access to all of our core switches and different DC's for example would be a very convenient view for us. Such as being able to drill down into all of the access switches within one location.
Just thinking out loud, looking for how others are organizing this. Automation rocks, but it is only as good as the data you're putting in.
Robbie Wright Siuslaw Broadband http://siuslawbroadband.com 541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
On Mon, Oct 7, 2013 at 4:54 PM, Adam Armstrong adama@memetic.org wrote:
You probably don't want to change any of that...
What are you trying to accomplish?
Adam.
Robbie Wright robbie@siuslawbroadband.com wrote:
Has anyone done anything to customize the device types? I poked around in the config file and it does look like each type has its own array of variables that go with it.
Robbie Wright Siuslaw Broadband http://siuslawbroadband.com 541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
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
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
On 2013-10-09 20:45, Robbie Wright wrote:
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 documentation [3] it looks like that. That would get us some of the flexibility in structuring as well. Is that still on the roadmap?
We wrote one, the purpose of custom parsers is to write your own :)
adam.
Good call Adam, we were just looking for any documentation around it. We'll poke around in the code and see what we can come up with.
Robbie Wright Siuslaw Broadband http://siuslawbroadband.com 541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
On Wed, Oct 9, 2013 at 1:13 PM, Adam Armstrong adama@memetic.org wrote:
On 2013-10-09 20:45, Robbie Wright wrote:
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 documentation [3] it looks like
that. That would get us some of the flexibility in structuring as well. Is that still on the roadmap?
We wrote one, the purpose of custom parsers is to write your own :)
adam.
______________________________**_________________ observium mailing list observium@observium.org http://postman.memetic.org/**cgi-bin/mailman/listinfo/**observiumhttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I think the existing one is includes/port-descr-parser.inc.php or similar.
There's a config variable to define what file is include()d for it.
You just take the ifDescr and generate an array containing parts that we put into the database, it's pretty simplistic.
adam.
On 2013-10-10 07:50, Robbie Wright wrote:
Good call Adam, we were just looking for any documentation around it. We'll poke around in the code and see what we can come up with.
Robbie Wright Siuslaw Broadband [2] 541-902-5101
**For support issues, please email support@siuslawbroadband.com.**
On Wed, Oct 9, 2013 at 1:13 PM, Adam Armstrong adama@memetic.org wrote:
On 2013-10-09 20:45, Robbie Wright wrote:
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 documentation [3] it looks like
that. That would get us some of the flexibility in structuring as well. Is that still on the roadmap?
We wrote one, the purpose of custom parsers is to write your own :)
adam.
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [1]
Links:
[1] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [2] http://siuslawbroadband.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
Robbie Wright -
Sander Steffann