Graylog2-server: Change frequency of constant REST calls in Graylog UI

[susanjia]

Expected Behavior

After login to graylog UI, in the web browser, there are some constantly rest api calls to the graylog server, for example:
https:///api/system/cluster/nodes (GET, every 5 seconds)
https:///api/cluster/metrics/multiple (POST, every 2 seconds)
https:///api/system/notifications (GET, every 3 seconds)
https:///api/(GET, every 20 seconds)

Expect: the frequency of the rest API calls can be configured

Current Behavior

Currently, the constantly rest api calls to the graylog server can not be changed.

Possible Solution

N/A

Steps to Reproduce (for bugs)

Context

The constantly REST api in Graylog UI lowers down the performance when a big amount of user log into Graylog UI.

Your Environment

• Graylog Version:2.2.3
• Elasticsearch Version: 2.2.3
• MongoDB Version: 2.2.3
• Operating System: Linux
• Browser version: Chrome, Fire Fox and IE

[dennisoelkers]

Thanks for your input. What is the higher level use case that you want to solve with this?

[susanjia]

I expect that in the config file, we can specify the frequency for the REST api calls.
For example:
After login, currently every 5 seconds, there will be a GET request https:///api/system/cluster/nodes

I expect we can config the frequency for this call to another value, like 10 seconds.

Similar for the following REST api calls, I expect we can config the frequency to a different value.
https:///api/cluster/metrics/multiple (POST, every 2 seconds)
https:///api/system/notifications (GET, every 3 seconds)
https:///api/(GET, every 20 seconds)

[gruselglatz]

I think most of the normal Users dont need the Statistics on the top right corner.

[susanjia]

Is there a way to disable it?

[joschi]

@susanjia No.

[dennisoelkers]

@susanjia why do you expect you can configure that? What is the high level problem you want to solve?

[dennisoelkers]

@susanjia: Found it now in the "Context"-section of your original issue.

[florianpopp]

We are using GitHub issues for tracking bugs in Graylog itself, but this doesn't look like one. Please post this issue to our discussion forum or join the #graylog channel on freenode IRC.

Thank you!