prometheus

Commit Graph

Author	SHA1	Message	Date
Julius Volz	d9b4f98b44	Integrate DNS-SD support for discovering job targets.	12 years ago
Matt T. Proud	d4db3cf00b	Code Review: Last replacement wins.	12 years ago
Matt T. Proud	9cde48754b	Fix race conditions in TargetPool. The race condition detector found a few anomalies whereby a TargetPool could be read during a mutation. This has been fixed.	12 years ago
Matt T. Proud	8f4c7ece92	Destroy naked returns in half of corpus. The use of naked return values is frowned upon. This is the first of two bulk updates to remove them.	12 years ago
Julius Volz	f1fc7d717a	Allow replacing job targets via HTTP API. This roughly comprises the following changes: - index target pools by job instead of scrape interval - make targets within a pool exchangable while preserving existing health state for targets - allow exchanging targets via HTTP API (PUT) - show target lists in /status (experimental, for own debug use)	12 years ago
Julius Volz	3537edee9f	Fix targetpool iteration deadlock.	12 years ago
Matt T. Proud	e01b6cdb44	Duration statistics for each target pool. We have an open question of how long does it take for each target pool to have the state retrieved from all participating elements. This commit starts by providing insight into this.	12 years ago
Matt T. Proud	ea54751431	Update import paths to new location. This repository moved from matttproud/prometheus to prometheus/prometheus, and all import paths need to be updated.	12 years ago
Matt T. Proud	f2ded515b7	Support versioned telemetry providers. client_golang was updated to support full label-oriented telemetry, which introduced interface incompatibilities with the previous version of Prometheus. To alleviate this, a general fetching and processing dispatching system has been created, which discriminates and processes according to the version of input.	12 years ago
Matt T. Proud	190e4e3fa3	``TargetManager`` and ``TargetPool`` ass pointers.	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
Matt T. Proud	2922def8d0	Use the ``TargetManager`` for targets.	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

14 Commits (22a40c298d5a89515ad8f43ff5297c13505ed46f)