-
-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Ability to disable/enable polling interval option from backend #789
Closed
jb-abhi opened this issue
Aug 3, 2024
· 4 comments
· May be fixed by https-quantumblockchainai-atlassian-net/ossinsight#887
Closed
Feature Request: Ability to disable/enable polling interval option from backend #789
jb-abhi opened this issue
Aug 3, 2024
· 4 comments
· May be fixed by https-quantumblockchainai-atlassian-net/ossinsight#887
Comments
Do you think that this should be under "read only" mode? |
yes, it would be great that way. Will the polling interval be set to off and hidden in "read only" mode? If so, that is fine. |
I've added a new createBullBoard({
queues: [new BullMQAdapter(exampleBullMq), new BullAdapter(exampleBull)],
serverAdapter,
options: {
uiConfig: {
pollingInterval: {
forceInterval: 5, // any valid value, -1 for off.
showSetting: false, // hides the setting option from Settings modal
},
},
},
}); |
Oh, nice. Thanks a ton. 😊 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
There is a settings option provided in UI through which user can select the polling interval. But the issue is that if the user selects a shorter polling interval, say 3-5 sec, then there will be an increased load on the backend.
Suggestion
Can add another optional option in UI Config Type with the name polling which can be set to off, which can then be used in UI to show/hide the polling interval option
Reasoning
This UI can be used by QA, Devs, clients etc. to monitor the jobs. If client or QA selects a shorter polling option, then that may incur additional requests and charges for different hosting services like azure, aws etc.
The text was updated successfully, but these errors were encountered: