prometheus

Commit Graph

Author	SHA1	Message	Date
beorn7	bea12d4be1	Merge branch 'release-1.7'	7 years ago
Björn Rabenstein	22eadbe635	Merge pull request #3222 from prometheus/beorn7/release Cut v1.7.2	7 years ago
Tobias Schmidt	e8ce37ad0d	Merge pull request #3223 from alcortesm/dead-code-at-stats util/stats: remove dead code	7 years ago
Tobias Schmidt	f104a5dfc6	Merge pull request #3224 from alcortesm/config-simplify-returns config: simplify some returns	7 years ago
Alberto Cortés	bb3dad9cba	config: simplify some returns	7 years ago
Alberto Cortés	2c9739162e	utils/stats: remove dead code	7 years ago
beorn7	f51c97c7d4	Cut v1.7.2	7 years ago
Björn Rabenstein	398fa4fd02	Merge pull request #3205 from prometheus/beorn7/ui Make all rule links link to the "Console" tab rather than "Graph"	7 years ago
beorn7	c2e9a151ab	Make all rule links link to the "Console" tab rather than "Graph" Clicking on a rule, either the name or the expression, opens the rule result (or the corresponding expression, repsectively) in the expression browser. This should by default happen in the console tab, as, more often than not, displaying it in the graph tab runs into a timeout.	7 years ago
beorn7	16c95ae8e7	Merge branch 'release-1.7'	7 years ago
beorn7	dd381356a5	Tweak floating point number rendering	7 years ago
beorn7	eaff0dcfc3	Merge branch 'yamatoya-fix_ui_graph_decimal_axis' into release-1.7	7 years ago
beorn7	61b6311504	Merge branch 'fix_ui_graph_decimal_axis' of git://github.com/yamatoya/prometheus into yamatoya-fix_ui_graph_decimal_axis	7 years ago
Takahito Yamatoya	b1151bdabc	ui changed, limit the number of digits for the larger units is 5	7 years ago
Takahito Yamatoya	1eac566d09	add ; , and change from B to G, and change from K to k, and add all the prefixes	7 years ago
Tom Wilkie	fae3bd17b9	Merge pull request #3132 from tomwilkie/fix-debug-handlers Get pprof handlers working again	7 years ago
Tom Wilkie	bbc9671d50	Get profile handlers working again after #3054 and #3146 . Ensures the pprod endpoints deal with path-prefixes correctly; adds a test so we don't break it again.	7 years ago
beorn7	e7aab2791a	Forward-merge bug fixes frem branch 'release-1.7'	7 years ago
beorn7	f6367afca4	Merge branch 'yamatoya-fix_web_ui_utc' into release-1.7	7 years ago
beorn7	7a8e340c1a	Merge branch 'fix_web_ui_utc' of git://github.com/yamatoya/prometheus into yamatoya-fix_web_ui_utc	7 years ago
Takahito Yamatoya	5d707d3aa3	#2439 library version update JQuery / JQuery.Selection / JQuery.hotkey (#3183 )	7 years ago
Takahito Yamatoya	ff038a4a39	bug fix	7 years ago
Takahito Yamatoya	7a3c348f83	fix decimal y-axis	7 years ago
Takahito Yamatoya	738a51bea6	#2371 fix to display utc date at datetime picker	7 years ago
beorn7	84211bd2df	Foward-merge bug fixes and cherry-picks from 'release-1.7'	7 years ago
Matt Palmer	3369422327	Improve DNS response handling to prevent "stuck" records [Fixes #2799 ] (#3138 ) The problem reported in #2799 was that in the event that all records for a name were removed, the target group was never updated to be the "empty" set. Essentially, whatever Prometheus last saw as a non-empty list of targets would stay that way forever (or at least until Prometheus restarted...). This came about because of a fairly naive interpretation of what a valid-looking DNS response actually looked like -- essentially, the only valid DNS responses were ones that had a non-empty record list. That's fine as long as your config always lists only target names which have non-empty record sets; if your environment happens to legitimately have empty record sets sometimes, all hell breaks loose (otherwise-cleanly shutdown systems trigger up==0 alerts, for instance). This patch is a refactoring of the DNS lookup behaviour that maintains existing behaviour with regard to search paths, but correctly handles empty and non-existent record sets. RFC1034 s4.3.1 says there's three ways a recursive DNS server can respond: 1. Here is your answer (possibly an empty answer, because of the way DNS considers all records for a name, regardless of type, when deciding whether the name exists). 2. There is no spoon (the name you asked for definitely does not exist). 3. I am a teapot (something has gone terribly wrong). Situations 1 and 2 are fine and dandy; whatever the answer is (empty or otherwise) is the list of targets. If something has gone wrong, then we shouldn't go updating the target list because we don't really know what the target list should be. Multiple DNS servers to query is a straightforward augmentation; if you get an error, then try the next server in the list, until you get an answer or run out servers to ask. Only if all the servers return errors should you return an error to the calling code. Where things get complicated is the search path. In order to be able to confidently say, "this name does not exist anywhere, you can remove all the targets for this name because it's definitely GORN", at least one server for all the possible names need to return either successful-but-empty responses, or NXDOMAIN. If any name errors out, then -- since that one might have been the one where the records came from -- you need to say "maintain the status quo until we get a known-good response". It is possible, though unlikely, that a poorly-configured DNS setup (say, one which had a domain in its search path for which all configured recursive resolvers respond with REFUSED) could result in the same "stuck" records problem we're solving here, but the DNS configuration should be fixed in that case, and there's nothing we can do in Prometheus itself to fix the problem. I've tested this patch on a local scratch instance in all the various ways I can think of: 1. Adding records (targets get scraped) 2. Adding records of a different type 3. Remove records of the requested type, leaving other type records intact (targets don't get scraped) 4. Remove all records for the name (targets don't get scraped) 5. Shutdown the resolver (targets still get scraped) There's no automated test suite additions, because there isn't a test suite for DNS discovery, and I was stretching my Go skills to the limit to make this happen; mock objects are beyond me.	7 years ago
Björn Rabenstein	4b8666b739	Merge pull request #3176 from prometheus/beorn7/release Backport the templating fix from master	7 years ago
beorn7	a3fd7dd335	Backport the templating fix from master The original fix is in commit `5f5d77848e`	7 years ago
Julius Volz	8ebeed0b44	remote: Expose ClientConfig type (#3165 ) The Client type is already exposed, but can't be used without the config for it also being exposed. Using the remote.Client from other programs is useful to do full end-to-end tests of Prometheus's remote protocol against adapter implementations.	7 years ago
Björn Rabenstein	df4bc3e407	Merge pull request #3170 from tomwilkie/1.7-2969-negative-shards Prevent number of remote write shards from going negative.	7 years ago
Tom Wilkie	f66f882d08	Merge pull request #3160 from bboreham/remote-keepalive Re-enable http keepalive on remote storage	7 years ago
Tom Wilkie	4f8efdbd59	Prevent number of remote write shards from going negative. This can happen in the situation where the system scales up the number of shards massively (to deal with some backlog), then scales it down again as the number of samples sent during the time period is less than the number received.	7 years ago
Ben Kochie	1ab0bbb2c2	Merge pull request #3125 from prometheus/bjk/staticcheck Enable statitcheck at build time.	7 years ago
Björn Rabenstein	4d8e7ca185	Merge pull request #3159 from mattbostock/1.7_marathon_sd_cherrypick Marathon SD: Set port index label	7 years ago
Matt Bostock	e758260986	Marathon SD: Set port index label The changes [1][] to Marathon service discovery to support multiple ports mean that Prometheus now attempts to scrape all ports belonging to a Marathon service. You can use port definition or port mapping labels to filter out which ports to scrape but that requires service owners to update their Marathon configuration. To allow for a smoother migration path, add a `__meta_marathon_port_index` label, whose value is set to the port's sequential index integer. For example, PORT0 has the value `0`, PORT1 has the value `1`, and so on. This allows you to support scraping both the first available port (the previous behaviour) in addition to ports with a `metrics` label. For example, here's the relabel configuration we might use with this patch: - action: keep source_labels: ['__meta_marathon_port_definition_label_metrics', '__meta_marathon_port_mapping_label_metrics', '__meta_marathon_port_index'] # Keep if port mapping or definition has a 'metrics' label with any # non-empty value, or if no 'metrics' port label exists but this is the # service's first available port regex: ([^;]+;;[^;]+\|;[^;]+;[^;]+\|;;0) This assumes that the Marathon API returns the ports in sorted order (matching PORT0, PORT1, etc), which it appears that it does. [1]: https://github.com/prometheus/prometheus/pull/2506	7 years ago
Bryan Boreham	9d6b945e41	Default HTTP keep-alive ON for remote read/write	7 years ago
Bryan Boreham	e0a4d18301	Allow http keep-alive setting to be overridden in config	7 years ago
Tobias Schmidt	8bee283f8a	Merge pull request #2895 from jamiemoore/ec2_discovery_rolearn Add the ability to assume a role for ec2 discovery	7 years ago
Jamie Moore	7a135e0a1b	Add the ability to assume a role for ec2 discovery	7 years ago
Fabian Reinartz	9b4c3d4254	Merge pull request #3146 from prometheus/fixprofpath web: fix profile paths	7 years ago
Fabian Reinartz	64c7c56df8	Merge pull request #3147 from dvrkps/patch-1 travis: add 1.x to go versions	7 years ago
Davor Kapsa	bb853abf24	travis: add 1.x to go versions	7 years ago
Fabian Reinartz	27bdddbf51	web: fix profile paths	7 years ago
Fabian Reinartz	6ab652e3dc	Merge pull request #3144 from wgliang/master should use time.Since instead of time.Now().Sub	7 years ago
Fabian Reinartz	a0280cc489	Merge pull request #3142 from prometheus/fish/fix-k8s-ingress-type k8s: Use versioned struct for ingress discovery	7 years ago
wangguoliang	7e6c6020ff	should use time.Since instead of time.Now().Sub Signed-off-by: wgliang <liangcszzu@163.com>	7 years ago
Johannes 'fish' Ziemke	75aec7d970	k8s: Use versioned struct for ingress discovery	7 years ago
Johannes 'fish' Ziemke	70f3d1e9f9	k8s: Support discovery of ingresses (#3111 ) * k8s: Support discovery of ingresses * Move additional labels below allocation This makes it more obvious why the additional elements are allocated. Also fix allocation for node where we only set a single label. * k8s: Remove port from ingress discovery * k8s: Add comment to ingress discovery example	7 years ago
Tobias Schmidt	29fff1eca4	Merge pull request #2966 from alkalinecoffee/consul-node-metadata Add support for consul's node metadata	7 years ago
Tobias Schmidt	d0a02703a2	Merge pull request #3105 from sak0/dev discovery openstack: support discovery hypervisors, add rule option.	7 years ago

1 2 3 4 5 ...

4021 Commits (bea12d4be1ecd24ecafab2a16f6d9dcc0b0cbc27) All Branches Search

4021 Commits (bea12d4be1ecd24ecafab2a16f6d9dcc0b0cbc27)

All Branches