Create a helper entity with either associations or attributes that can be used to constrain your chart results. I have found that attributes work well for dates (I typically use 2 attributes to enable users to select a month, year, week, etc.) while associations are better suited for values where users may want to select multiple values (states, resources, etc.)
Once the entity is created, you can create an instance each time a chart is needed. Make a page that displays the newly created object and enables the selection on reference values or entity values. After the values are selected, you can then create a microflow that is called from a button on the page. Your entity can be passed to the microflow, and you can use the association values and entity values to constrain your results.
You should consider making your helper entity non persistent or, if its persistent, make sure you have the capability to view and delete the list of these objects so that you don't end up with a large number of unneeded objects in your database.
Hope that helps,