Explore Logs: Broken UI when using Explore Logs

[drivvnab]

What happened?

When using the "Explore logs" feature in the open source version of Grafana, I am able to see the initial page which lists all services. When clicking into a specific service I am able to see the logs but when I try and click on the tabbed menu (labels, fields, patterns) nothing happens and I start to see these errors in my browser console:

Too many calls to Location or History APIs within a short timeframe.

Uncaught DOMException: The operation is insecure.
    S useLocation.js:7
    Ke history.js:347
    ht history.js:135
    Ke history.js:340
    push LocationService.tsx:82
    y navigate.ts:117
    b navigate.ts:110
    onChangeTab ActionBarScene.tsx:104
    React 11
    Angular 11
    React 5
    init app.ts:269
    41188 index.ts:33
    Angular 18
    41188 index.ts:32
    Webpack 7

This error message appears on the screen, in the top right as I am redirected back to the "Explore logs" homepage:

Error
parse error : queries require at least one regexp or equality matcher that does not have an empty-compatible value. For instance, app=~".*" does not meet this requirement, but app=~".+" will

Screen recording:

grafana-explore-logs-ui-bug-issue.mp4

What did you expect to happen?

When I click one of the following tabs:

• Labels
• Fields
• Patterns

I expect to see the UI change to reflect the choosen feature.

Did this work before?

I have not been able to get a working version of this.

How do we reproduce it?

1. I have tried both Grafana OSS v11.30 and v11.4.0 (via helm charts 8.5.12 and 8.8.3 respectively)
2. Configure more than one Loki 3 instance as datasources
3. Navigate to the "Explore logs" page
4. Select a service that has incoming logs by clicking "Show logs"
5. Click one of the following tabs; "Labels", "Fields" and "Patterns"
6. View page refuse to load correct UI, error messages in console and possibly redirect to the "Explore logs" home page with an error message on screen

Is the bug inside a dashboard panel?

No

Environment (with versions)?

Grafana: v11.30 and v11.4.0
OS: AKS Kubernetes Linux for host, Mac OS 15.1.1 for client
Browser: Firefox 134.0.1

Grafana platform?

Kubernetes

Datasource(s)?

Loki 3

[gtk-grafana]

@drivvnab thanks for reporting. I am not able to reproduce this locally or in cloud as of yet.

What version of Explore Logs are you running? You can check by visiting: /plugins/grafana-lokiexplore-app in your Grafana instance:

And what specific version of Loki are you running?

[drivvnab]

Hi @gtk-grafana , thank you for looking into this. I am using version 1.0.6 of explore logs and version 3.2.0 of Loki. I have tested this and been unable to reproduce it on Safari version 18.1.1 or Chrome version 131.0.6778.265 . It seems to be just Firefox version 134.0.1 that I am seeing this issue on.

[gtk-grafana]

@drivvnab I am still unable to reproduce this on FF 134.0.1 & 134.0.2, grafana main & 11.4, explore logs main & 1.0.6.
Can you reproduce this in a private window in firefox 134.0.1?

#1014 (comment) was having a similar issue and mentioned it was fixed in the nightly FF, so hopefully updating Firefox solves the problem and you can get back to your logs.

[gtk-grafana]

@drivvnab I'm closing this, it appears to be a conflict with browser extensions, but please re-open if you can reproduce this in a private window.

#1014 (comment)