23 Commits (cc0ff26f1fe8048de70d8b5d625e6b306c837c5c)

Author	SHA1	Message	Date
Fabian Reinartz	311e7b5069	storage/vendor: update to latest fabxc/tsdb	8 years ago
Fabian Reinartz	157e698958	web/api: fix min/max timestamps to valid range	8 years ago
Fabian Reinartz	fecf9532b9	*: fix misc compile errors	8 years ago
Fabian Reinartz	5817cb5bde	*: migrate from model.* to promql.* types	8 years ago
Fabian Reinartz	09666e2e2a	promql: make scalar public	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
beorn7	094a098ce6	Revert "Revert the /graph changes." ... This reverts commit aa43d34a86. This brings back the /graph changes so that @grandbora can continue to work on the redirect for backwards compatibility. And other changes can already take the new /graph parameters into account.	8 years ago
beorn7	aa43d34a86	Revert the /graph changes. ... This revert will be reverted once v1.1 is released and has its own release branch. Since we had already change on top of this, there was no cleaner way of cutting those changes out. This commit reverts the following commits: Revert "Update backend helpers and templates to new url schema" This reverts commit fc6cdd0611. Revert "Refactor graph.js" This reverts commit 445fac56e0. Revert "Use query parameters in the url" This reverts commit 3e18d86d8a. Revert "Point to correct place for GraphLinkForExpression" This reverts commit 3da825fc76. Assets are also updated.	8 years ago
Dmitry Ulianov	a8619111f3	Added toUpper and toLower formatting to templates	8 years ago
Bora Tunca	fc6cdd0611	Update backend helpers and templates to new url schema	8 years ago
beorn7	4b574e8a61	Switch chunk encoding to type 2 where it was hardcoded type 1 before ... The chunk encoding was hardcoded there because it mostly doesn't matter what encoding is chosen in that test. Since type 1 is battle-hardened enough, I'm switching to type 2 here so that we can catch unexpected problems as a byproduct. My expectation is that the chunk encoding doesn't matter anyway, as said, but then "unexpected problems" contains the word "unexpected".	9 years ago
Brian Brazil	738af32057	template: Use zero-values for missing values. ... Currently missing values will get the value <no value> rather than the empty string. Using the empty string is more consistent, and should be easier for users to deal with too.	9 years ago
Julius Volz	af513468eb	Fix some dead code, missing error checks, shadowings. ... I applied https://medium.com/@jgautheron/quality-pipeline-for-go-projects-497e34d6567 and was greeted with a deluge of warnings, most of which were not applicable or really fixable realistically. These are some of the first ones I decided to fix.	9 years ago
Julius Volz	995d3b831d	Fix most golint warnings. ... This is with `golint -min_confidence=0.5`. I left several lint warnings untouched because they were either incorrect or I felt it was better not to change them at the moment.	9 years ago
Fabian Reinartz	d6b8da8d43	Switch promql types to common/model	9 years ago
Fabian Reinartz	306e8468a0	Switch from client_golang/model to common/model	9 years ago
Julius Volz	bbc8b8490e	Switch human-readable times to UTC. ... This fixes https://github.com/prometheus/prometheus/issues/829	10 years ago
Julius Volz	d868264bb8	Improve UI of /alerts page. ... Changes to the UI: - "Active Since" timestamps are now human-readable. - Alerting rules are now pretty-printed better. - Labels are no longer just strings, but alert bubbles (like we do on the status page for base labels). - Alert states and target health states are now capitalized in the presentation layer rather than at the source.	10 years ago
Fabian Reinartz	fe301d7946	promql: remove global flags	10 years ago
Fabian Reinartz	0de6edbdfc	Move pkg/ to util/	10 years ago
Fabian Reinartz	dbc0d30e3e	Move string functionality to pkg/strutil	10 years ago
Fabian Reinartz	f45a5cab60	Move templates package to pkg/template	10 years ago