382 Commits (690de487e2fb0be3e3a41121bbe2b9ac3e7a844c)

Author	SHA1	Message	Date
Anders Daljord Morken	5c025a2f41	query_range: Validate that start comes before end	8 years ago
Fabian Reinartz	8fa18d564a	storage: enhance Querier interface usage ... This extracts Querier as an instantiateable and closeable object rather than just defining extending methods of the storage interface. This improves composability and allows abstracting query transactions, which can be useful for transaction-level caches, consistent data views, and encapsulating teardown.	8 years ago
Julius Volz	f92532f254	api: Consolidate web API contexts ... This is based on the common/route changes in https://github.com/prometheus/common/pull/61.	8 years ago
Julius Volz	c187308366	storage: Contextify storage interfaces. ... This is based on https://github.com/prometheus/prometheus/pull/1997. This adds contexts to the relevant Storage methods and already passes PromQL's new per-query context into the storage's query methods. The immediate motivation supporting multi-tenancy in Frankenstein, but this could also be used by Prometheus's normal local storage to support cancellations and timeouts at some point.	8 years ago
Julius Volz	ed5a0f0abe	promql: Allow per-query contexts. ... For Weaveworks' Frankenstein, we need to support multitenancy. In Frankenstein, we initially solved this without modifying the promql package at all: we constructed a new promql.Engine for every query and injected a storage implementation into that engine which would be primed to only collect data for a given user. This is problematic to upstream, however. Prometheus assumes that there is only one engine: the query concurrency gate is part of the engine, and the engine contains one central cancellable context to shut down all queries. Also, creating a new engine for every query seems like overkill. Thus, we want to be able to pass per-query contexts into a single engine. This change gets rid of the promql.Engine's built-in base context and allows passing in a per-query context instead. Central cancellation of all queries is still possible by deriving all passed-in contexts from one central one, but this is now the responsibility of the caller. The central query context is now created in main() and passed into the relevant components (web handler / API, rule manager). In a next step, the per-query context would have to be passed to the storage implementation, so that the storage can implement multi-tenancy or other features based on the contextual information.	8 years ago
Anders Daljord Morken	e9885ecb94	Bugfix: Avoid divide-by-zero panic on query_range?step=0	8 years ago
Julius Volz	3bfec97d46	Make the storage interface higher-level. ... See discussion in https://groups.google.com/forum/#!topic/prometheus-developers/bkuGbVlvQ9g The main idea is that the user of a storage shouldn't have to deal with fingerprints anymore, and should not need to do an individual preload call for each metric. The storage interface needs to be made more high-level to not expose these details. This also makes it easier to reuse the same storage interface for remote storages later, as fewer roundtrips are required and the fingerprint concept doesn't work well across the network. NOTE: this deliberately gets rid of a small optimization in the old query Analyzer, where we dedupe instants and ranges for the same series. This should have a minor impact, as most queries do not have multiple selectors loading the same series (and at the same offset).	8 years ago
Julius Volz	0c1e7a5b00	Support time range in /api/v1/series endpoint. ... This adds optional "start" and "end" form values that may be used to restrict the time range of returned series. Fixes https://github.com/prometheus/prometheus/issues/1542	9 years ago
Jonathan Boulle	38098f8c95	Add missing license headers ... Prometheus is Apache 2 licensed, and most source files have the appropriate copyright license header, but some were missing it without apparent reason. Correct that by adding it.	9 years ago
beorn7	836f1db04c	Improve MetricsForLabelMatchers ... WIP: This needs more tests. It now gets a from and through value, which it may opportunistically use to optimize the retrieval. With possible future range indices, this could be used in a very efficient way. This change merely applies some easy checks, which should nevertheless solve the use case of heavy rule evaluations on servers with a lot of series churn. Idea is the following: - Only archive series that are at least as old as the headChunkTimeout (which was already extremely unlikely to happen). - Then maintain a high watermark for the last archival, i.e. no archived series has a sample more recent than that watermark. - Any query that doesn't reach to a time before that watermark doesn't have to touch the archive index at all. (A production server at Soundcloud with the aforementioned series churn and heavy rule evaluations spends 50% of its CPU time in archive index lookups. Since rule evaluations usually only touch very recent values, most of those lookup should disappear with this change.) - Federation with a very broad label matcher will profit from this, too. As a byproduct, the un-needed MetricForFingerprint method was removed from the Storage interface.	9 years ago
beorn7	a7408bfb47	Unify duration parsing ... It's actually happening in several places (and for flags, we use the standard Go time.Duration...). This at least reduces all our home-grown parsing to one place (in model).	9 years ago
Julius Volz	1ae23bf5e9	Handle OPTIONS HTTP requests correctly. ... Fixes https://github.com/prometheus/prometheus/issues/1346	9 years ago
Tobias Schmidt	7a6a0630d1	Merge pull request #1213 from prometheus/fix-wrong-http-status-codes ... Return HTTP server error codes for execution errors	9 years ago
Tobias Schmidt	bf84faa010	Return HTTP server error codes for execution errors	9 years ago
Tobias Schmidt	50079a85a1	Make time parameter optional in v1 query API ... If no time paramter is provided, the current server timestamp is used.	9 years ago
Fabian Reinartz	33aab4169c	Anchor regexes in vector matching ... This commit makes the regex behavior of vector matching consistent with configuration and label_replace() by anchoring it. Fixes #1200	9 years ago
Fabian Reinartz	398bbf906b	Switch to common/route package	9 years ago
Fabian Reinartz	171f50706a	Fix unkeyed field errors.	9 years ago
Fabian Reinartz	f8a25f6af7	Apply HTTP handler compression everywhere	9 years ago
Fabian Reinartz	d6b8da8d43	Switch promql types to common/model	9 years ago
Fabian Reinartz	1535ef1457	Replace metric.SamplePair with model.SamplePair	9 years ago
Fabian Reinartz	438e232c9b	Fix grouping of import blocks	9 years ago
Fabian Reinartz	306e8468a0	Switch from client_golang/model to common/model	9 years ago
Fabian Reinartz	8f904d6a54	api/v1: fix response format tests	10 years ago
Fabian Reinartz	b36fa7ad61	api/v1: fix Content-Type in response	10 years ago
Julius Volz	bc1c789bab	Disallow cross-origin DELETE and POST requests.	10 years ago
Fabian Reinartz	5b91ea9b36	storage: improve label matching and allow unset matching. ... Matching of empty labels now also matches metrics where the label was not explicitly set to the empty string.	10 years ago
Fabian Reinartz	94cd321be1	promql: error if all label matchers are empty.	10 years ago
Fabian Reinartz	7bb7e565a4	web/api: add GET and DELETE /series endpoints	10 years ago
Fabian Reinartz	7be94ce962	web/api: improve errors, add tests	10 years ago
Fabian Reinartz	75b0b7420e	web/api: replace /metrics/names with /label/:name/values endpoint.	10 years ago
Fabian Reinartz	ab9c98acac	web/api: add initial API v1 implementation.	10 years ago