You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the bug?
Added multiple datasources in opensearch for remote clusters. The added datasources shows up in dropdown in devtools but not in security analytics. In security analytics, datasource defaults to local cluster, although a newly added datasources is added as default.
How can one reproduce the bug?
Steps to reproduce the behavior:
Add datasources in opensearch
Go to security analytics and click on Local Cluster (written on top right corner)
Check the available datasources present in dropdown
It shows only 1 option i.e Local Cluster.
What is the expected behavior?
All the added data sources should be present in dropdown for selection in datasources in security analytics
What is your host/environment?
OS: linux
Version: 2.16.0
Plugins: security analytics
Do you have any screenshots?
All datasources available for selection in dev tools
Added datasources not showing up in security analytics
The text was updated successfully, but these errors were encountered:
kritikashahi
changed the title
[BUG] Added datasources not visible in security analytics but shows up in dev tools
[BUG] Added datasources not visible in security analytics
Nov 12, 2024
What is the bug?
Added multiple datasources in opensearch for remote clusters. The added datasources shows up in dropdown in devtools but not in security analytics. In security analytics, datasource defaults to local cluster, although a newly added datasources is added as default.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
All the added data sources should be present in dropdown for selection in datasources in security analytics
What is your host/environment?
Do you have any screenshots?
All datasources available for selection in dev tools
Added datasources not showing up in security analytics
The text was updated successfully, but these errors were encountered: