hardcock-driven development
Friendship ended with Cursor Now Claude Code is my best friend
to be fair idk if I’m going to use it as much, probably will just try out the Claude on Web UI for starters, and might try Claude Code later
I also want to try completely switching off vscode in favor of neovim
cursor has been the only thing that hold me back
I also want to try completely switching off vscode in favor of neovim
cursor has been the only thing that hold me back
Grafana Loki timeouts from a query over ~5GB of logs (~30mil logs, <24 hours timeframe)
I honestly don't understand Loki
I honestly don't understand Loki
hardcock-driven development
Grafana Loki timeouts from a query over ~5GB of logs (~30mil logs, <24 hours timeframe) I honestly don't understand Loki
I sure hope such a small amount of logs wouldn't require me to provision a bigger instance than elasticsearch requires or set up scalable deployment
hardcock-driven development
Grafana Loki timeouts from a query over ~5GB of logs (~30mil logs, <24 hours timeframe) I honestly don't understand Loki
I've figured out that I've been measuring latency a little wrong
it takes around 23 seconds to process all ~35M logs
which is, well, still seems suboptimal, but if I filter a specific service by label, that has ~4M logs -- I get ~3s per query of 100 lines, which is actually, I would say, decent
but I'm scared to image what horrors would happen if I try to query the data over longer periods of time
it takes around 23 seconds to process all ~35M logs
which is, well, still seems suboptimal, but if I filter a specific service by label, that has ~4M logs -- I get ~3s per query of 100 lines, which is actually, I would say, decent
but I'm scared to image what horrors would happen if I try to query the data over longer periods of time
and also I realized that the service that has the least useful logs -- produces 80% of the logs
chat check out the grafana I've deployed: http://127.0.0.1:3000/
😁5
took me some time to figure out how to properly do log levels when using VictoriaLogs datasource in Grafana
it's still undocumented, but you can specify it as:
in the datasources yaml
levels:
operators:
it's still undocumented, but you can specify it as:
jsonData:
logLevelRules:
- field: level
operator: equals
value: INFO
level: info
enabled: true
- field: level
operator: equals
value: WARN
level: warning
enabled: true
- field: level
operator: equals
value: DEBUG
level: debug
enabled: true
in the datasources yaml
levels:
critical, error, warning, info, debug, trace, unknownoperators:
equals, notEquals, greaterThan, lessThan, regex❤1
it also has ingestion compatibility layers with every possible protocol/format in the world
crazy
crazy
set up both Loki and VictoriaLogs, will wait for a day and see how it performs after consuming many kiloliters of logs
❤1
I suspect that memory usage might go quite a bit up, surprisingly enough it consumes less memory and CPU than Loki at the moment