In build view in Blue Ocean

(e.g. https://anonymised/blue/organizations/jenkins/build-job/detail/build-job/5364/pipeline/830)

we noticed hundreds of irrelevant events from jenkins-blueocean-core-js. Nothing new, but it started to generate too much traffic and is harder and harder to accept.
 
Request URL:
https://build-jenkins.kumoroku.com/sse-gateway/listen/jenkins-blueocean-core-js-1615302278422-5iyp3
 
Event stream - hundreds/thousands of messages like:
{{

{"jenkins_event_uuid":"384d9c08-5114-427b-b701-cf67e3bfa454","sse_subs_dispatcher_inst":"1117208742","pipeline_job_name":"repository-builder-sumologic/PR-2342","pipeline_run_id":"1","jenkins_event_timestamp":"1615304586265","pipeline_step_name":"sh","pipeline_step_stage_id":"402","pipeline_step_is_paused":"false","pipeline_step_flownode_id":"402","jenkins_event":"pipeline_stage","pipeline_step_stage_name":"Checkout branch PR-2342","sse_subs_dispatcher":"jenkins-blueocean-core-js-1615302278422-5iyp3","pipeline_context":"2/3/4/10/11/12/13/14/15/16/17/18/19/150/151/152/156/160/161/166/167/169/360/362/363/364/365/370/371/372/373/394/395/396/397","jenkins_instance_url":"https://anonymised","jenkins_channel":"pipeline"}

}}
 
and we know for sure they have nothing to do with the build which we have opened on the screen in blue ocean. 
 
Now multiply that by the number of developers working in parallel and having multiple tabs open each = way too many requests to jenkins master.
 

 
Not sure if related:
https://issues.jenkins.io/browse/JENKINS-42137
 
______________________________________________________________
ps Also I think that Blue Ocean should pause fetching data if tab is not active or a build finished, but for this one I'm creating a separate JIRAs:

https://issues.jenkins.io/browse/JENKINS-65065