[Feature][Dashboard] Remove the warning when there's no data

[Startrekzky]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Use case

As a user, when I see the initial status of any dashboard in Grafana, I can see the warning signs, which look like an error page.

I want to see more user-friendly dashboards when no data is collected.

Description

It is mainly caused by the multi-value filter. When no data is collected, the SQL becomes

project in ()

which caused the syntax error.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[Startrekzky]

Analysis

The reason for this problem is that I enabled 'multi-value options' in the filters on the dashboard. When using the multi-value filter, I have to use the in word in SQL, such as

project_name in ($project)

because when multi values (a, b, c) are selected. The SQL will be converted to

project_name in ('a','b','c')

However, if none of the values is selected, the SQL would be

project_name in ()

which will cause a syntax error.

Solutions

I can think of two possible solutions.

1. Keep using filters that enable multi-value options. In this direction, we'll need to find another way to write the SQL.
2. Stop using filters that enable multi-value options. In this direction, we'll need to replace all the in keywords with = keywords in the queries, such as

project_name = '$project'

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.

[github-actions]

This issue has been automatically marked as stale because it has been inactive for 60 days. It will be closed in next 7 days if no further activity occurs.

[github-actions]

This issue has been closed because it has been inactive for a long time. You can reopen it if you encounter the similar problem in the future.