156 commits

Author	SHA1	Message	Date
Matt T. Proud	efe61c18fa	Refactor target scheduling to separate facility. ... ``Target`` will be refactored down the road to support various nuanced endpoint types. Thusly incorporating the scheduling behavior within it will be problematic. To that end, the scheduling behavior has been moved into a separate assistance type to improve conciseness and testability. ``make format`` was also run.	2013-01-13 10:43:37 +01:00
Julius Volz	56384bf42a	Add initial config and rule language implementation.	2013-01-07 23:43:36 +01:00
Matt T. Proud	52f52a7ee2	Include nascent instrumentation of stack.	2013-01-04 23:32:46 +01:00
Matt T. Proud	2922def8d0	Use the `TargetManager` for targets.	2013-01-04 17:17:23 +01:00
Julius Volz	45a3e0a182	Rename Target Frequency -> Interval.	2013-01-04 13:03:32 +01:00
Matt T. Proud	7a9777b4b5	Create `TargetPool` priority queue. ... ``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.	2013-01-04 12:17:31 +01:00

Renamed from retrieval/type.go (Browse further)