Hi Yuepeng, This seems interesting there are a few comments that I have based on the doc and the feature request:
1. Can you give an example of the scenarios where this can be useful. Adding rate limiters to logs seems like an interesting idea, but just wondering what is the business motivation. 2. Number of customers requesting this feature? Maintenance as @Piotr Karwasz <pkarw...@apache.org> , mentioned is going to be a 5 - 10 year period, if we do not have enough customers requesting this, then maintenance of this feature + efforts might not be worth it. 3. I am interested in what you talked about - dimensions and allow thresholds to be shared across these dimensions or metrics. Could you give an example of this particularly, I just want to know about the real world applications of this. Regards, Jay Katariya On Sun, Jan 26, 2025 at 2:57 AM Yuepeng Pan <panyuep...@apache.org> wrote: > Hi, community, > > > > > In some business scenarios, users expect the log rate limit thresholds to > be influenced > > by different dimensions and allow thresholds to be shared across these > dimensions or metrics. > > This enables the system to flexibly output as many logs as possible within > the safe constraints of the thresholds. > > Therefore, it is meaningful to introduce rate limiters based on process > granularity and logger granularity, > > targeting both the number of log entries and the size of the logs. > > > > > So, I'd like to start a discussion about 'Support a cross-rate Filter > based on process and logger granularity'.[1] > > > > > Looking forward to your attention and comments. > > > > > Thank you. > > > > > [1] > https://docs.google.com/document/d/1kVa0V_RrPpT5aa5rfxEaH-QxyXTplQr65xUMZMmDoFA/edit?tab=t.0#heading=h.jfuayzme0ome > > > > > Best, > > Yuepeng Pan
