Flex SDK → flex:RateLimiter (WARN): rate limiter hit. name="flex-ui-interaction-v1" #61
-
|
We've been using this repo as our baseline for rolling out Flex, started about a month ago using the v2 plugin. In dev I noticed that after just a call or two my console would reach 1MB of events and the Flex SDK would rate limit. Thought it was just a dev config somewhere that I couldn't find how to turn off, but it's affecting all our users on Prod since going live. Example console log after 1 call: Any ideas where this debug flag is set and how to turn it off? Our build is nearly a 1:1 mirror of this starter project template -- we have not added any special logging, changed flags, etc. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments
-
|
We've been seeing these logs on Flex UI 2.0.0-beta.1 even without any plugins deployed, so I don't believe this is a direct result of the plugin, and is expected behavior for 2.0.0-beta.1. |
Beta Was this translation helpful? Give feedback.
-
|
Very pleased to hear you have been leveraging the template. As @dremin mentioned, this is unfortunately a flex 2.0 thing - you should be able to update this in the flex configuration but it is currently ignored. you can see this setting in action in your I would advise creating a support ticket in the console to get some weight behind it, i'll do what i can to draw some attention to it internally. |
Beta Was this translation helpful? Give feedback.
-
|
I've got ticket # 9754071 open with support on this issue. |
Beta Was this translation helpful? Give feedback.
-
|
After doing some digging around in jira it looks like the fix is already waiting to be released with the next 2.0 release. as an aside, i think this might be a bit of a red herring for your root issue - i dont think the log level should have anything to do with the rate limit, thats to do with events that are being posted as far as i can tell. Perhaps you have added some code that's triggering some odd behavior. I'd recommend doing some testing locally to reproduce and dig deeper, you can lower loglevels using appConfig locally to confirm |
Beta Was this translation helpful? Give feedback.
After doing some digging around in jira it looks like the fix is already waiting to be released with the next 2.0 release.
as an aside, i think this might be a bit of a red herring for your root issue - i dont think the log level should have anything to do with the rate limit, thats to do with events that are being posted as far as i can tell. Perhaps you have added some code that's triggering some odd behavior.
I'd recommend doing some testing locally to reproduce and dig deeper, you can lower loglevels using appConfig locally to confirm