zincobserve VS VictoriaMetrics

Take a look at https://github.com/zinclabs/zincobserve or Zinc cloud It has logs, metrics, traces, dashboards, alerts, functions and more.

For some reason if you do not want to have the complexity of log forwarders you could simply send the json logs using http them to log files in /var/lib/docker/containers . You would then configure vector/fluentbit to send it to appropriate centralized log search tool. A good light weight tool for self hosting would be - https://github.com/zinclabs/zincobserve . From what you have mentioned I think you would rather prefer the cloud service which you can access at https://zinc.dev/

shell wget https://github.com/zinclabs/zincobserve/releases/download/v0.4.4/zincobserve-v0.4.4-linux-amd64-musl.tar.gz tar -zxvf zincobserve-v0.4.4-linux-amd64-musl.tar.gz ./zincobserve

ZincObserve for logs, metrics, traces and dashboards - https://github.com/zinclabs/zincobserve

We are building long term storage for prometheus. Actually we are building an unified system for logs, metrics and traces - see https://github.com/zinclabs/zincobserve . We are working on implementing promql query interface for ZincObserve. We would love to get community feedback on which functions should we prioritize first - https://github.com/zinclabs/zincobserve/issues/582

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...

Victoria Metrics

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.

Not sure I follow since there are very competitive tools written in Go such as https://victoriametrics.com for an example in this space.

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

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.

VictoriaMetrics

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...