Yesterday I had the opportunity of being part of a Statseeker presentation. For those who haven’t heard of this organization, Statseeker offers a single server solution for monitoring very large scale networks. To put things into perspective, they have single server solutions deployed that monitor over 500,000 interfaces. Furthermore, this is done with minimal storage requirements. A rule of thumb storage estimate is 1GB, per 1000 interface, per year of retention.
For those wanting to see the full demonstration, the video can be at the URL below–
Based on the presentation and demonstration, I think Statseeker performed quite well. I think it achieves the following claims:
- Very Large Scale Monitoring from a Single Server
- Minimal Time Between Poll Cycles (60 second data points)
- No Summarization of Old Data
Furthermore, the Statseeker demonstration performed surprising well at obtaining random data points from 2 years ago. These data points were, as advertised, not summarized in any way. The solution offered several perspectives and sort options to the data set. These vantage points should allow an engineer to quickly see potential issues and hotspots in a network. As a result, I think this product is a solid choice for organizations that need this granularity of history and have some significance to the size of the network being monitored. Additionally, I think this is a fantastic solution for an organization that wants interface monitoring to work well out of the box with minimal configuration and tweaking.
With a solution that powerful, why wouldn’t every organization be using it? There are a few cases that I can think of. The first hurdle is the fact that we are tech people and we often want the knobs to turn. It’s not that Statseeker totally takes away the ability to tweak the solution, but it doesn’t appear to be built with flexibility in mind (although I get the sense that future versions will have some enhancements in this regard). Another point I would make is that not all networks need the scale that can be afforded by this solution. In some cases these smaller networks may benefit from greater integration and more predefined alerting templates and triggers.
Statseeker can certainly provide a wealth of information quickly. Very granular information about statistics without any normalization (aka loss) of data is very attractive. The methods employed to give the solution its scale are also beneficial when monitoring a large number of ports. From what I have seen, this is a perfect solution for an organization that needs these benefits but don’t want to build it manually. Furthermore, this seems to be a good solution to resolve the challenges of monitoring very large networks.
Disclaimer: Statseeker is one of the sponsors for Networking Field Day 4. As a result, their sponsorship covered a portion of the cost of my travel and expenses associated with my attendance to this event. This article was written without any restrictions or requirement to do so. My opinions on this product are my own and are accurately reflected.