Filters broken for dashboards

[jesusgn90]

Wazuh	Elastic	Rev
3.9.3	7.2	520

Description
Filters are being applied the very first time, but if the user changes the tab and then go back, filters are now being applied as expected.

Steps to reproduce

1. Click Agents > :some_agent
2. Open Security Events
3. Now click on a different dashboard such as FIM
4. Go back to Security Events, now the agent.id filter is now being applied.

Screenshots

As we can see, there is a mixing of alerts in the above screenshot.

[jesusgn90]

After some researching, I think we've found the main cause of this issue.

It's related to the latest changes in Discover directive, some functions are called for fetching data as it did before but now we have to check if the Wazuh filters are ready in one more place.

https://github.com/wazuh/wazuh-kibana-app/blob/0639d2eb58992f03e13dfeaa5fe016255818075a/public/kibana-integrations/kibana-discover.js#L399-L402

As we can see, the above function is updating the fetching source with no filter checks as other functions do. The solution was just adding our filter blocker at the very first line of that function f50ac08.

if(!filtersAreReady()) return;

That's like a lock for the Wazuh filters, and we were using it from a long time ago, but with the 7.2 changes we forgot to add the lock to the recently added event subscription named filterUpdateSubscription.

In any case, pending testing.

[juankaromo]

Testing report

Fully remove "rule.id" as URL feature #1584

1. Rule link is removed in the Security Events Alerts summary rule.id table filed. ✅
   

2. Rule link is removed in Discover. ✅
   

3. Rule link is removed in the index pattern. ✅
   

4. Fixed after App update

Filters broken for dashboards #1583

Everything seems right, but there will be more intensive testing here #1593