147 Commits (5aa3d8260a7335a0da6946dea82f608cafa46c20)

Author	SHA1	Message	Date
Fabian Reinartz	7ccd4b39b8	*: implement query params ... This adds a parameter to the storage selection interface which allows query engine(s) to pass information about the operations surrounding a data selection. This can for example be used by remote storage backends to infer the correct downsampling aggregates that need to be provided.	8 years ago
Brian Brazil	0a42a9fc8f	Copy over rule group duration on reload. ... This is currently getting lost, this will soon be in a metric and we don't want it dropping to 0 on every reload.	8 years ago
Fabian Reinartz	62461379b7	rules: decouple notifier packages ... The dependency on the notifier packages caused a transitive dependency on discovery and with that all client libraries our service discovery uses.	8 years ago
Fabian Reinartz	bd9f7460eb	rules: remove config package dependency	8 years ago
Fabian Reinartz	2d0e3746ac	rules: remove dependency on promql.Engine	8 years ago
Fabian Reinartz	83cd270ea4	*: adapt to storage interface changes	8 years ago
Jorge Hernández	6cd0f63eb1	Use testutil in rules subpackage (#3278) ... * Use testutil in rules subpackage * Fix manager test * Use testutil in rules subpackage * Fix manager test * Fix rebase * Change to testutil for applyConfig tests	8 years ago
Krasi Georgiev	e86d82ad2d	Fix regression of alert rules state loss on config reload. (#3382) ... * incorrect map name for the group prevented copying state from existing alert rules on config reload * applyConfig test * few nits * nits 2	8 years ago
Brian Brazil	cc5499fcad	Only close after checking for err.	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
Fabian Reinartz	d21f149745	*: migrate to go-kit/log	8 years ago
Goutham Veeramachaneni	507790a357	Rework logging to use explicitly passed logger ... Mostly cleaned up the global logger use. Still some uses in discovery package. Signed-off-by: Goutham Veeramachaneni <cs14btech11014@iith.ac.in>	9 years ago
Goutham Veeramachaneni	8cca666cf2	Add file name to group. ... Signed-off-by: Goutham Veeramachaneni <cs14btech11014@iith.ac.in>	9 years ago
Brian Brazil	dcea3e4773	Don't append a 0 when alert is no longer pending/firing ... With staleness we no longer need this behaviour.	9 years ago
Brian Brazil	cc867dae60	Copy previous series and alert state more intelligently. ... Usually rules don't more around, and if they do it's likely that rules/alerts with the same name stay in the same order. If rules/alerts with the same name are added/removed this could cause a blip for one cycle, but this is unavoidable without requiring rule and alert names to be unique - which we don't want to do.	9 years ago
Brian Brazil	0451d6d31b	Add unittest for rule staleness, and rules generally.	9 years ago
Julius Volz	ac203ef0ee	Add externalURL template function (#2716) ... This allows users to e.g. add links back to the generating Prometheus right in their alert templates.	9 years ago
Fabian Reinartz	e94b0899ee	rules: fix tests, remove model types	9 years ago
Jonathan Lange	2a2da40223	Make rule evaluation publicly available ... Means that a third-party can parse rules and run them with their own execution model.	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
Brian Brazil	6fc88d4b4d	Remove __name__ from alerts sent to AM. ... Fixes #1861	10 years ago
Brian Brazil	0509b0f2db	Expand alert templates at eval time. ... Fixes #1678 #1677	10 years ago
Tobias Schmidt	f1f8317fa5	Fix detection of flapping alerts ... Alerts in the resolve retention period must be transitioned to the active state again when their condition is met.	10 years ago
Fabian Reinartz	62075aa037	Reduce noisy no-alertmanager warning	10 years ago
Fabian Reinartz	52e5224f5a	Refactor rules/ package	10 years ago
Fabian Reinartz	7c90db22ed	Use annotation based alerts in rules/ ... This commit breaks the previously used alert format.	10 years ago
Fabian Reinartz	306e8468a0	Switch from client_golang/model to common/model	10 years ago
Fabian Reinartz	f06cf664e1	rules: cleanup alerting test	11 years ago
Fabian Reinartz	4625485b84	rules: move rules*.go contents to manager*.go	11 years ago
Fabian Reinartz	749ae450c5	promql: add runbook to alert statement. ... This commit adds the RUNBOOK keyword to alert statements. The field is optional and expected to be a link.	11 years ago
Fabian Reinartz	fe301d7946	promql: remove global flags	11 years ago
Fabian Reinartz	5e13880201	General cleanup of rules.	11 years ago
Fabian Reinartz	25cdff3527	Remove `name` arg from `Parse*` functions, enhance parsing errors.	11 years ago
Fabian Reinartz	3ca11bcaf5	Switch Prometheus to promql package. ... This commit removes all functionality from rules/ that is now handled in promql/. All parts of Prometheus are changed to use the promql/ package.	11 years ago
Brian Brazil	6c1689f0c6	Sort NaN as the lowest value. ... Currently it ends up in a random position.	11 years ago
Brian Brazil	c3a2b63fe9	Add stddev and stdvar aggregation functions. ... This adds the population standard deviation and variance as aggregation functions, useful for spotting how many standard deviations some samples are from the mean.	11 years ago
Brian Brazil	74aed55e55	Add square root function	11 years ago
Fabian Reinartz	624f27f4b6	Add ln, log2, log10 and exp functions to the query language.	11 years ago
Julius Volz	b2651027fc	Fix special value handling in division and modulo. ... This fixes https://github.com/prometheus/prometheus/issues/597	11 years ago
beorn7	13fcf1ddbc	Implement double-delta encoded chunks.	11 years ago
Fabian Reinartz	182de6b99f	Fix unary +/- expressions. ... Unary expressions cause parsing errors if they are done in the lexer by tokenizing them into the number. This fix moves unary expressions to the parser.	11 years ago
Fabian Reinartz	6f754073d5	Add OR operation and vector matching options. ... This commits implements the OR operation between two vectors. Vector matching using the ON clause is added to limit the set of labels that define a match between two elements. Group modifiers (GROUP_LEFT/GROUP_RIGHT) to request many-to-one matching are added.	11 years ago
Julius Volz	0ac931aed1	Also support parsing float formats like "2.".	11 years ago
Julius Volz	c2ab54e9a6	Support scientific notation and special float values. ... This adds support for scientific notation in the expression language, as well as for all possible literal forms of +Inf/-Inf/NaN. TODO: Keep enough state in the parser/lexer to distinguish contexts in which "Inf", "NaN", etc. should be parsed as a number vs. parsed as a label name. Currently, foo{nan="bar"} would be a syntax error. However, that is an existing bug for all our reserved words. E.g. foo{sum="bar"} is a syntax error as well. This should be fixed separately.	11 years ago
beorn7	9e7c3e3bcd	Add the histogram_quantile function. ... Since we are now getting really deep into floating point calculation, the tests had to take into account the precision loss. Since the rule tests are based on direct line matching in the output, implementing the "almost equal" semantics was pretty cumbersome, but here we are.	11 years ago
Julius Volz	42601acfde	Replace labelsToKey() with metric Fingerprint (fixes grouping bug).	11 years ago
Julius Volz	645cf57bed	Fix aggregation grouping key calculation.	11 years ago
Julius Volz	15b2b5aa66	Add tests for invalid uses of "offset".	11 years ago
Julius Volz	72d7b325a1	Implement offset operator. ... This allows changing the time offset for individual instant and range vectors in a query. For example, this returns the value of `foo` 5 minutes in the past relative to the current query evaluation time: foo offset 5m Note that the `offset` modifier always needs to follow the selector immediately. I.e. the following would be correct: sum(foo offset 5m) // GOOD. While the following would be *incorrect*: sum(foo) offset 5m // INVALID. The same works for range vectors. This returns the 5-minutes-rate that `foo` had a week ago: rate(foo[5m] offset 1w) This change touches the following components: * Lexer/parser: additions to correctly parse the new `offset`/`OFFSET` keyword. * AST: vector and matrix nodes now have an additional `offset` field. This is used during their evaluation to adjust query and result times appropriately. * Query analyzer: now works on separate sets of ranges and instants per offset. Isolating different offsets from each other completely in this way keeps the preloading code relatively simple. No storage engine changes were needed by this change. The rules tests have been changed to not probe the internal implementation details of the query analyzer anymore (how many instants and ranges have been preloaded). This would also become too cumbersome to test with the new model, and measuring the result of the query should be sufficient. This fixes https://github.com/prometheus/prometheus/issues/529 This fixed https://github.com/prometheus/promdash/issues/201	11 years ago