[Security Solution] Alerts page shows `The "kibana.alert.rule.name" field can not be used for filtering.` error in non default space

[maximpn]

Summary

Security Solution's Alert page shows an error The "kibana.alert.rule.name" field can not be used for filtering. in a non default space when opened for the first time. After navigating another page an returning some time later the error doesn't appear. It's a discrepancy between the default and a non default spaces since the error doesn't appear in the default space.

Steps to reproduce

• Run fresh ES+Kibana ESS instances (I tested locally in dev mode)
• Create a non default space
• Switch to just created space
• Create a rule
• Create/ingest event (for example via resolver_generator script node x-pack/plugins/security_solution/scripts/endpoint/resolver_generator.js --node http://elastic:changeme@127.0.0.1:9200 --kibana http://elastic:changeme@localhost:5601/kbn --numHosts=5 --numDocs=2)
• Run/rerun the rule and make sure it generated alert(s)
• Navigate to the Alerts page

ER: The page shows an alerts chart, no error are shown. AR: The page shows The "kibana.alert.rule.name" field can not be used for filtering. instead of the chart.

After navigating away and returning back with some delay the page shows the chart as expected. Default space doesn't have the same problem.

Screenshot:

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[elasticmachine]

Pinging @elastic/security-detection-engine (Team:Detection Engine)

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-threat-hunting-investigations (Team:Threat Hunting:Investigations)

[elasticmachine]

Pinging @elastic/security-threat-hunting (Team:Threat Hunting)