prometheus

Commit Graph

Author	SHA1	Message	Date
David Kaltschmidt	c93e54d240	Adds execution timer stats to the range query API consumers should be able to get insight into the query run times. The UI currently measures total roundtrip times. This PR allows for more fine grained metrics to be exposed. * adds new timer for total execution time (queue + eval) * expose new timer, queue timer, and eval timer in stats field of the range query response: ```json { "status": "success", "data": { "resultType": "matrix", "result": [], "stats": { "execQueueTimeNs": 4683, "execTotalTimeNs": 2086587, "totalEvalTimeNs": 2077851 } } } ``` * stats field is optional, only set when query parameter `stats` is not empty Try it via ```sh curl 'http://localhost:9090/api/v1/query_range?query=up&start=1486480279&end=1486483879&step=14000&stats=true' ``` Review feedback * moved query stats json generation to query_stats.go * use seconds for all query timers * expose all timers available * Changed ExecTotalTime string representation from Exec queue total time to Exec total time	8 years ago
Alexey Miroshkin	8c681f4a6c	Provide POST endpoint for query+query_range (#3322 ) This PR fixes #3072 by providing POST endpoints for `query` and `query_range`. POST request must be made with `Content-Type: application/x-www-form-urlencoded` header.	8 years ago
Tom Wilkie	746752b946	Merge external labels in order.	8 years ago
Tom Wilkie	ee011d906d	Port remote read server to 2.0.	8 years ago
Julius Volz	099df0c5f0	Migrate "golang.org/x/net/context" -> "context" (#3333 ) In some places, where ctxhttp or gRPC are concerned, we still need to use the old contexts.	8 years ago
Brian Brazil	3a7c51ab70	Remote read endpoint should handle matchers for external labels. (#3325 ) If the other Prometheus has an external label that matches that of the Prometheus being read from, then we need to remove that matcher from the request as it's not actually stored in the database - it's only added for alerts, federation and on the output of the remote read endpoint. Instead we check for that label being empty, in case there is a time series with a different label value for that external label.	8 years ago
Brian Brazil	c25f7c600b	Apply external labels to remote read endpoint (#3263 ) Fixes #3261	8 years ago
beorn7	f20e6a0ae4	Only respond to API requests once the server is ready	8 years ago
Julius Volz	f7e8348a88	Re-add contexts to storage.Storage.Querier() (#3230 ) * Re-add contexts to storage.Storage.Querier() These are needed when replacing the storage by a multi-tenant implementation where the tenant is stored in the context. The 1.x query interfaces already had contexts, but they got lost in 2.x. * Convert promql.Engine to use native contexts	8 years ago
Tom Wilkie	758d64ffd9	s/EncodReadResponse/EncodeReadResponse/	8 years ago
Tom Wilkie	febed48703	Implement remote read server in Prometheus.	8 years ago
Max Leonard Inden	1c96fbb992	Expose current Prometheus config via /status/config This PR adds the `/status/config` endpoint which exposes the currently loaded Prometheus config. This is the same config that is displayed on `/config` in the UI in YAML format. The response payload looks like such: ``` { "status": "success", "data": { "yaml": <CONFIG> } } ```	8 years ago
Fabian Reinartz	ccf9e62972	*: add admin grpc API	8 years ago
Tom Wilkie	4d9b917d11	Instrument Prometheus with OpenTracing (#2554 ) * Use request.Context() instead of a global map of contexts. * Add some basic opentracing instrumentation on the query path. * Remove tracehandler endpoint.	8 years ago
David Symonds	04ad889751	Preserve Alertmanager URLs as *url.URL. Render a nicer link in the web UI.	8 years ago
Tom Wilkie	f0e8a5f37c	Add promql.ErrStorage, which is interpreted by the API as a 500.	8 years ago
Fabian Reinartz	bbcf20ba01	web: deduplicate series in federation	8 years ago
Fabian Reinartz	f56644e3ae	api/v1: deduplicate selected series	8 years ago
Bplotka	1823ae8bc4	Fixed int64 overflow for timestamp in v1/api parseDuration and parseTime (#2501 ) * Fixed int64 overflow for timestamp in v1/api parseDuration and parseTime This led to unexpected results on wrong query with "(...)&start=148966367200.372&end=1489667272.372" That query is wrong because of `start > end` but actually internal int64 overflow caused start to be something around MinInt64 (huge negative value) and was passing validation. BTW: Not sure if negative timestamp makes sense even.. But model.Earliest is actually MinInt64, can someone explain me why? Signed-off-by: Bartek Plotka <bwplotka@gmail.com> * Added missing trailing periods on comments. Signed-off-by: Bartek Plotka <bwplotka@gmail.com> * MOved to only `<` and `>`. Removed equal. Signed-off-by: Bartek Plotka <bwplotka@gmail.com>	8 years ago
Goutham Veeramachaneni	4b0270290b	Fix comments to match convention	8 years ago
Goutham Veeramachaneni	c6b329c55b	Support Custom Timeouts for Queries	8 years ago
Goutham Veeramachaneni	6634984a38	Comments and Typo Fixes	8 years ago
Fabian Reinartz	d80a3de235	pkg/textparse: add documentation	9 years ago
Fabian Reinartz	157e698958	web/api: fix min/max timestamps to valid range	9 years ago
Frederic Branczyk	bd92571bdd	web/api: make target and alertmanager api responses consistent	9 years ago
Frederic Branczyk	389c6d0043	web/api: add alertmanager api	9 years ago
beorn7	767c0709b1	Retrieval: Avoid copying Target retreival.Target contains a mutex. It was copied in the Targets() call. This potentially can wreak a lot of havoc. It might even have caused the issues reported as #2266 and #2262 .	9 years ago
Fabian Reinartz	bc20d93f0a	storage: rename iterator value getters to At()	9 years ago
Fabian Reinartz	28f547bcc7	api/v1: fix tests, restore series queries	9 years ago
Fabian Reinartz	f8fc1f5bb2	*: migrate ingestion to new batch Appender	9 years ago
Fabian Reinartz	5817cb5bde	: migrate from model. to promql.* types	9 years ago
Frederic Branczyk	33b583d50e	web/api: add targets endpoint	9 years ago
Anders Daljord Morken	5c025a2f41	query_range: Validate that start comes before end	9 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.	9 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.	9 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.	9 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.	9 years ago
Anders Daljord Morken	e9885ecb94	Bugfix: Avoid divide-by-zero panic on query_range?step=0	9 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).	9 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).	10 years ago
Julius Volz	1ae23bf5e9	Handle OPTIONS HTTP requests correctly. Fixes https://github.com/prometheus/prometheus/issues/1346	10 years ago
Tobias Schmidt	bf84faa010	Return HTTP server error codes for execution errors	10 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.	10 years ago
Fabian Reinartz	398bbf906b	Switch to common/route package	10 years ago
Fabian Reinartz	171f50706a	Fix unkeyed field errors.	10 years ago
Fabian Reinartz	f8a25f6af7	Apply HTTP handler compression everywhere	10 years ago
Fabian Reinartz	d6b8da8d43	Switch promql types to common/model	10 years ago

1 2

65 Commits (c93e54d240db26595c230150cc082d086feebdb2)