valyala

9 ms·

91.
by valyala 11mo ago
Boring monitoring software is rare, since it is hard to refuse adding yet another shiny feature (and breaking the core functionality along the way) instead of focusing on improving the usability for the core functionality. We at VictoriaMet
92.
by valyala 11mo ago
VictoriaLogs - https://www.truefoundry.com/blog/victorialogs-vs-loki
93.
by valyala 11mo ago
You can use other monitoring systems, which support both pull-based and push-based models for metrics' collection. See, for example, https://docs.victoriametrics.com/victoriametrics/#how-to-imp...
94.
by valyala 11mo ago
There are products, which fight against the software bloat with bells and whistles, and against breaking backwards compatibility with every new release. They put user experience and stability as the top priority - https://docs.vi
95.
by valyala 11mo ago
Take a look at Perses - https://perses.dev/
96.
by valyala 11mo ago
> lack of a promise of full PromQL compatibility (too many PromQL dashboards built by too many teams) This is a classical FUD. VictoriaMetrics is used as a drop-in replacement for Prometheus, Thanos and Mimir. It works perfectly across a
97.
AI Agents Observability with OpenTelemetry and the VictoriaMetrics Stack(victoriametrics.com)
1 points by valyala 11mo ago|0 comments
98.
Animation: What is sync.Pool and how to use it properly(youtube.com)
1 points by valyala 11mo ago|0 comments
99.
LeetCode for DevOps(labs.iximiuz.com)
1 points by valyala 11mo ago|0 comments
100.
by valyala 1y ago
Omarchy tries resolving this https://github.com/basecamp/omarchy
101.
Discarding gRPC-Go: The Story Behind OTLP/gRPC Support in VictoriaTraces(victoriametrics.com)
2 points by valyala 1y ago|0 comments
102.
Creating a Sustainable Open-Source Business Model – Introduction(victoriametrics.com)
3 points by valyala 1y ago|0 comments
103.
I have divided (and partly uninformed) views on OpenTelemetry(utcc.utoronto.ca)
2 points by valyala 1y ago|0 comments
104.
by valyala 1y ago
We also hit this scalability issue at the default memory allocator for musl. Switching back to glibc allowed increasing the performance in production by 5x on a machine with 96 CPU cores [1]. [1] https://github.com/VictoriaM
105.
Architecture by Fashion, Not Fundamentals(substack.com)
5 points by valyala 1y ago|0 comments
106.
Grepping Logs Remains Terrible(chronicles.mad-scientist.club)
2 points by valyala 1y ago|1 comments
107.
Alerting Best Practices(victoriametrics.com)
2 points by valyala 1y ago|0 comments
108.
by valyala 1y ago
Lock-free data structures and algorithms access shared memory via various atomic operations such as compare-and-swap and atomic arithmetic. The throughout of these operations do not scale with the number of CPU cores. Contrary, the throughp
109.
Monotonic and wall clock time in the Go time package(victoriametrics.com)
22 points by valyala 1y ago|6 comments
110.
by valyala 1y ago
See also https://x.com/zeeg/status/1945875538620584159
111.
I recommend native Prometheus instrumentation over OpenTelemetry(promlabs.com)
1 points by valyala 1y ago|1 comments
112.
by valyala 1y ago
Performance drop for exposing application metrics in Prometheus format is close to zero. These metrics are usually some counters, which are updated atomically in a few nanoseconds. Prometheus scrapes these metrics once per 10-30 seconds, so
113.
by valyala 1y ago
These tricks are essential for every database optimized for metrics / logs / traces. For example, you can read on how VictoriaMetrics can compress production metrics to less than a byte per sample (every sample includes metric nam
114.
by valyala 1y ago
This is called "progress". Humans always generate the amounts of data which can be stored and processed by the tools they have. The more data the tool can process under the given budget limit, the more data will be generated and s
115.
by valyala 1y ago
There are two tricks used by ClickHouse and similar databases: - Smart placement of the data on disk, which allows skipping the majority of data and reading only the needed chunks (and these chunks are stored in a compressed form in order t
116.
by valyala 1y ago
Just don't use ClickHouse for OLTP tasks. ClickHouse is an analytical database, which isn't optimized for transactional workloads. Keep calm and use Postgresql for OLTP, and ClickHouse for OLAP.
117.
by valyala 1y ago
Properly implemented wide events usually reduce storage costs comparing to typical chaotic logging of everything. It is expected that a single external request leads to exactly one wide event with all the information about this request, whi
118.
by valyala 1y ago
> Why would I use ClickHouse instead of storing log data as json file for historical log data? There are multiple reasons: 1. Databases optimized for logs (such as ClickHouse or VictoriaLogs) store logs in a compressed form, where values
119.
by valyala 1y ago
How much RAM does Elasticsearch need for fast full-text search over 100 petabytes of logs? 100 petabytes is 100 millions of gigabytes, just in case.
120.
VictoriaLogs cluster is available in Open Source(victoriametrics.com)
3 points by valyala 1y ago|0 comments

More ›