TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How Grammarly Improved Monitoring by over 10x with VictoriaMetrics

11 点作者 dengolius超过 1 年前

6 条评论

civiloid超过 1 年前
As one of the maintainers of go-graphite stack, I&#x27;d really like to know more about what didn&#x27;t work for Gramnarly. Based on values they&#x27;ve provided I can deduce that it was carbonapi + go-carbon, though I wonder if they&#x27;ve considered migrating to graphite-clickhouse. I understand that now it is too late, but maybe more details would help to fix same problem for other people.<p>P.S. It is also nice to see that feature that I&#x27;ve added long time ago just to have simpler dev setup for myself (vm-backend support) is actually used by people, even though it required few fixes :) (or to be precise - used at least at some point, it is not very clear if they&#x27;ve migrated to built-in one)
评论 #37409240 未加载
hagen1778超过 1 年前
&gt; Our proof-of-concept trial showed dramatically reduced compute and storage costs, translating into a 10x lower AWS bill
slach超过 1 年前
VictoriaMetrics + VictoriaLogs as prometheus + loki replacement, best choice
dengolius超过 1 年前
Why Grammarly chose the VictoriaMetrics stack from a large list of modern products for monitoring and observability
krakazyabra超过 1 年前
moved all my monitoring system to VM + VMLogs instead of ELK and loki. Boss said &quot;thanks&quot; cos I saved a lot of money. High performance with low resource usage.
anton_patsev超过 1 年前
I use VictoriaMetrics as remoteWrite for prometheus. It is popular.