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