159 Commits (eb651233ac7b831675620a865a2055c4c8810900)

Author	SHA1	Message	Date
Matt T. Proud	88d15373c5	Upgrade Prometheus to new API.	12 years ago
Julius Volz	80cdb0121d	Add support for configured job base labels.	12 years ago
Matt T. Proud	9752f1e61d	Refactor Target as interface for testability. ... Future tests around the ``TargetPool`` and ``TargetManager`` and friends will be a lot easier when the concrete behaviors of ``Target`` can be extracted out. Plus, each ``Target``, I suspect, will have its own resolution and query strategy.	12 years ago
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.	12 years ago
Julius Volz	56384bf42a	Add initial config and rule language implementation.	12 years ago
Matt T. Proud	52f52a7ee2	Include nascent instrumentation of stack.	12 years ago
Matt T. Proud	2922def8d0	Use the ``TargetManager`` for targets.	12 years ago
Julius Volz	45a3e0a182	Rename Target Frequency -> Interval.	12 years ago
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.	12 years ago