valyala

8 ms·

121.
Scaling our observability platform by embracing wide events and replacing OTel(clickhouse.com)
200 points by valyala 1y ago|108 comments
122.
OpenTelemetry for Go: Measuring the Overhead(coroot.com)
6 points by valyala 1y ago|0 comments
123.
by valyala 1y ago
Thanks! If you'll hit any issues with the integration, then please file them at https://github.com/VictoriaMetrics/VictoriaMetrics/issues , so we could quickly resolve them.
124.
Comparing Elasticsearch, Tempo, ClickHouse and VictoriaLogs in Tracing Benchmark(victoriametrics.com)
6 points by valyala 1y ago|0 comments
125.
I have divided (and partly uninformed) views on OpenTelemetry(utcc.utoronto.ca)
2 points by valyala 1y ago|0 comments
126.
by valyala 1y ago
VictoriaMetrics CTO here. If you hit some issues with VictoriaLogs or if you have ideas on how VictoriaLogs usability could be improved, then please file issues at https://github.com/VictoriaMetrics/VictoriaMetrics&#x2F
127.
by valyala 1y ago
What if the machine is unavailable? It is better to store logs from multiple hosts into a centralized database, so the logs could be investigated even if the original host is no longer available for any reason.
128.
by valyala 1y ago
200GB of metrics and 1TB of logs can be efficiently processed by a single-node observability solution optimized for metrics/logs (for example, VictoriaMetrics/VictoriaLogs), which runs on a low-end computer such as Raspberry Pi. T
129.
by valyala 1y ago
VictoriaLogs developer here. I agree with you - it is important to support multiple popular data ingestion protocols at the database for logs, so users could continue using the existing protocol instead of adding an intermediate proxy for c
130.
by valyala 1y ago
Could you add the ability to ship logs to VictoriaLogs? The logs can be shipped via one of the supported data ingestion protocols - https://docs.victoriametrics.com/victorialogs/data-ingestion...
131.
Peacetime Observability: Spotting Risks Before They Become Incidents(coroot.com)
3 points by valyala 1y ago|0 comments
132.
We're replacing our 27-node Elasticsearch with a single VictoriaLogs node(aus.social)
3 points by valyala 1y ago|0 comments
133.
by valyala 1y ago
What is the main difference between ClickStack and SigNoz, which also stores data in ClickHouse?
134.
Our Grafana and Loki installs have become 'legacy software' here(utcc.utoronto.ca)
5 points by valyala 1y ago|0 comments
135.
Fix Safari SecurityError when Block All Cookies is enabled(github.com)
1 points by valyala 1y ago|0 comments
136.
Go synctest: solving flaky tests(victoriametrics.com)
1 points by valyala 1y ago|0 comments
137.
by valyala 1y ago
> For example, every damn log message has hundreds of fields,. Most of which never change. Why not push this information once, on service startup an not with every log message? If the log field doesn't change with every log entry, t
138.
by valyala 1y ago
You can't derive system metrics such as the usage of CPU, RAM, disk IO, disk space and network, from wide events.
139.
by valyala 1y ago
Loki doesn't work well with structured logs and wide events because it has weak support for log fields with many unique values such as trace_id, span_id, user_id, etc. (aka high-cardinality fields). The recommended way to store structu
140.
by valyala 1y ago
HDD-based persistent disks usually have much lower IO latency comparing to S3 (microseconds vs hundreds of milliseconds). This may help improving query performance a lot. sc1 HDD-based volumes are cheaper than S3, while st1-based volumes ar
141.
by valyala 1y ago
> The mistake many teams make is to worry about storage but not querying The amounts of logs, wide events and traces, which must be stored and queried, is frequently measured in hundreds of terabytes and petabytes. A petabyte of data on
142.
AgentHouse(clickhouse.com)
2 points by valyala 1y ago|0 comments
143.
by valyala 1y ago
There is no need in loading data block, which has no rows with column values, which might be included into the final set of rows. If every column in every granule has a header containing the minimum and the maximum value seen in the granule
144.
Bloat – Rob Pike(docs.google.com)
7 points by valyala 1y ago|0 comments
145.
Don't default to microservices: You'll thank us later(victoriametrics.com)
3 points by valyala 1y ago|0 comments
146.
Performance optimization in TSDB: sync.Pool for CPU-bound operations(victoriametrics.com)
3 points by valyala 1y ago|0 comments
147.
Container CPU requests and limits explained with GOMAXPROCS tuning(victoriametrics.com)
5 points by valyala 2y ago|1 comments
148.
by valyala 2y ago
It would be great using VictoriaLogs as a storage for structured logs in Coroot, since it is optimized for structured logs with arbitrary sets of labels. See https://docs.victoriametrics.com/victorialogs/keyconcepts&#x2
149.
by valyala 2y ago
This is a follow-up for the 10-years old post https://news.ycombinator.com/item?id=9504028
150.
A year of Rust in ClickHouse(clickhouse.com)
125 points by valyala 2y ago|94 comments

More ›