I had the opposite experience with Syncthing + Logseq. The way Logseq is designed, refreshing the entire graph is a must before you even consider editing your pages in another device. I forgot to do it once and after some time editing my pages, I realized that I lost a good chunk of my notes from several days back.
I was in the middle of transitioning my existing account to Brex. I have many things to do and so this lower on my priority list. I'm glad I was only in the beginning of the transition and that I hadn't moved over completely. While I wasted a few hours of my time, nothing near what I would have wasted if you had pulled this on me later.
But if traffic is high in the beginning of the month does this mean you should be allocated more budget? How much? Such an alarm doesn't really give you any insight into where the additional costs might be, or where/whether it's worth spending engineering time optimizing!
If you don't have a budget, then that's what you should establish first. If you can't get a handle on your budget, then no set of tools and techniques is going to save you.
The point is that the budget changes all the time for anything other than a simple application stack. If you're constantly experimenting and building new applications, you basically need to quickly glance at your daily usage to make sure you won't get a surprise in 30 days.
I've never worked at a company where the cloud budget fluctuated in the way that you are describing, and we certainly didn't run "simple application stacks." Costs and usage patterns are predictable. If you want to do whatever you want, costs be damned, then I'd ask why you're even bothering to be alerted about costs in the first place.
I agree that you have to make it a daily or weekly habit to check because 30 days is too long a time to incur costs you're not aware of. That's why I built Billgist.com, same idea but it sends a daily email with usage amount right in the subject, like: $16.56 XYZAccount – Daily AWS billing alert.
