influxdata / influxdata/influxdb

Grafana search option does not work with Influx Cloud Serverless

Open
#25,971 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
31.7k
Forks
3.7k
Avg merge
13h 37m
Merged PRs (30d)
8

Description

__Steps to reproduce:__

1. Create a database/bucket in InfluxDB Cloud Serverless Storage Engine Version 3
2. add Influx to Grafana as a datasource (I tested with Grafana Cloud (Free), Grafana v10.2.4)
3. Create a new dashboard and try to use the search option.

__Expected behaviour:__
Grafana proposes tagnames that start with the substring that was inserted in the search field.

__Actual behaviour:__
When selecting "a measurement" in grafana, all the options are shown, so It is able to get all the measurements in the database.
However, when searching for a substring of a measurement, the result is empty:
![Image](https://github.com/user-attachments/assets/f542cd54-2d42-455e-94ce-2850eaf06533)
I tried the same influx Data source in 2 different grafana versions, same results in both. I added other Influx (V2) datasources to grafana. With these influx versions, the search option works.

__Environment info:__
it's an influx cloud, not sure what I should give as info here

__Config:__
no config changes

__Logs:__

__ExtraInfo:__
I started here:
https://community.influxdata.com/t/grafana-search-option-does-not-work-with-influx-cloud-serverless/56149

Contributor guide

Open the contributing guide

Research direction

No repository file, test, or entry point is identified. Start by reproducing the measurement search with InfluxDB Cloud Serverless through Grafana, then trace the relevant query path; done means substring searches return the matching measurement or tag names as expected.

Written by the indexing model from the issue text.

Assessment

Domain
databases, observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.