Ah, now I get it. Thanks for the clarification.
I can't think of a way to stop that line chart from doing the initial rendering of all of the data. At least not in a way that makes a lot of sense. I can really only think of two possible solutions, but they're both bad.
You could save the dashboard in a default state with 1 filter applied, the most common filter (assuming you have one), so that at least for some use cases that initial render wouldn't be a wasted query. But then users would have to select the other filter they actually do want, and unselect the default one, so it's not great.
The only other thing I can think of would be worse. Basically, apply a filter that matches nothing, and have it enabled by default. This way the initial render will have 0 results, and nothing would be rendered. That doesn't really solve the load on the Elasticsearch side though, as the query would still happen. Also, when the dashboard initially loads, it'll look empty.
Is there a reason you don't just create 4 different dashboards, 1 for each filter, and simply start with the dashboard view that you want?