![]() The latter has a ton of functionality that can produce some interesting data for purposes of traffic engineering, among other things. There are interesting Netflow tools like Elastiflow and pmacct that are more robust than nfsen. ![]() With streaming telemetry becoming more of a thing, there will definitely be a shift away from SNMP for things that are polled for statistics. I think it also has (better?) support for weathermap, so I could technically replace InterMapper with weathermap and collapse the tool chain a bit. I believe that LibraNMS has at some capability to use more robust graphing engines, which for me would be great I find rrd is a little limiting these days. Smokeping for what smokeping does (but I just discovered vaping this morning, which looks awesome and will get some love). Netflow collection and graphing is handled by nfsen, Syslog and SNMPTRAP collection, correlation and alerting is handled by Splunk, I feel that a visual representation of the physical network topology is extremely helpful for many aspects of day-to-day operations, so InterMapper handles that, Observium handles polling, graphing and alerting for SNMP exposed objects on network devices, Here’s a snapshot of what tends to work for me, along with my $0.02 of thoughts: (resending with really, really the correct from:)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |