moss
VictoriaMetrics
moss | VictoriaMetrics | |
---|---|---|
2 | 97 | |
941 | 10,900 | |
0.0% | 2.3% | |
0.0 | 9.9 | |
about 2 years ago | 4 days ago | |
Go | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
moss
-
Open Source Databases in Go
moss - Moss is a simple LSM key-value storage engine written in 100% Go.
-
But how, exactly, databases use mmap?
I decided to dig through a database source code to answer that question. There are plenty of databases that use mmap. Some of them decided to not use anymore. Some examples: SQLite has an option of accessing disk content directly using memory-mapped I/O[1], it seems LevelDB used to use but it changed it[2], Lucene has an option with MMapDirectory[3], LMDB uses mmap[4], a simple key/value in-memory database from Counchbase called moss uses mmap for durability of in-memory data[5] and MongoDB removed mmap storage engine for WiredTiger[6].
VictoriaMetrics
-
OpenTelemetry Is Too Complicated
VictoriaMetrics CTO here.
The referred library is the official OpenTelemetry package for reading metrics in Go language [1] - more details are available at [2].
Note that we at VictoriaMetrics like the idea of unified observability standard like OpenTelemetry. The issue is in the current otel implementation. It is too bloated and very inefficient. This contradicts to our experience with observability cases, which need very optimized format for metrics' transfer in order to reduce costs on CPU and network traffic needed to transfer and process these metrics.
VictoriaMetrics continues investing in OpenTelemetry by providing integration docs [3] and improving the existing functionality for otel metrics' ingestion [4].
[1] https://github.com/open-telemetry/opentelemetry-proto-go
[2] https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2570...
[3] https://docs.victoriametrics.com/guides/getting-started-with...
[4] https://github.com/VictoriaMetrics/VictoriaMetrics/issues/60...
-
Observability at KubeCon + CloudNativeCon Europe 2024 in Paris
Victoria Metrics
- All you need is Wide Events, not "Metrics, Logs and Traces"
-
Top 11 Grafana Alternatives in 2023
VictoriaMetrics is primarily a time-series database designed for efficiently storing and querying time-series data. It is often used as a back-end data store for time-series data generated by monitoring systems like Prometheus. VictoriaMetrics excels at handling large volumes of time-series data, offering efficient storage and query capabilities.
-
InfluxDB CTO: Why We Moved from Go to Rust
Not sure I follow since there are very competitive tools written in Go such as https://victoriametrics.com for an example in this space.
-
μMon: Stupid simple monitoring
Did you try VictoriaMetrics [1] and vmagent [2]? It is a single self-contained binary without external dependencies. It requires relatively low amounts of CPU, RAM, disk space and disk IO, and it runs on ARM.
[1] https://github.com/VictoriaMetrics/VictoriaMetrics/
[2] https://docs.victoriametrics.com/vmagent.html
-
CERN swaps out databases to feed its petabyte-a-day habit
https://github.com/VictoriaMetrics/VictoriaMetrics#cardinali...
If I understanding correctly, it deal with high cardinality by dropping data, the operators need to monitor for this and adjust their data to lower the cardinality.
-
Prometheus Observability Platform: Intro
VictoriaMetrics
-
VictoriaMetrics VS openobserve - a user suggested alternative
2 projects | 30 Aug 2023
-
OpenTelemetry in 2023
You shouldn't unless you want to use the new open source standard for telemetry. You won't benefit from simplicity or performance improvements. It would be quite the opposite. You can check what is the actual cost of open telemetry adoption here [0]
But if you ever decide to go this path - VictoriaMetrics supports OpenTelemetry protocol for metrics [1]
[0] https://github.com/VictoriaMetrics/VictoriaMetrics/pull/2570
[1] https://docs.victoriametrics.com/Single-server-VictoriaMetri...
What are some alternatives?
badger - Fast key-value DB in Go.
mimir - Grafana Mimir provides horizontally scalable, highly available, multi-tenant, long-term storage for Prometheus.
bolt
thanos - Highly available Prometheus setup with long term storage capabilities. A CNCF Incubating project.
tidb - TiDB is an open-source, cloud-native, distributed, MySQL-Compatible database for elastic scale and real-time analytics. Try AI-powered Chat2Query free at : https://tidbcloud.com/free-trial
prometheus - The Prometheus monitoring system and time series database.
loki - Like Prometheus, but for logs.
InfluxDB - Scalable datastore for metrics, events, and real-time analytics
ClickHouse - ClickHouse® is a free analytics DBMS for big data
fastcache - Fast thread-safe inmemory cache for big number of entries in Go. Minimizes GC overhead