github-mirrors/VictoriaMetrics

mirror of https://github.com/VictoriaMetrics/VictoriaMetrics.git synced 2024-11-21 14:44:00 +00:00

Author	SHA1	Message	Date
Yury Molodov	9541ef2e9e	vmui: add lists of top queries (#3065 ) * feat: add lists of top queries * fix: change the field label * refactor: add handlers for readability * app/vmselect: `make vmui-update` * docs: document `top queries` tab Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>	2022-09-08 21:43:37 +03:00
John Belmonte	defced2599	MetricsQL doc spellcheck (#3080 )	2022-09-08 21:28:03 +03:00
Aliaksandr Valialkin	53b0c2eee4	docs/CHANGELOG.md: document `ec273eafef` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3076	2022-09-08 21:25:30 +03:00
Aliaksandr Valialkin	b9231c715a	docs/Release-Guide.md: require manual push of the created release tags to public Github The automated push of release tags to Github require specifying the remote repository name when doing `git push <remote-repo-name> v1.xx.y`. The remote repository name can differ in different environments, so it cannot be put into Makefile rule. TODO: create a Makefile rule, which generates standard remote names for public and private repositories in Git, so `git push` for release tags could be automated then.	2022-09-08 15:00:18 +03:00
Aliaksandr Valialkin	07441b1cee	app/vmselect/netstorage: fix a typo, which leads to incorrect query results in VictoriaMetrics cluster The typo has been introduced in the commit `1a254ea20c` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3067	2022-09-08 13:48:20 +03:00
Aliaksandr Valialkin	9f20d01a81	Revert "docs: add `Monitoring at scale with Victoria Metrics` (#3078 )" This reverts commit `f24572fa65`, because the article https://tech.bedrockstreaming.com/2022/09/06/monitoring-at-scale-with-victoriametrics.html has been already added at `09ff3f1928`	2022-09-08 11:05:25 +03:00
Roman Khavronenko	f24572fa65	docs: add `Monitoring at scale with Victoria Metrics` (#3078 ) Signed-off-by: hagen1778 <roman@victoriametrics.com>	2022-09-06 16:29:48 +02:00
Max Golionko	7da9443686	moved cluster dashboard to master (#3074 ) dashboards: move cluster dashboard to master branch This change should simplify dashboards management.	2022-09-06 16:19:43 +02:00
Aliaksandr Valialkin	ef7fdbb63c	docs/Single-server-VictoriaMetrics.md: add a note that cardinality explorer at cluster version of VictoriaMetrics may return lower than expected number of unique label values See the corresponding comment in the code: `5a6e617b5e/app/vmselect/netstorage/netstorage.go (L1039-L1045)`	2022-09-06 14:46:35 +03:00
Aliaksandr Valialkin	09ff3f1928	docs/Articles.md: add https://tech.bedrockstreaming.com/2022/09/06/monitoring-at-scale-with-victoriametrics.html	2022-09-06 13:32:41 +03:00
Aliaksandr Valialkin	651ace6ce4	docs/vmctl.md: `make docs-sync` after `c5261d5f56` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2733	2022-09-06 13:19:48 +03:00
Aliaksandr Valialkin	5fa9525498	lib/storage: verify that timestamps in block are in the range specified by blockHeader.{Min,Max}Timestamp when upacking the block This should reduce chances of unnoticed on-disk data corruption. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2998 Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3011 This change modifies the format for data exported via /api/v1/export/native - now this data contains MaxTimestamp and PrecisionBits fields from blockHeader. This is OK, since the native export format is undocumented.	2022-09-06 13:08:09 +03:00
Zakhar Bessarab	c5261d5f56	vmctl: implement support of chunking data for vm-native export (#3044 ) vmctl: implement support of chunking data for vm-native export process See https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2733	2022-09-06 09:09:34 +02:00
Craig Rodrigues	462fc7b394	docs: Clarify DataDog examples for VictoriaMetrics cluster (#3048 ) Signed-off-by: Craig Rodrigues <rodrigc@crodrigues.org>	2022-09-05 16:25:05 +02:00
Yurii Kravets	7b04112352	docs: Update keyConcepts (#3040 ) docs: update keyConcepts Co-authored-by: Roman Khavronenko <roman@victoriametrics.com>	2022-09-05 13:59:28 +02:00
Aliaksandr Valialkin	ae31b2363f	app/vmselect/prometheus: follow-up after `50e2524bc2` - Add getCommonParamsWithDefaultDuration function and use it at /api/v1/series, /api/v1/labels and /api/v1/label/.../values - Document the default behaviour for setting 5 minutes time range if start arg isn't passed to /api/v1/series, /api/v1/labels and /api/v1/label/.../values - Document the change at docs/CHANGELOG.md Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/3052	2022-09-05 11:55:48 +03:00
Aliaksandr Valialkin	7dc632719d	app/vmselect/promql: consistently calculate `rate_over_sum(m[d])` as `sum_over_time(m[d])/d` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3045	2022-09-02 23:18:04 +03:00
Aliaksandr Valialkin	ac98ecdc1d	docs/CHANGELOG.md: cut v1.81.1	2022-09-02 21:58:28 +03:00
Aliaksandr Valialkin	08538ff82a	app/vmselect/netstorage: fix potential panic under high load The panic may trigger during data blocks' processing received from vmstorage nodes when some of vmstorage nodes return an error or when `-replicationFactor` is set to values higher than 2 at `vmselect`. Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3058	2022-09-02 21:38:27 +03:00
Aliaksandr Valialkin	4076277cf0	app/vmselect/promql: evaluate `union()` args in parallel in order to increase query performance Note that the parallel execution of `union()` args may take more memory and CPU time than the sequential execution if args contain heavy queries, which may load all the available CPU, disk and memory resources and vmselect and vmstorage levels.	2022-09-02 19:46:27 +03:00
Aliaksandr Valialkin	f9d4ade35a	docs/Articles.md: add a link to https://aatarasoff.medium.com/optimizing-linkerd-metrics-in-prometheus-de607ec10f6b	2022-08-31 05:03:22 +03:00
Aliaksandr Valialkin	b26de84b4a	docs/FAQ.md: mention that single-node vm is easier to setup and operate than the cluster version of vm	2022-08-31 05:02:15 +03:00
Aliaksandr Valialkin	6b0050a028	docs/CHANGELOG.md: cut v1.81.0	2022-08-31 02:33:23 +03:00
Max Golionko	c685afebb2	simplify release process (#3012 ) * simplify release process * address comments * address comments * wip * wip * wip Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>	2022-08-31 02:27:24 +03:00
Aliaksandr Valialkin	6c5d5bc7e6	docs/CHANGELOG.md: add missing link to vmagent	2022-08-31 02:21:44 +03:00
Aliaksandr Valialkin	c84e6429a0	docs/CHANGELOG.md: document v1.79.3 LTS release	2022-08-31 00:22:31 +03:00
Aliaksandr Valialkin	022bb62fa1	docs: clarify why cluster version is recommended to use for serving high loads	2022-08-31 00:22:30 +03:00
Craig Rodrigues	a54d7c24ff	docs: Add DataDog to list of ingestion methods (#3047 ) Signed-off-by: Craig Rodrigues <rodrigc@crodrigues.org> Signed-off-by: Craig Rodrigues <rodrigc@crodrigues.org>	2022-08-31 00:21:53 +03:00
Craig Rodrigues	e68a97f8d4	docs: add https://github.com/VictoriaMetrics/ansible-playbooks to README.md (#3046 ) Signed-off-by: Craig Rodrigues <rodrigc@crodrigues.org> Co-authored-by: Roman Khavronenko <hagen1778@gmail.com>	2022-08-30 20:52:24 +02:00
Aliaksandr Valialkin	bcdba8be18	docs/FAQ.md: add chapters explaining main differences between single-node and cluster versions of VictoriaMetrics - Which type of VictoriaMetrics is better to use in production? - How to migrate data from single-node VictoriaMetrics to cluster?	2022-08-30 13:12:03 +03:00
Artem Navoiev	5d4b1bc742	update multi-region guide, specify multi-level vmselect option (#3039 ) * update multi-region guide, specify multi-level vmselect option Signed-off-by: Artem Navoiev <tenmozes@gmail.com> * add more references * Apply suggestions from code review Signed-off-by: Artem Navoiev <tenmozes@gmail.com> Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>	2022-08-30 12:26:23 +03:00
Aliaksandr Valialkin	1eec2460ba	docs: fix links to DogStatsD Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3042	2022-08-30 10:49:26 +03:00
Aliaksandr Valialkin	d2e94ee91a	docs/CHANGELOG.md: document the `044d51b668`	2022-08-30 09:42:19 +03:00
Aliaksandr Valialkin	ad11b8d83d	app/vmselect/promql: follow-up after `2d71b4859c` - Use getScalar() function for obtaining the expected scalar from phi arg - Reduce the error message returned to the user when incorrect phi is passed to histogram_quantiles - Improve the description of this bugfix in the docs/CHANGELOG.md Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/3026	2022-08-27 01:35:49 +03:00
Dmytro Kozlov	2d71b4859c	vmselect/promql: fix panic in histogram_quantiles function (#3029 ) * vmselect/promql: fix panic in histogram_quantiles function * Update docs/MetricsQL.md Co-authored-by: Roman Khavronenko <roman@victoriametrics.com> Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com> Co-authored-by: Roman Khavronenko <roman@victoriametrics.com>	2022-08-27 01:33:56 +03:00
Aliaksandr Valialkin	c06e7a142c	lib/promscrape: optimize discoveryutils.SanitizeLabelName() Cache sanitized label names and return them next time. This reduces the number of allocations and speeds up the SanitizeLabelName() function for common case when the number of unique label names is smaller than 100k	2022-08-27 00:17:45 +03:00
Aliaksandr Valialkin	7afe8450fc	lib/promrelabel: optimize matching for commonly used regex patterns in `if` option The following regex patterns are optimized: - literal string match, e.g. "foo" - prefix match, e.g. "foo." and "foo.+" - substring match, e.g. ".foo.*" and ".+foo.+" - alternate values match, e.g. "foo\|bar\|baz"	2022-08-26 14:53:06 +03:00
Aliaksandr Valialkin	0d4ea03a73	lib/promrelabel: optimize `action: {labeldrop,labelkeep,keep,drop}` with `regex` containing alternate values For example, the following relabeling rule must work much faster now: - action: labeldrop regex: "foo\|bar\|baz"	2022-08-24 17:54:29 +03:00
Aliaksandr Valialkin	cdffe401e4	app/vmagent: follow-up after `2b22aa1537` - Document the change at docs/CHANGELOG.md - Move auth token parsing from app/vmagent/opentsdbhttp/ to app/vmagent/main.go, since it must be parsed only when multitenancy support is enabled at vmagent side. See https://docs.victoriametrics.com/vmagent.html#multitenancy	2022-08-24 16:18:59 +03:00
Dmytro Kozlov	463ea6897b	vmselect/promql: enable search.maxPointsSubqueryPerTimeseries for sub-queries (#2963 ) * vmselect/promql: enable search.maxPointsPerTimeSeriesSubquery for sub-queries * vmselect/promql: cleanup * vmselect/promql: rename config flag * vmselect/promql: add tests * vmselect/promql: use test object instead of log * vmselect/promql: fix posible panic is subquery has more points. add description * vmselect/promql: update tests descriptions * vmselect/promql: update doInternal validation * vmselect/promql: fix linter * vmselect/promql: fix linter * vmselect/promql: update documentation and release notes * wip - Properly apply -search.maxPointsSubqueryPerTimeseries limit to subqueries. Previously the -search.maxPointsPerTimeseries limit was unexpectedly applied to subqueries if it was smaller than the -search.maxPointsSubqueryPerTimeseries . - Clarify docs for -search.maxPointsSubqueryPerTimeseries command-line flag . - Document -search.maxPointsPerTimeseries and -search.maxPointsSubqueryPerTimeseries flags at https://docs.victoriametrics.com/#resource-usage-limits . - Update docs/CHANGELOG.md . Updates https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2922 Co-authored-by: Aliaksandr Valialkin <valyala@victoriametrics.com>	2022-08-24 15:25:18 +03:00
Aliaksandr Valialkin	3d12ee47f9	docs: mention that it is safe sharing the collected profiles from security PoV The collected profiles do not contain sensitive information	2022-08-24 14:07:36 +03:00
Aliaksandr Valialkin	796aa310c2	app/vmstorage: expose `vm_{hourly,daily}_series_limit_{max,current}_series` metrics if `-storage.max{Hourly,Daily}Series` limits are set These metrics allow alerting when the number of unique series approach the limit. For example, the following query alerts when the number of series reaches 90% of the configured limit: vm_hourly_series_limit_current_series / vm_hourly_series_limit_max_series > 0.9	2022-08-24 13:44:04 +03:00
Aliaksandr Valialkin	b1e1c50627	all: update Google Analytics tracking code from Unversal Analytics to v4 This is needed because Google Analytics devs decided to force their users to update all their tracking codes to GA v4. See https://support.google.com/analytics/answer/9744165 The link to the new tracking property ( G-N9SVT8S3HK ) - https://analytics.google.com/analytics/web/?authuser=1#/a129683199p328513681/admin/streams/table/4004610168	2022-08-24 12:16:37 +03:00
Aliaksandr Valialkin	c011fb0f30	docs/vmagent.md: fix alerting query when scraped samples are dropped because of exceeded series limit This is a follow-up after `7d26414b2e`	2022-08-24 01:18:31 +03:00
Roman Khavronenko	8d0f5b9e60	docs: follow-up after `88425bb285` (#3007 ) Signed-off-by: hagen1778 <roman@victoriametrics.com> Signed-off-by: hagen1778 <roman@victoriametrics.com>	2022-08-22 13:49:17 +02:00
laixintao	88425bb285	vmalert: add $activeAt into template variables. (#3000 ) vmalert: add `$activeAt` template variable for annotations https://github.com/VictoriaMetrics/VictoriaMetrics/issues/2999	2022-08-22 13:32:36 +02:00
Aliaksandr Valialkin	6e4e3fae63	docs/CHANGELOG.md: document `d59d829cdb` Updates https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2673	2022-08-21 23:35:47 +03:00
Ivan Dudin	f69990ba10	Update Cluster-VictoriaMetrics.md (#3005 ) Flags `-search.maxTagKeys` and `-search.maxTagValues` are present at vmstorage and not at vmselect ``` # ./vmselect-prod -h \| egrep 'search.maxTagKeys\|search.maxTagValues' # ./vmstorage-prod -h \| egrep 'search.maxTagKeys\|search.maxTagValues' -search.maxTagKeys int -search.maxTagValues int ```	2022-08-21 23:28:40 +03:00
Aliaksandr Valialkin	22aa07b8c9	docs/Cluster-VictoriaMetrics.md: document the best strategies for cluster update / upgrade	2022-08-21 23:21:02 +03:00
Aliaksandr Valialkin	8550c44e31	app/vmagent: add ability to construct a label from multiple existing labels by referring them in the `replacement` field during relabeling For example: - target_label: composite-label replacement: "{{source_label1}}-{{source_label2}}"	2022-08-21 22:50:01 +03:00

1 2 3 4 5 ...

1863 commits