可观测性技术栈 – 首先考虑人工智能?

1作者: jblake7 天前原帖
所以……我落后太多了。这周才开始接触Claude……它已经在处理我大部分的编码和错误修复了。真是疯狂。 关于我公司的背景:成熟的Ruby on Rails应用(14年),使用Sidekiq、Redis、PG、AWS Lambda/EventBridge、React/Preact、Swift等。托管在Heroku上,数据库使用量很大。我是一个独立开发者,既是所有者也是运营者。 当前技术栈: 使用Datadog进行日志记录(尝试过APM、指标等,但Heroku的构建包太臃肿,我不得不将其移除),所以现在只是简单地将Heroku日志转发到Datadog。我真的很怀念statsd主机和APM的功能……但这让我的slug大小从约250MB增加到350MB以上,导致启动和部署变得更慢。我也想要脱离Heroku……总有一天……但我现在甚至无法想象。 使用Bugsnag来处理错误。已经将其迁移到Sentry,尝试AI相关的功能。 对Datadog有点厌倦,每个月还要支付600美元的账单,外加我的企业承诺。最大的痛点是:索引按行计费,而不是按GB(这让我不愿意进行简单的日志记录,所以我不得不将事件放入单个请求/作业日志行中,然后复杂地分割消息,以免Heroku日志转发破坏JSON格式)。 配置Datadog的复杂性是一个痛点,但AI在很大程度上解决了这个问题。 我想要一个一体化的工具……这样AI可以在一个地方获取所有上下文似乎是最好的。然而,Sentry的日志功能还很初级,速度慢,功能有限。我尝试过BetterStack,同样也很基础。定价与Datadog相似。我每月大约处理600GB和5000万行数据。 所以我得出的结论是,Datadog的日志仍然比市场上任何其他工具要好得多。但Sentry在错误处理方面要好得多(我还有其他项目:iOS应用、React、原生JS)。 有什么建议吗?我喜欢投入时间在这些事情上,当我需要修复某些东西时,所有信息都在那儿让我感到非常开心,但在某个时刻——就像使用Heroku的原因一样——我有很多其他事情需要关注。 探索切换的主要原因是为了自动化根本原因分析、错误修复、性能改进等。我对Claude仍然是个新手,现在只是把它当作Claude Code VSCode聊天中的配对程序员,有时使用CLI。
查看原文
So... I&#x27;m way behind. Just got into Claude this week... it&#x27;s already doing most of my coding and bug fixes. Crazy stuff.<p>Some background on my company: Mature (14 yrs) Ruby on Rails app, Sidekiq, Redis, PG, AWS lambda&#x2F;eventbridge, react&#x2F;preact, swift, and others. Hosted on Heroku. Very database heavy. Solo guy, owner&#x2F;operator.<p>Current stack:<p>Datadog logging (dabbled in APM, metrics, and others, but the build pack for Heroku is so bloated I had to remove it), so now it&#x27;s a simple Heroku log drain to datadog. I really miss the statsd host and APM stuff... but it took my slug size from ~250mb to over 350 and made booting and deploys much slower. I&#x27;d also like to get off Heroku.... some day... but I can&#x27;t event fathom it.<p>Bugsnag for errors. Already moved this to Sentry to try out the AI stuff.<p>A little fed up with Datadog and receiving $600 monthly bills on top of my enterprise commitment. biggest pain points: indexing is priced per line, not by gb (discourages me from simple logging, so I resort to putting events into a single request&#x2F;job log line, then have complex chunking of messages to split them up so that Heroku log drains don&#x27;t destroy the json).<p>The complexity of configuring datadog was a pain point, but AI has mostly solved that.<p>I want an all in one tool... it seems that would be best for AI to have all the context in one place. However, sentry logs is pretty green, slow, and doesn&#x27;t do much. I tried BetterStack, again, pretty basic. Pricing is similar to datadog anyway. I do about 600gb + 50M lines a month.<p>So I&#x27;ve come to the conclusion that Datadog logs are still so much better than anything out there. But Sentry is quite a bit better for errors (I also have other projects: iOS app, react, vanilla JS).<p>Any tips? I love putting time into this stuff, it makes me so happy when I have to fix something and it&#x27;s all there, but at some point - like the reason for using Heroku - I have a lot of other stuff I need to focus on.<p>The main reason for exploring a switch is to automate root cause analysis, bug fixing, performance improvements, etc. Im still a noobie with Claude, right now I&#x27;m just using it as a pair programmer in Claude Code vscode chat, sometimes CLI.