[16:26:34] <claime>	 Yo, wanted to check if logstash would be able to take the hit from envoy logging 1k messages/s? Can restrict to a time window if it helps
[16:37:44] <claime>	 It's somewhat time-sensitive 
[17:01:35] <cwhite>	 claime: time limited would be best, but we could take a burst.  We're operating pretty hot these days and trying to bring the rate down.
[17:02:30] <claime>	 cwhite: I can start with +200/s, current rate is about 100/s and we see from there?
[17:02:58] <claime>	 basically I'd like (for a period) to log all 429s so we can more easily debug rate limit issues
[17:03:32] <cwhite>	 claime: is the rate increase expected to go longer than a few hours?
[17:03:35] <claime>	 The thing right now is we're doing the sampling in envoy, so even local logs are incomplete
[17:04:03] <claime>	 I'd also be open to you just dropping x% at point of ingestion so long as I can have the local logs
[17:04:19] <claime>	 cwhite: it would if I don't revert it basically
[17:04:39] <claime>	 But I can turn it on, look at stuff for a while, and turn it off
[17:06:58] <cwhite>	 That sounds reasonable.  Send it as you need and I'll be watching.  I wouldn't leave it on over the weekend though.  We are fighting rate and space constraints.
[17:10:56] <claime>	 Ack
[17:11:21] <claime>	 I'll PoC it with 20% first anyway since it's a new config flag I'm adding. I'll keep you posted
[17:12:08] <cwhite>	 Thanks!
[17:34:47] <claime>	 Going to 20% of 429s (about 200/s)
[17:40:45] <claime>	 how is it holding up?
[17:42:45] <cwhite>	 claime: looks ok right now