-
We have feedback from the Trace view feedback form and some feedback from previous user and customer interviews. This issue is the groundwork to go through it, order it and present it to the team.
-
### What happened?
Set up an Elasticsearch datasource, configure the level field name to "log_level" which is what we are using within Elasticsearch.
When you now explore and view log fields, "log_l…
trexx updated
1 month ago
-
### What happened?
After upgrade to 11.3.0 _Flux_ queries in dashboards stopped working when they were using variables.
### What did you expect to happen?
Dashboards queries work as before.
### Di…
-
When I try to explore datasources it always fail with a TypeError. No idea why this happens.
I have tried versions 0.15.0 - 0.17.0
This is what happens:
```
➜ ~ export GRAFANA_URL=https://graf…
-
Follow up to [#83666](https://github.com/grafana/grafana/issues/83666).
With most of the core now using the `react-router-dom-v5-compat` package, the next step would be to consider switching complete…
-
Add a new float field to the logs generator so we can add e2e coverage for float fields
-
We've created a powerful tool for our users. Now, we need to show them how they can use this amazing app to help them solve issues and explore their data. With Explore Profiles available on Grafana Pl…
-
When `ruler.alertmanager.url` is is set to point to an external Alertmanager, the source URLs sent are always in the format suitable for a Prometheus web UI, not a Grafana explore.
#### To Reproduc…
-
## Description
We added support for specifying an icon when configuring an extension for an extension point. The icons are being displayed in Explore but not yet in the dashboard panel menu. We sho…
-
### What happened?
I was building a query with the builder, adding a `WHERE ... IN ...` clause through `Filter` -> `Any in`, then when the component reloads (either by refreshing the page, collapsing…