The result: full visibility into AI-assisted development.
By integrating #telemetry into VictoriaMetrics Stack, you can create insightful dashboards and queries that address key questions about your AI-assisted development processes, utilizing MetricsQL for metrics and #LogsQL for #logs and traces.

Learn more in our latest blog post 👇
https://bit.ly/45e88o3

📈 #LogsQL query language provides fast full-text search, advanced analytics, and data extraction/transformation at query time. Can be combined with Unix tools like grep, less, sort, and jq for log analysis.

🎯 Optimized for high cardinality fields like trace_id, user_id, and ip addresses. Supports logs with hundreds of fields (wide events), multitenancy, out-of-order ingestion, live tailing, and surrounding log context selection.

Yeah, #logsql is kind of amazing. I haven't seen many be able to do join syntax for logs that makes sense.

I'm pretty sure #victorialogs is my logs server now. I'm having actual fun slicing through logs. Send help! 😅

https://docs.victoriametrics.com/victorialogs/logsql/#join-pipe

Also, doesn't help that I'm getting fairly quickly productive with its #logsQL. I more than familiar with #Loki and #ElasticSearch for these things, but #victorialogs really does feel a bit easy to understand how to query and filter.

Though once I have like a month with it, I will likely find the short cases that breaks this love and question why not use SQL. 😝