I know this has been asked/answered, but the whole archives thing...what's the history behind [the lack of] support for IS-IS data in Observium, are there any plans to add it at any point, and would it be of value to anyone else? Even basics like warning on adjacency changes, tracking neighbors over time, etc. would be great...I would personally find it of value for an additional sanity check during maintenances or outages - an ISIS health overview tab for a device with the ISO address/area, participating interfaces, and stats.
Generalizing the data pool: any current thoughts around creating an abstraction layer between Observium and its data source? Mysql as the sole backend presents some challenges for us in trying to scale Observium to production. OBQL? :)
Sort-of on the tails of that last question, has there been any discussion about adapting Observium to take advantage of network devices which emit metrics using thrift/protobuf? E.g. using some other data pipeline/collection system as a data source...or even doing the collection itself and doing the necessary quantization/processing to produce a useable view.
Last one in that train of thought, any thoughts around incorporating additional data collectors other than simple snmp polling (e.g. facebook's udppinger or fbtracert)?
Aaron
--
Aaron Finney
Network Engineer | OpenX
888 East Walnut Street, 2nd Floor | Pasadena, CA 91101
o: +1 (626) 466-1141 x6035 |
aaron.finney@openx.com