Terryfilch (talk | contribs) Adds new integrations: OpenTelemetry, DataDog and NewRelic. |
Citation bot (talk | contribs) Removed parameters. | Use this bot. Report bugs. | Suggested by Jay8g | Category:CS1 maint: url-status | #UCB_Category 423/711 |
||
(7 intermediate revisions by 4 users not shown) | |||
Line 1: | Line 1: | ||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
{{AfC submission|||ts=20240314192046|u=Terryfilch|ns=118}} |
|||
{{AFC submission|d|v|u=Terryfilch|ns=118|decliner=Johannes Maximilian|declinets=20240223164254|ts=20240223110152}} <!-- Do not remove this line! --> |
|||
⚫ | |||
{{AFC submission|d|corp|u=Jean-Jerome Schmidt|ns=118|decliner=Stuartyeates|declinets=20220902085558|small=yes|ts=20220901114527}} <!-- Do not remove this line! --> |
{{AFC submission|d|corp|u=Jean-Jerome Schmidt|ns=118|decliner=Stuartyeates|declinets=20220902085558|small=yes|ts=20220901114527}} <!-- Do not remove this line! --> |
||
{{AFC submission|d|nn|u=Jean-Jerome Schmidt|ns=118|decliner=S0091|declinets=20211023211206|small=yes|ts=20211023185216}} <!-- Do not remove this line! --> |
{{AFC submission|d|nn|u=Jean-Jerome Schmidt|ns=118|decliner=S0091|declinets=20211023211206|small=yes|ts=20211023185216}} <!-- Do not remove this line! --> |
||
Line 10: | Line 14: | ||
---- |
---- |
||
⚫ | |||
⚫ | |||
⚫ | |||
⚫ | |||
{{Infobox software |
{{Infobox software |
||
Line 22: | Line 26: | ||
| released = Closed Source Release: September, 2018 / |
| released = Closed Source Release: September, 2018 / |
||
1st Open Source Release: May, 2019 |
1st Open Source Release: May, 2019 |
||
| latest release version = v1. |
| latest release version = v1.99 |
||
| latest release date = |
| latest release date = 01 March 2024 |
||
| repo = https://github.com/VictoriaMetrics/VictoriaMetrics |
| repo = https://github.com/VictoriaMetrics/VictoriaMetrics |
||
| programming language = [[Go_(programming_language)|Go]] |
| programming language = [[Go_(programming_language)|Go]] |
||
Line 33: | Line 37: | ||
}} |
}} |
||
'''VictoriaMetrics''' is a free and [[Open-source software|open source]] [[time series database]] (TSDB) and monitoring solution <ref>{{Cite web|title= |
'''VictoriaMetrics''' is a free and [[Open-source software|open source]] [[time series database]] (TSDB) and monitoring solution <ref>{{Cite web |last=Speed |first=Richard |date=11 Dec 2023 |title=VictoriaMetrics takes organic growth over investor pressure |url=https://www.theregister.com/2023/12/11/victoriametrics_interview/ |access-date=2023-01-11 |website=The Register}}</ref><ref>{{cite book |first1=Michael |last1=Hausenblas |date=26 December 2023 |title=Cloud Observability in Action |url=https://www.simonandschuster.com/books/Cloud-Observability-in-Action/Michael-Hausenblas/In-Action/9781633439597 |publisher=Manning |page=106 |isbn=978-1633439597}}</ref><ref>{{cite book |first1=Rob |last1=Chapman |first2=Peter |last2=Holmes |date=12 January 2024 |title=Observability with Grafana: Monitor, control, and visualize your Kubernetes and cloud platforms using the LGTM stack |url=https://www.packtpub.com/en-lv/product/observability-with-grafana-9781803248004 |publisher=Packt Publishing |page=24 |isbn=9781803248004}}</ref>. It is designed to collect, store and process real-time metrics. It supports the [[Prometheus (software)|Prometheus]] pull model and various push protocols ([[Graphite (smart font technology)|Graphite]], [[InfluxDB]], OpenTSDB) for data ingestion. For reading the data and evaluating alerting rules VictoriaMetrics supports the MetricsQL and Graphite query languages. The project is written in [[Go (programming language)|Go]] and licensed under the [[Apache License, Version 2.0|Apache 2]] License, with its [[source code]] available on [[GitHub]]. |
||
== History == |
== History == |
||
VictoriaMetrics was created by Aliaksandr Valialkin in response to [[Database scalability|scalability]] issues with the [[Prometheus (software)|Prometheus]] monitoring solution used at his previous place of work.<ref>{{Cite web|last= |
VictoriaMetrics was created by Aliaksandr Valialkin in response to [[Database scalability|scalability]] issues with the [[Prometheus (software)|Prometheus]] monitoring solution used at his previous place of work.<ref>{{Cite web |last=Tolmashov |first=Oleg |date=2023-11-15 |title=Unleashing VM histograms for Ruby: Migrating from Prometheus to VictoriaMetrics with vm-client |url=https://hackernoon.com/unleashing-vm-histograms-for-ruby-migrating-from-prometheus-to-victoriametrics-with-vm-client |access-date=2023-11-15 |website=HackerNoon |language=en}}</ref> Inspired by the performance and architecture of [[ClickHouse|ClickHouse]], a free software analytical database, Aliaksandr decided to implement a storage for efficient processing of time series data. He started working on a project he later named VictoriaMetrics, after his wife. |
||
The initial, [[Proprietary software|proprietary]] version of VictoriaMetrics was released in September, 2018. |
The initial, [[Proprietary software|proprietary]] version of VictoriaMetrics was released in September, 2018. |
||
Line 76: | Line 80: | ||
* OpenTSDB Put protocol |
* OpenTSDB Put protocol |
||
* Graphite plaintext protocol |
* Graphite plaintext protocol |
||
* OpenTelemetry<ref name="Adopting OpenTelemetry and its collector">{{cite web |last1=Behar |first1=Vincent |title=Adopting OpenTelemetry and its collector |url=https://archive.fosdem.org/2022/schedule/event/adapting_otel/attachments/slides/4975/export/events/attachments/adapting_otel/slides/4975/adopting_opentelemetry.pdf |website |
* OpenTelemetry<ref name="Adopting OpenTelemetry and its collector">{{cite web |last1=Behar |first1=Vincent |title=Adopting OpenTelemetry and its collector |url=https://archive.fosdem.org/2022/schedule/event/adapting_otel/attachments/slides/4975/export/events/attachments/adapting_otel/slides/4975/adopting_opentelemetry.pdf |website=FOSDEM |access-date=2022-02-06}}</ref><ref name="Vendors who natively support OpenTelemetry">{{cite web |last1=OpenTelemetry |first1=Authors |title=Vendors who natively support OpenTelemetry |url=https://opentelemetry.io/ecosystem/vendors/ |website=OpenTelemetry |publisher=OpenTelemetry Authors |access-date=2024-01-31}}</ref> |
||
* DataDog v2 data ingestion protocol |
* DataDog v2 data ingestion protocol |
||
* NewRelic agent data ingestion |
* NewRelic agent data ingestion |
||
Line 88: | Line 92: | ||
== Usage == |
== Usage == |
||
{{More citations needed|section|date=March 2024}} |
|||
* VictoriaMetrics is used by [[CERN]] for real-time monitoring of [[Compact Muon Solenoid|CMS]]<ref>{{Cite journal|last=Kuznetsov|first=Valentin|title=CMS Monitoring R&D: Real time monitoring and Alerts|url=https://indico.cern.ch/event/877333/contributions/3696707/attachments/1972189/3281133/CMS_mon_RD_for_opInt.pdf|journal=Cornell University / Indico, CERN|pages=26|access-date=2022-08-30}}</ref> |
* VictoriaMetrics is used by [[CERN]] for real-time monitoring of [[Compact Muon Solenoid|CMS]]<ref>{{Cite journal|last=Kuznetsov|first=Valentin|title=CMS Monitoring R&D: Real time monitoring and Alerts|url=https://indico.cern.ch/event/877333/contributions/3696707/attachments/1972189/3281133/CMS_mon_RD_for_opInt.pdf|journal=Cornell University / Indico, CERN|pages=26|access-date=2022-08-30}}</ref> |
||
* [[Grammarly]] uses VictoriaMetrics for internal monitoring of the infrastructure |
* [[Grammarly]] uses VictoriaMetrics for internal monitoring of the infrastructure |
||
* [[Percona]] Monitoring and Management (PMM) solution uses VictoriaMetrics |
* [[Percona]] Monitoring and Management (PMM) solution uses VictoriaMetrics |
||
* Open Cosmos has integrated VictoriaMetrics into its mission-critical satellite control and data distribution platform<ref>{{Cite web| |
* Open Cosmos has integrated VictoriaMetrics into its mission-critical satellite control and data distribution platform<ref>{{Cite web |last=Bridgwater |first=Adrian |date=25 January 2023 |title=Is it time for time-series databases? |url=https://www.siliconrepublic.com/start-ups/victoriametrics-data-monitoring-satellites |access-date=2023-01-25 |website=Computer Weekly}}</ref> |
||
* Other organizations using VictoriaMetrics include Semrush, Ably, Roblox, Cloudflare, Criteo and more. |
* Other organizations using VictoriaMetrics include Semrush, Ably, Roblox, Cloudflare, Criteo and more. |
||
== References == |
== References == |
Latest revision as of 23:54, 14 March 2024
- Comment: I'm not seeing the in-depth coverage in independent secondary sources needed here. Stuartyeates (talk) 08:55, 2 September 2022 (UTC)
- Comment: Sources are not independent. Also, blogs and are not reliable sources and links github should not used. S0091 (talk) 21:12, 23 October 2021 (UTC)
Original author(s) | Aliaksandr Valialkin |
---|---|
Developer(s) | VictoriaMetrics Inc. |
Initial release | Closed Source Release: September, 2018 / 1st Open Source Release: May, 2019 |
Stable release | v1.99
/ 01 March 2024 |
Repository | https://github.com/VictoriaMetrics/VictoriaMetrics |
Written in | Go |
Operating system | Linux, Windows, MacOS, FreeBSD, OpenBSD |
Available in | English |
Type | Time Series Database / Monitoring Solution |
License | Apache 2.0 |
Website | https://victoriametrics.com |
VictoriaMetrics is a free and open source time series database (TSDB) and monitoring solution [1][2][3]. It is designed to collect, store and process real-time metrics. It supports the Prometheus pull model and various push protocols (Graphite, InfluxDB, OpenTSDB) for data ingestion. For reading the data and evaluating alerting rules VictoriaMetrics supports the MetricsQL and Graphite query languages. The project is written in Go and licensed under the Apache 2 License, with its source code available on GitHub.
History
VictoriaMetrics was created by Aliaksandr Valialkin in response to scalability issues with the Prometheus monitoring solution used at his previous place of work.[4] Inspired by the performance and architecture of ClickHouse, a free software analytical database, Aliaksandr decided to implement a storage for efficient processing of time series data. He started working on a project he later named VictoriaMetrics, after his wife.
The initial, proprietary version of VictoriaMetrics was released in September, 2018.
Later, in May 2019, the open source version of VictoriaMetrics was released.
Architecture
VictoriaMetrics is distributed as a single-node or cluster version.
- Single-node version: a single binary executable capable of scraping metrics, accepting write requests or executing reading queries.
- Cluster version: extended version of a single node split into three components:
- vminsert: for processing write requests, data sharding, routing and replication
- vmselect: for processing read requests, deduplication, caching
- vmstorage: for storing and processing data on disk
Additional Components
There are additional components in the VictoriaMetrics product ecosystem for various purposes:
- vmagent: a lightweight application for metrics collection, transformation and forwarding to the storage. Acts as a proxy between clients and VictoriaMetrics
- vmalert: an application for evaluating alerting and recording rules
- vmbackup/vmrestore: a set of tools for backup and recovery
- vmauth: an authentication proxy used for extra protection and routing
- vmctl: an utility for migrating from other systems such as Prometheus, InfluxDB or OpenTSDB
- vmanomaly: an anomaly detection service
Limitations
- No data update support
- Limited data deletion support
- Supports only numeric values as time series data point value
- Does not accept data with timestamps set in the future
Integrations
VictoriaMetrics supports data ingestion via the following protocols:
- Prometheus remote write protocol
- Prometheus exposition and OpenMetrics protocol
- InfluxDB line protocol
- OpenTSDB Put protocol
- Graphite plaintext protocol
- OpenTelemetry[5][6]
- DataDog v2 data ingestion protocol
- NewRelic agent data ingestion
Use Cases
- Kubernetes and cloud-native monitoring
- APM (Application Performance Monitoring)
- IoT sensors, connected cars, industrial telemetry
- Financial markets data
Usage
- VictoriaMetrics is used by CERN for real-time monitoring of CMS[7]
- Grammarly uses VictoriaMetrics for internal monitoring of the infrastructure
- Percona Monitoring and Management (PMM) solution uses VictoriaMetrics
- Open Cosmos has integrated VictoriaMetrics into its mission-critical satellite control and data distribution platform[8]
- Other organizations using VictoriaMetrics include Semrush, Ably, Roblox, Cloudflare, Criteo and more.
References
- ^ Speed, Richard (11 Dec 2023). "VictoriaMetrics takes organic growth over investor pressure". The Register. Retrieved 2023-01-11.
- ^ Hausenblas, Michael (26 December 2023). Cloud Observability in Action. Manning. p. 106. ISBN 978-1633439597.
- ^ Chapman, Rob; Holmes, Peter (12 January 2024). Observability with Grafana: Monitor, control, and visualize your Kubernetes and cloud platforms using the LGTM stack. Packt Publishing. p. 24. ISBN 9781803248004.
- ^ Tolmashov, Oleg (2023-11-15). "Unleashing VM histograms for Ruby: Migrating from Prometheus to VictoriaMetrics with vm-client". HackerNoon. Retrieved 2023-11-15.
- ^ Behar, Vincent. "Adopting OpenTelemetry and its collector" (PDF). FOSDEM. Retrieved 2022-02-06.
- ^ OpenTelemetry, Authors. "Vendors who natively support OpenTelemetry". OpenTelemetry. OpenTelemetry Authors. Retrieved 2024-01-31.
- ^ Kuznetsov, Valentin. "CMS Monitoring R&D: Real time monitoring and Alerts" (PDF). Cornell University / Indico, CERN: 26. Retrieved 2022-08-30.
- ^ Bridgwater, Adrian (25 January 2023). "Is it time for time-series databases?". Computer Weekly. Retrieved 2023-01-25.