-
Notifications
You must be signed in to change notification settings - Fork 7
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
Data persistence issue #20
Comments
I'm having this same issue. It seems like it's duplicating or readding steps on panel refresh without clearing the existing data. This happens specifically when I change the dashboard parameters. |
Thanks for opening this issue! I will try to reproduce this during the day and open a fix prior to the next release. |
Thanks @mckn, let me know if you need any help! |
I think it has do to with the generated key for each component which makes it append instead of re-rendering the bar. Trying to verify it aws. |
@jasonlanderson can you please provide some test information? Can you share anything regarding your dashboard that can help me reproduce this? |
I think I managed to reproduce it and have a fix in #32 |
Awesome, thanks @mckn! Is there an easy way I can update the funnel plugin in our grafana instance to test it out? We used |
Would also appreciate guidance on how to update. |
I am encountering a recurring issue with the funnel chart, where data seems to "linger" when changing the dashboard's parameters (or when hitting the "refresh" button). Here are the details:
Environment:
Grafana version: 10.4.2
Browser: Chrome and Safari (Issue reproduced in both)
Steps to Reproduce:
The funnel chart retains (some of the) data from the first run and combines it with data from the second run.
The only way to clear the data and start fresh is to refresh the entire page. Clicking the "refresh dashboard" button does not resolve the issue.
The screenshot below shows for example the "limit_results" step that is stacked over and over again. So much so, that the funnel even covers the visualization below...
The text was updated successfully, but these errors were encountered: