valyala

24 ms·

301.
by valyala 3y ago
Yes - take a look at VictoriaMetrics. https://docs.victoriametrics.com/guides/migrate-from-influx....
302.
by valyala 3y ago
VictoriaMetrics has many users, who successfully migrated from InfluxDB. It supports data ingestion via Influx line protocol, so you can continue using Telegraf and sending the collected metrics to VictoriaMetrics instead of InfluxDB. You g
303.
by valyala 3y ago
Prometheus text exposition format [1], which is used by exporters for metrics' export at `/metrics` page, doesn't provide the ability to advertise pseudo-port or exporter name / type, which could be used as a part of `in
304.
Why Prometheus exporters need fixed TCP ports(utcc.utoronto.ca)
2 points by valyala 3y ago|3 comments
305.
Insights from a Go Developer, Navigating Rust Syntax Shenanigans(arriqaaq.substack.com)
1 points by valyala 3y ago|0 comments
306.
by valyala 3y ago
Thanks for the link to log-store! Very promising solution from the first sight, with the goals similar to VictoriaLogs.
307.
by valyala 3y ago
Agreed that PromQL and MetricsQL have limited querying capabilities comparing to SQL or InfluxQL. But they cover the most of use cases for analyzing time series measurements, and allow writing much simpler queries than InfluxQL or Flux for
308.
by valyala 3y ago
Other than good integration with existing command-line tools for log analysis, VictoriaLogs is also optimized for low resource usage. For example, it uses up to 30x less RAM and up to 15x less disk space than ElasticSearch on production wor
309.
The usability of modern log management tools is screwed
8 points by valyala 3y ago|3 comments
310.
by valyala 3y ago
> Taking VC money could provide that velosity. Could you provide a few real examples where VCs money helped companies making better product and moving faster than self-bootstrapped competitors?
311.
by valyala 3y ago
It's unusual to read that InfluxDB is fast and efficient. Did you try VictoriaMetrics? It usually needs 10x less RAM than InfluxDB for the same workload, especially when the number of active time series is high. It also uses less CPU a
312.
by valyala 3y ago
Which Prometheus backend would you recommend?
313.
by valyala 3y ago
It would be great to read in which exact ways did money from VCs help your company to reach the current state?
314.
by valyala 3y ago
Separating the storage layer from data ingestion and query layer is very smart idea, which is used behind VictoriaMetrics cluster architecture [1]. It makes the cluster more reliable when either data ingestion or query side has temporary is
315.
by valyala 3y ago
Why?
316.
by valyala 3y ago
There are Graphite-compatible monitoring systems, which use much more efficient storage format than Whisper. They resolve the most annoying issues associated with Graphite for large-scale setups - high disk IO and high disk space usage. See
317.
by valyala 3y ago
Agreed that storing structured logs into a relational database can be very expensive. But you can store structured logs into analytical databases such as ClickHouse. When properly configured, it may efficiently store and query trillions of
318.
by valyala 3y ago
There is no need to choose between push and pull, since both methods have their pros and cons [1]. Just use monitoring system, which supports both methods [2]. [1] https://docs.victoriametrics.com/keyConcepts.html#write-data
319.
by valyala 3y ago
These are slides from my 5-minute talk at Monitorama. IMHO modern shiny UIs for logs analysis are completely broken from the usability and prosuctivity PoV. They make log analysis harder comparing to plain old command-line tools such a as g
320.
You are doing logs wrong(docs.google.com)
2 points by valyala 3y ago|2 comments
321.
by valyala 3y ago
Fair reasoning. We need to think more about using the '-' instead of '!' in LogsQL. On the other hand, the '!' char is used in almost every programming language as 'NOT' operator. Probably, this is my
322.
by valyala 3y ago
- VictoriaLogs uses its own storage format, which is inspired by ClickHouse storage format [1]. This is basically a column storage format optimized for structured logs with arbitrary number of fields. - Yes, VictoriaLogs is going to support
323.
by valyala 3y ago
VictoriaLogs core developer here. The main motivation for creating VictoriaLogs was not so good experience with the existing open source solutions for logs - mainly ElasticSearch (or Opensearch) and Grafana Loki. These systems have the foll
324.
by valyala 3y ago
Initially LogsQL used the '-' char as 'NOT' shortcut. But lately we decided replacing it with '!' char, since the '-' is frequently used in full-text search phrases and/or field names. For exampl
325.
by valyala 3y ago
VictoriaLogs will be easier to setup and operate than qryn and self-hosted Sentry. Single-node VictoriaLogs is a single small self-contained statically linked binary with zero external dependencies. It runs with optimal settings out of the
326.
by valyala 3y ago
Let's determine what is the "high cardinality" logs. Grafana Loki puts log messages with the same set of labels into a single "stream". For example, all the log messages with the labels {job="nginx", insta
327.
by valyala 3y ago
VictoriaMetrics core developer here. OpenObserve looks very promising from the first sight! It prioritizes the same properties as VictoriaMetrics products: - Easy setup and operation - Low resource usage (CPU, RAM, storage) - Fast performan
328.
Never-firing alerts: What they are and how to deal with them(victoriametrics.com)
3 points by valyala 3y ago|0 comments
329.
by valyala 3y ago
Grafana Loki stores every data chunk in a separate file [1]. Data chunks are created every 2 hours per every stream [2] which receives at least a single log entry during the last 2 hours. This creates 12 * 30 = 360 chunk files per month per
330.
by valyala 4y ago
nil map in Go can be used for reading. It cannot be used for writing only.

More ›