Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ templating ] [ Query type ] text : value pairs dismissed with duplicate value #55154

Open
Satyam1210 opened this issue Sep 14, 2022 · 1 comment
Labels
area/dashboard/templating prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. prio/future Used by the dashboards squad to prioritise their backlog team/grafana-dashboards Dashboards squad type/bug

Comments

@Satyam1210
Copy link

Satyam1210 commented Sep 14, 2022

I am trying to use the Query Type variable with a regex .*key=\"(?<text>[^\"]+)\"} (?<value>[^\\ ]+).*
The result of the query is unique keys with multiple keys having same value.
However, with regex, only the entries that have unique values is shown, rest all are dismissed.

For example:
Entries without applying regex:

{key="2022-09-15 01:00:00 <-> 2022-09-15 11:30:00"} 48600 1663147810000
{key="2022-09-09 22:00:00 <-> 2022-09-11 04:30:00"} 120600 1663147810000
{key="2022-09-10 22:00:00 <-> 2022-09-12 04:30:00"} 120600 1663147810000
{key="2022-09-11 22:00:00 <-> 2022-09-13 04:30:00"} 120600 1663147810000
{key="2022-09-12 22:00:00 <-> 2022-09-14 04:30:00"} 120600 1663147810000
{key="2022-09-08 22:00:00 <-> 2022-09-10 04:30:00"} 120600 1663147810000
{key="2022-09-14 01:00:00 <-> 2022-09-15 11:30:00"} 135000 1663147810000

Entries with regex:

2022-09-15 01:00:00 <-> 2022-09-15 11:30:00
2022-09-09 22:00:00 <-> 2022-09-11 04:30:00
2022-09-14 01:00:00 <-> 2022-09-15 11:30:00

Expected behaviour: Show all unique keys no matter what the values are
Actual behaviour: Keys are dropped with same values

This can be reproduced with any query that produces entries with unique key names, but with same values.

Based on this #40414, there was similar issue in Custom type variable, which was fixed in v8.2.2. However it still does not work for Query type.

Grafana v 8.3.4
Datasource : Prometheus

Any help is greatly appreciated !

Thanks

@mellieA mellieA added area/dashboard/templating triage/needs-confirmation used for OSS triage rotation - reported issue needs to be reproduced labels Sep 23, 2022
@dprokop
Copy link
Member

dprokop commented Sep 26, 2022

I can confirm this works as described in the issue. I can't promise when this is going to be fixed, but I'm moving this into our backlog.

@dprokop dprokop added prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. and removed triage/needs-confirmation used for OSS triage rotation - reported issue needs to be reproduced labels Sep 26, 2022
@natellium natellium added the team/grafana-dashboards Dashboards squad label Jun 23, 2023
@natellium natellium added the prio/future Used by the dashboards squad to prioritise their backlog label Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dashboard/templating prio/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough interest in it. prio/future Used by the dashboards squad to prioritise their backlog team/grafana-dashboards Dashboards squad type/bug
Projects
Status: 📝 Backlog
Development

No branches or pull requests

4 participants