quickwit-datasource

quickwit-datasource copied to clipboard

Multisearch response unmarshalling loses nano precision from numeric timestamps

1

This issue proves complex to tackle, better keep a description of things here . # The problem : https://github.com/quickwit-oss/quickwit-datasource/blob/8a3c88b0301b4e68f5fc8c8b8c38730dd0d99173/pkg/quickwit/response_parser.go#L296 When creating a data frame from the response to a search...

ddelemeny

Allow using private datasource connect (PDC)

4

I would like to be able to query my quickwit cluster from the grafana cloud. PDC allows you to proxy from grafana cloud into your internal network. The elasticsearch plugin...

camerondavison

- Clean up the client implementation (mostly ExecuteMultisearch and related functions) - Use a shallow unmarshal pass to avoid casting timestamps to float64 when not desired - Adjust dataframe field...

ddelemeny

Plugin freezes on hovering "Ad-hoc statistics" in explore view

6

When hovering over “Ad-hoc statistics”, the plugin freezes the browser. It happens occasionally, and I don't know how to reproduce it. 

fmassot

…lding query.

fmassot

Valid query considered invalid by the editor

3


fmassot

I suspect the state management paradigm used in the query editor is causing some sync issues. When running a query, the old state may flash for a split second.

ddelemeny

Keeping query context while changing query types

1

Example to reproduce the lost of query context: 1. Enter a metrics query (term or date histogram) 2. Execute it 3. Change logs query 4. Go back to metrics query:...

fmassot

Consider template variables valid in the query editor

1

It's possible to use variables in a dashboard. The query editor should consider `$query`, `${query}`, `${query:raw}` as a valid syntax. 

fmassot

- DataSource.fields.values only implements Vector interface prior to grafana 10.0

ddelemeny