7a9777b4b5
``TargetPool`` is a pool of targets pending scraping. For now, it uses the ``heap.Interface`` from ``container/heap`` to provide a priority queue for the system to scrape from the next target. It is my supposition that we'll use a model whereby we create a ``TargetPool`` for each scrape interval, into which ``Target`` instances are registered. |
||
|---|---|---|
| coding | ||
| model | ||
| retrieval | ||
| storage | ||
| utility | ||
| .gitignore | ||
| .travis.yml | ||
| CONTRIBUTORS.md | ||
| LICENSE | ||
| Makefile | ||
| Makefile.TRAVIS | ||
| README.md | ||
| main.go | ||
README.md
Prometheus
Bedecke deinen Himmel, Zeus! A new kid is in town.
Prerequisites
- Go 1.0.X.
- LevelDB: (https://code.google.com/p/leveldb/).
- Protocol Buffers Compiler: (http://code.google.com/p/protobuf/).
- goprotobuf: the code generator and runtime library: (http://code.google.com/p/goprotobuf/).
- Levigo, a Go-wrapper around LevelDB's C library: (https://github.com/jmhodges/levigo).
Initial Hurdles
- A bit of this grew organically without an easy way of binding it all together. The tests will pass but slowly. They were not optimized for speed but end-to-end coverage of the whole storage model. This is something immediate to fix.
- Protocol Buffer generator for Go changed emitted output API. This will need to be fixed before other contributors can participate.
Milestones
- In-memory archive, basic rule language, simple computation engine, and naive exposition system.
License
Apache License 2.0