3 ms·
I've thought about this a lot too and agree to a good extent, however: > 2. You can derive arbitrary metrics from log streams Not quite. There isn't really a
by ris 7y ago
I've thought about this a lot too and agree to a good extent, however:
> 2. You can derive arbitrary metrics from log streams
Not quite. There isn't really a way (that I'd consider sensible) to get periodic, system-level measurements such as system load, memory usage, I/O stats from logs.
I'm also far less anxious about the idea of throwing away metrics beyond a certain age than I would with logs, and to a degree that allows me to worry a bit less about the volume of data I collect through metrics.
Doubling up on metrics/logs can also be key in detecting that one of those systems isn't working properly for a particular set of hosts.
- yehosef 7y ago>There isn't really a way (that I'd consider sensible) to get periodic, system-level measurements such as system load, memory usage, I/O stats from logs. Why not Metric Beats (https://www.elastic.co/products/beats/metricbeat https://www.elastic.co/products/beats/metricbeat). The log structure is generally numbers, but it is still fundamentally different from pure metrics, IMO. My biggest problem with using ES for metrics is that with the exception of Timelion, there is no way to do cross metric calculations (db queries/s over requests/s => db queries/request)