valyala

13 ms·

181.
by valyala 2y ago
If you like grep, you'll like https://docs.victoriametrics.com/victorialogs/querying/#comm...
182.
by valyala 2y ago
Try VictoriaLogs [1]. It supports wide events with hundreds of fields (aka canonical logs). [1] https://docs.victoriametrics.com/victorialogs/
183.
How HTTP/2 Works and How to Enable It in Go(victoriametrics.com)
2 points by valyala 2y ago|0 comments
184.
by valyala 2y ago
You can emit as many events per request as you wish, and store all of them to VictoriaLogs. But it is recommended emitting a single "master" event with all the context and useful information about the request in separate fields, w
185.
by valyala 2y ago
Wide events are plain old structured logs with many fields. They can be represented as JSON. They also can be represented as logfmt, protobuf or any other format suitable for representing a set of (field=value) pairs. The novelty of wide ev
186.
by valyala 2y ago
VictoriaLogs - it is fully open source released under Apache2 license, and it can efficiently store and query these "plain old JSONs" with hundreds of fields (aka wide events) - https://docs.victoriametrics.com/vic
187.
by valyala 2y ago
This works only for Go language, which provides slog package ( https://go.dev/blog/slog ). What about other programming languages?
188.
by valyala 2y ago
This is possible by semi-automatic detection of anomalies over time for some preset of fields used for grouping the events (aka dimensions) and another preset of fields used in stats calculations (aka metrics). In general case this is hard
189.
by valyala 2y ago
While the article is written by observability vendor, it contains an excellent information about wide events, without annoying advertisement of the vendor.
190.
by valyala 2y ago
Wide events aren't limited to website analytics. Thy are useful for observability of any application types - databases, services, microservices, web servers, application servers, mobile apps, industrial apps, IoT, etc.
191.
by valyala 2y ago
JSON column type in ClickHouse [1] looks promising, since it allows storing wide events with arbitrary sets of fields. This feature is still in beta. Let's see how it will evolve. [1] https://clickhouse.com/docs/en
192.
by valyala 2y ago
Wide events is a great concept for observability space! This a superset of structured logs and traces. Wide events is basically structured logs, where every log entry contains hundreds of fields with various properties of the log entry. Thi
193.
by valyala 2y ago
Very good post! We at VictoriaMetrics try following similar practices: - Constantly think on how to simplify the code. - Keep external dependencies to the minimum - https://valyala.medium.com/stripping-dependency-bloat-in-vi
194.
Vector.dev: introduction, AWS S3 logs, and integration with VictoriaLogs(rtfm.co.ua)
2 points by valyala 2y ago|0 comments
195.
From net/RPC to gRPC in Go Applications(victoriametrics.com)
2 points by valyala 2y ago|0 comments
196.
by valyala 2y ago
The costs highly depend on the shape of the ingested logs and the type of queries, which are performed over the ingested logs. For example, VictoriaLogs compresses typical logs from Kubernetes containers by up to 50 times. This means it nee
197.
by valyala 2y ago
Agreed that Vector is much better for log collection, transformation and forwarding to the log storage than Promtail. VictoriaLogs can accept logs from Vector - https://docs.victoriametrics.com/victorialogs/data-ingesti
198.
by valyala 2y ago
JSON is the universal format for structured logs. It is supported by all the popular log collectors and shippers. It is natively supported by VictoriaLogs [1] together with other popular data ingestion formats for logs [2]. [1] https:&#x2F
199.
by valyala 2y ago
VictoriaLogs author here Both Loki and VictoriaLogs are open source and free to use. But they have non-zero costs for the hardware they use and non-zero maintenance and operational costs. VictoriaLogs is much easier to configure and run pro
200.
Weak pointers in Go: why they matter now(victoriametrics.com)
78 points by valyala 2y ago|33 comments
201.
by valyala 2y ago
Yup, there is a big room for improvements there! BTW, VictoriaLogs docs are open source too [1], so we'll be more than happy receiving pull requests with improvements for the docs! [1] https://github.com/VictoriaMetrics
202.
by valyala 2y ago
Databend performance looks good! https://benchmark.clickhouse.com/#eyJzeXN0ZW0iOnsiQWxsb3lEQi... It looks like it has slightly worser on-disk data compression than ClickHouse, and slightly worser performance for some query
203.
by valyala 2y ago
That's not truth. There are solutions for logging, which are very easy to setup and operate. For example, VictoriaLogs [1] (I'm its' author). It is designed from the grounds up to be easy to configure and use. It contains a s
204.
by valyala 2y ago
ClockHouse outperforms TimescaleDB in every aspect on large volumes of data. https://benchmark.clickhouse.com/ If you have small volumes of data (let's say less than a terabyte of data), then TimescaleDB is OK to use i
205.
TLS certificates were almost never particularly well verified(utcc.utoronto.ca)
3 points by valyala 2y ago|0 comments
206.
Building Observability with ClickHouse(cmtops.dev)
59 points by valyala 2y ago|23 comments
207.
Show HN: VictoriaLogs v1.0.0 Release(github.com)
3 points by valyala 2y ago|0 comments
208.
by valyala 2y ago
HyperDX looks great! Are you going to add support for other backends (aka data sources) in order to become "Grafana for logs" solution? For example, I'd be glad to see the support for VictoriaLogs in HyperDX. It provides rich
209.
by valyala 2y ago
If you want fast searching for some unique word or phrase across terabytes of logs (aka "needle in the haystack" type of search), then take a look at VictoriaLogs [1] (I'm the core developer). It uses bloom filters for quick
210.
Go Runtime Finalizer and KeepAlive(victoriametrics.com)
3 points by valyala 2y ago|0 comments

More ›