105 Commits (2bc12fa2fb1ebf50f3c016b22ffa94deaeed65b9)

Author	SHA1	Message	Date
Fabian Reinartz	b24602f713	kubernetes: merge back into single configuration	9 years ago
Fabian Reinartz	2331701b50	kubernetes: Add K8S v2 pod discovery ... This adds plumbing for a parallel version of the new K8S SD and adds pod discovery as the first role.	9 years ago
bekbulatov	01b53c1180	Add tls support	9 years ago
Ingo Gottwald	3b546d061f	Add support for GCE discovery	9 years ago
Fabian Reinartz	692ddc592c	retrieval: fix IPv6 port default, add tests ... This fixes port defaulting for IPv6 addresses and restructures and test the construction of target label sets.	10 years ago
Fabian Reinartz	17cdd4f966	retrieval: fix IPv6 port default, add tests ... This fixes port defaulting for IPv6 addresses and restructures and test the construction of target label sets.	10 years ago
beorn7	e2b3626e0c	retrieval: Clean up target group map on config reload ... Also, remove unused `providers` field in targetSet. If the config file changes, we recreate all providers (by calling `providersFromConfig`) and retrieve all targets anew from the newly created providers. From that perspective, it cannot harm to clean up the target group map in the targetSet. Not doing so (as it was the case so far) keeps stale targets around. This mattered if an existing key in the target group map was not overwritten in the initial fetch of all targets from the providers. Examples where that mattered: ``` scrape_configs: - job_name: "foo" static_configs: - targets: ["foo:9090"] - targets: ["bar:9090"] ``` updated to: ``` scrape_configs: - job_name: "foo" static_configs: - targets: ["foo:9090"] ``` `bar:9090` would still be monitored. (The static provider just enumerates the target groups. If the number of target groups decreases, the old ones stay around. ``` scrape_configs: - job_name: "foo" dns_sd_configs: - names: - "srv.name.one.example.org" ``` updated to: ``` scrape_configs: - job_name: "foo" dns_sd_configs: - names: - "srv.name.two.example.org" ``` Now both SRV records are still monitored. The SRV name is part of the key in the target group map, thus the new one is just added and the old ane stays around. Obviously, this should have tests, and should have tests before, not only for this case. This is the quick fix. I have created https://github.com/prometheus/prometheus/issues/1906 to track test creation. Fixes https://github.com/prometheus/prometheus/issues/1610 .	10 years ago
Frederic Branczyk	7714b9c781	move relabeling functionality to its own package ... also remove the returned error as it was always nil	10 years ago
Dmitry Vorobev	273e457da4	web: return status code and error message for config resource	10 years ago
Fabian Reinartz	4c864c8a88	retrieval: don't sync to uninitialized scrape pool ... This change does just signal a scrape target update to the scraping loop once an initial target set is fetched. Before, the scrape pool was directly synced, causing a race against an uninitialized scrape pool. Fixes #1703	10 years ago
Fabian Reinartz	d0eeae9d0e	retrieval: don't sync to uninitialized scrape pool ... This change does just signal a scrape target update to the scraping loop once an initial target set is fetched. Before, the scrape pool was directly synced, causing a race against an uninitialized scrape pool. Fixes #1703	10 years ago
Fabian Reinartz	0f21bd31ca	config: deprecate `target_groups` for `static_configs` ... This change deprecates the `target_groups` option in favor of `static_configs`. The old configuration is still accepted but prints a warning. Configuration loading errors if both options are set.	10 years ago
Fabian Reinartz	4e087165aa	retrieval: handle nil target groups from updates	10 years ago
Fabian Reinartz	8fe8ccce63	retrieval: document panic behavior	10 years ago
Fabian Reinartz	021ef27fe3	retrieval: don't panic on non-HTTP scheme	10 years ago
Fabian Reinartz	12b03db373	retrieval: handle nil target groups from updates	10 years ago
Fabian Reinartz	ea36efbbd1	retrieval: document panic behavior	10 years ago
Fabian Reinartz	a5ba166935	retrieval: don't panic on non-HTTP scheme	10 years ago
stuart nelson	d02591814b	discovery/dns: move dns to own package	10 years ago
Fabian Reinartz	9f8feb9ff6	discovery: consolidate Marathon SD files	10 years ago
Fabian Reinartz	5837e6a97f	discovery: move consul SD into own package	10 years ago
Seth Miller	0988e3b937	Add support for Azure discovery ... This change adds the ability to do target discovery with Microsoft's Azure platform.	10 years ago
Fabian Reinartz	769389e559	Fix potential race in ctx intialization	10 years ago
Fabian Reinartz	f2e359962c	Sort exported targets	10 years ago
Fabian Reinartz	56fc9bdff3	Handle closed target provider channel ... This fixes the case where a target provider closes the update channel and exits before the context is canceled. This should only be true for the static provider but it's safer to generally handle this case.	10 years ago
Fabian Reinartz	2060a0a15b	Turn target group members into plain lists. ... As the scrape pool deduplicates targets now, it is no longer necessary to store a hash map for members of each group.	10 years ago
Fabian Reinartz	0d7105abee	Remove scrape config from Target. ... This commit removes the scrapeConfig entirely from Target. All identity defining parameters are thus immutable now and the mutex can be removed.. Target identity is now correctly defined by the labels and the full URL. This in particular includes URL parameters that are not specified in the label set. Fingerprint is also removed from hash to remove an unnecessary tight coupling to the common/model package.	10 years ago
Fabian Reinartz	75681b691a	Extract HTTP client from Target. ... The HTTP client is the same across all targets with the same scrape configuration. Thus, this commit moves it into the scrape pool.	10 years ago
Fabian Reinartz	76a8c6160d	Deduplicate targets in scrape pool. ... With this commit the scrape pool deduplicates incoming targets before scraping them. This way multiple target providers can produce the same target but it will be scraped only once.	10 years ago
Fabian Reinartz	84f74b9a84	Apply new scrape config on reload. ... This commit updates a target set's scrape configuration on reload. This will cause all running scrape loops to be stopped and started again with new parameters.	10 years ago
Fabian Reinartz	775316f8d2	Move appender construction from Target to scrapePool	10 years ago
Fabian Reinartz	05de8b7f8d	Extract target scraping into scrape loop. ... This commit factors out the scrape loop handling into its own data structure. For the transition it will be directly attached to the target.	10 years ago
Fabian Reinartz	cebba3efbb	Simplify and fix TargetManager reloading	10 years ago
Fabian Reinartz	d15adfc917	Preserve target state across reloads. ... This commit moves Scraper handling into a separate scrapePool type. TargetSets only manage TargetProvider lifecycles and sync the retrieved updates to the scrapePool. TargetProviders are now expected to send a full initial target set within 5 seconds. The scrapePools preserve target state across reloads and only drop targets after the initial set was synced.	10 years ago
Fabian Reinartz	5b30bdb610	Change TargetProvider interface. ... This commit changes the TargetProvider interface to use a context.Context and send lists of TargetGroups, rather than single ones.	10 years ago
Fabian Reinartz	5bfa4cdd46	Simplify target update handling. ... We group providers by their scrape configuration. Each provider produces target groups with an unique identifier. On stopping a set of target providers we cancel the target providers, stop scraping the targets and wait for the scrapers to finish. On configuration reload all provider sets are stopped and new ones are created. This will make targets disappear briefly on configuration reload. Potentially scrapes are missed but due to the consistent scrape intervals implemented recently, the impact is minor.	10 years ago
Fabian Reinartz	6df1f49c13	Remove fullLabels method and fix target updating ... With recent changes to a Target's internal data representation updating by fullLabels() assigns the additional default instance label. This breaks target identity comparison and causes identical targets from service discovery to be constantly swapped.	10 years ago
Fabian Reinartz	825831e98f	Use fingerprint for target identity comparison ... So far we were using the InstanceIdentifier to compare equality of targets. This is not always accurate, for example for the blackbox exporter where the actual target is in the parameter.	10 years ago
Fabian Reinartz	a06bc75519	Remove occurrences of 'base' labels	10 years ago
Julius Volz	3728b5872f	Fix target update error handling. ... Fixes https://github.com/prometheus/prometheus/issues/1378	10 years ago
beorn7	ec08c9a391	Rework the way to communicate backpressure (AKA suspended ingestion) ... This gives up on the idea to communicate throuh the Append() call (by either not returning as it is now or returning an error as suggested/explored elsewhere). Here I have added a Throttled() call, which has the advantage that it can be called before a whole _batch_ of Append()'s. Scrapes will happen completely or not at all. Same for rule group evaluations. That's a highly desired behavior (as discussed elsewhere). The code is even simpler now as the whole ingestion buffer could be removed. Logging of throttled mode has been streamlined and will create at most one message per minute.	10 years ago
Julien Dehee	061fe2f364	Support AirBnB's Smartstack Nerve client for SD ... nerve's registration format differs from serverset. With this commit there is now a dedicated treecache file in util, and two separate files for serverset and nerve. Reference: https://github.com/airbnb/nerve	10 years ago
Fabian Reinartz	29a69eecb8	Do not panic in Consul SD creation	10 years ago
Brian Brazil	427bf29db1	Add in default port after relabelling. ... For the SNMP and blackbox exporters where the ports tends to not be 80/443 and indeed there may not be a port this makes the relabelling a bit simpler as you don't have to figure out this logic exists and strip off the :80. This is a breaking change for the example configs of those exporters.	10 years ago
Brian Brazil	fd2bd81cd8	Allow all instance labels in target groups ... With the blackbox exporter, the instance label will commonly be used for things other than hostnames so remove this restriction. https://example.com or https://example.com/probe/me are some examples. To prevent user error, check that urls aren't provided as targets when there's no relabelling that could potentically fix them.	10 years ago
Julius Volz	d88aea7e6f	Fix SD mechanism source prefix handling. ... The prefixed target provider changed a pointerized target group that was reused in the wrapped target provider, causing an ever-increasing chain of source prefixes in target groups from the Consul target provider. We now make this bug generally impossible by switching the target group channel from pointer to value type and thus ensuring that target groups are copied before being passed on to other parts of the system. I tried to not let the depointerization leak too far outside of the channel handling (both upstream and downstream) because I tried that initially and caused some nasty bugs, which I want to minimize. Fixes https://github.com/prometheus/prometheus/issues/1083	10 years ago
Matt Jibson	dcb4856d72	Add SD for Amazon EC2 instances	10 years ago
Fabian Reinartz	e3b6ec9784	Switch to common/log	10 years ago
Julius Volz	99e8fff872	Fix target manager CPU busyloop caused by bad done-channel handling. ... Unfortunately this isn't nicely testable, as it's timing-dependent and one would have to detect a stray goroutine doing a CPU busyloop... Fixes https://github.com/prometheus/prometheus/issues/1114	10 years ago
Fabian Reinartz	cc1a2a2061	Remove attachment of global labels upon ingestion	11 years ago