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
Is your feature request related to a problem? Please describe.
When using a chart resource with Steampipe dashboards, there is no way to generate a link dynamically based on the graph's content.
This makes dashboards less interactive. For example, if we graph resources in the cloud by region, I could get 3 different regions in my graph with the number of resources, like eu-west-1, us-east-1, and eu-west-2. When you select the graph using the mouse, the values are highlighted, but there is no way to generate a link with that data. For example, I want to go to another dashboard with a filter applied for that region (https://mydashboards/local.dashboard.test?input.region="SELECTED_VALUE")
Describe the solution you'd like
A similar behavior is already implemented with the tables resources, using:
Is your feature request related to a problem? Please describe.
When using a
chart
resource with Steampipe dashboards, there is no way to generate a link dynamically based on the graph's content.This makes dashboards less interactive. For example, if we graph resources in the cloud by region, I could get 3 different regions in my graph with the number of resources, like eu-west-1, us-east-1, and eu-west-2. When you select the graph using the mouse, the values are highlighted, but there is no way to generate a link with that data. For example, I want to go to another dashboard with a filter applied for that region (https://mydashboards/local.dashboard.test?input.region="SELECTED_VALUE")
Describe the solution you'd like
A similar behavior is already implemented with the tables resources, using:
I think we should use graphs in a similar way so we can dynamically generate a link based on their content.
This will make the Steampipe dashboards much more useful in terms of navigation and user experience.
The text was updated successfully, but these errors were encountered: