a year ago
I've recently put in place log rate limits so I don't hit the 500 logs/second rate limit and get logs dropped.
They work, but I had to dial them back further when it seemed like the rate applied to my entire project (all its services combined) vs per service rate limit.
Can you please confirm one way or the other? Thank you!
3 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 Production: outbound HTTPS to Supabase starts timing out after 10–20 minutes; redeploy temporarily fixes
- 📚 Logging
- 📚 Public API Reference
If you find the answer from one of these, please let us know by solving the thread!
Status changed to Awaiting User Response Railway • 11 months ago
a year ago
I noticed in your docs it says 500/second per replica but that's definitely not what I was seeing. I reduced to 250 logs/second per replica and was still seeing significant drops. now i've dialed it back to 100 logs /second across all replicas and services, and not seeing drops any more. But ... pretty delayed logging. Thank you
Status changed to Awaiting Railway Response Railway • 11 months ago
Status changed to Solved jake • 11 months ago