We do already collect data with a number of other protocols and methods, like the agent, ipmi, and dragging data from things like smokeping and munin.

It would certainly be possible to accept data in other formats, but I'm not sure if it's something we'd be able to implement without it being of use to a significant number of people.

On 19 Jul 2016, at 02:45, Aaron Finney <aaron.finney@openx.com> wrote:

Heh, fair enough.

Network devices emitting stats via a lightweight protocol (e.g. thrift) is something we've waited a long time for; no more polling your devices every x minutes hoping to see the needle in the haystack (one click of the shutter every 300s). Juniper just added it, and I talked with the SnapRoute guys about it last week...I assume other open platforms like fboss/etc probably support emitting metrics also. SNMP can't die soon enough for me. :D

The other utils - udppinger and fbtracert - are tools which FaceBook has open-sourced that they use internally for proactively monitoring their network, e.g. the health of individual ecmp links within the dc fabric. The question was more around extending a device to accept external inputs/data-sources for additional status outside of what you can get by polling every x seconds, though I understand that that kind of goes against a major architecture principle of Observium (simplicity for the user).

Cheers,

Aaron

On Fri, Jul 15, 2016 at 1:57 AM, Adam Armstrong <adama@memetic.org> wrote:
Hi Aaron,

ISIS support doesn't yet exist because whoever wrote the ISIS MIB was a fool who thought it a good idea to use indexing that requires far more effort to decypher than I've ever had the motivation to expend. It's been on the list practically as long as Observium as existed, but each time I look at it, it just doesn't go anywhere.

The others are no, no and no. :)

Aside from not actually knowing what most of those things are, the resource cost to us of trying to implement stuff like that is orders of magnitude higher than the usefulness of them. The fact that I've not even heard of any of them goes some way to suggesting how useful they'd be to the majority of the user base! :D

adam.

Sent from Mailbird

On 15/07/2016 10:39:14, Aaron Finney <aaron.finney@openx.com> wrote:
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
Advertising Age Best Places to Work
Deloitte's Technology Fast 500™
www.openx.com | Twitter | Facebook | LinkedIn | YouTube

_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium

--
Aaron Finney
Network Engineer | OpenX
888 East Walnut Street, 2nd Floor | Pasadena, CA 91101
o: +1 (626) 466-1141 x6035 | aaron.finney@openx.com
Advertising Age Best Places to Work
Deloitte's Technology Fast 500™
www.openx.com | Twitter | Facebook | LinkedIn | YouTube
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium