Skogul is a collector of various data, but unlike most similar tools, it does NOT provide a backend storage, and the aim is to provide a generic, reasonably future-proof API that can be built upon using various backend writers, transformers and more.
It is very much a work in progress, and is aimed to handle both simple installations where there's roughly a 1:1 between input sources and storage backends, and large enterprise installations where there can be hundreds of different input sources all being routed and transformed based on site-specific needs.
The first use-case is expected to be Gondul (https://github.com/gathering/gondul), where it will provide a shim-layer between SNMP collectors, ping collectors and DHCP event data collectors; and postgresql and influxdb as storage backends.
The rationale is that the problem of writing an efficient snmp collector should not be tightly coupled to where you store the data. And where you store the data should not be tightly coupled with how you receive it, or what you do with it.
At present time, it's not suited for much more than looking at the general development of the architecture. As such, build-instructions and more are explicitly left out.
Skogul is meant to scale well. At present time, there are known flaws in the implementation, but still, simple local testing on a laptop is able to produce decent results.
The above graph is from a very simple test on a laptop (with a quad core i7), using the provided tester to write data to influxdb. It demonstrates that despite well-known weaknesses (specially in the influx-writer), we're able to push roughly 600-800k values/s through Skogul.
The laptop in question was using about 150-190% CPU for skogul and 400% for InfluxDB, the rest went to the testers. No real attempt at tuning was done, but a few different scenarios were tested.
Note that the general values/s is decent both with a ton of values for each metric, and just a handful of values per metric, but tons of metrics per containers.
As future work will introduce buffers and "batch aggregators" to make it better equipped to handle irregular traffic, it's is expected and acceptable that performance dips when the number of values per container drops.
Skogul is a Valkyrie. After extensive research (5 minutes on wikipedia with a cross-check on duckduckgo), this name was selected because it is reasonably unique and is also a valkyrie, like Gondul, a sister-project.
Being a whole week old, a name change was due, so you might find references to Gollector here and there, if I suck at grep(1).