Loss of autorefresh configuration with Real-time shift auto-select enabled

[matteoberts]

Hi there,

I wanted to report a bug regarding a component after updating Grafana to version 10.4.0 and utilizing the Real-time shift auto-select functionality. It seems that the board is losing its autorefresh configuration when the shift changes occur.

Steps to reproduce

1. Update Grafana to version 10.4.0.
2. Add grafana-shift-selector component and configure 2 or more shifts
3. Enabled the Real-time shift auto-select functionality.
4. Observe the component's behavior during shift changes.

Expected behavior The autorefresh configuration should persist during shift changes.

Actual behavior The autorefresh configuration seems to be lost when the shift changes occur. On shift change, board is not refreshing.

This issue seems related to one mentioned here. This issue impacts our workflow significantly, as it disrupts the continuous monitoring process during shift changes. Please let me know if further information or clarification is needed.

Thank you for your attention to this matter.

Best regards, Matteo

[isaozler]

Thanks @matteoberts,

Thanks for the detailed report. This issue was fixed in the latest release, but apparently, this is reoccurring with Grafana 10.4.0. I will get back to this once I have looked into it.

[matteoberts]

Thank you for the update, @isaozler. I appreciate your attention to this matter. Do you have any estimate on when the fix will be released? Knowing this would be extremely useful for us to decide whether to wait for the update of the plugin or rollback Grafana version.

[isaozler]

@matteoberts, can you test if version 0.1.6 fixes this issue?

[matteoberts]

Hi @isaozler ,

Thank you for your message.

I've tested version 0.1.6 of the plugin as per your request (static shift mapping mode). Initially, I updated the plugin to version 0.1.6 on Grafana version 10.4.0 (the version where the original issue occurred). However, I encountered an issue where the plugin couldn't be found. I've attached screenshots for reference.

Subsequently, I updated Grafana to version 10.4.2. After this update, I was able to locate the plugin within Grafana. However, I'm encountering errors with it. I've also attached screenshots of these errors.

I'd like to share the error log that occurs during shift changes (the path parameter '&refresh=' has disappeared from the URL).

Please let me know if there are any additional steps I should take. Once again, thank you so much for your support.

Best, Matteo

[matteoberts]

Hi @isaozler ,

I hope this message finds you well.

I'm writing to inquire if there have been any updates regarding the issue I reported. Currently, the anomaly requires us to manually refresh the dashboard at every shift change. This is quite a blocker, and we might have to consider an alternative solution if the problem isn't resolved.

Any information or progress you could share would be greatly appreciated.

Thank you for your assistance.

Best regards, Matteo

[isaozler]

Hi @isaozler ,

I hope this message finds you well.

I'm writing to inquire if there have been any updates regarding the issue I reported. Currently, the anomaly requires us to manually refresh the dashboard at every shift change. This is quite a blocker, and we might have to consider an alternative solution if the problem isn't resolved.

Any information or progress you could share would be greatly appreciated.

Thank you for your assistance.

Best regards, Matteo

Hi @matteoberts, I'm sorry to hear that. I'll look into your issue again and get back to you as soon as possible. Your report for the 12th of April is still relevant, I suppose?

[matteoberts]

Hi @isaozler , I hope this message finds you well. I'm writing to inquire if there have been any updates regarding the issue I reported. Currently, the anomaly requires us to manually refresh the dashboard at every shift change. This is quite a blocker, and we might have to consider an alternative solution if the problem isn't resolved. Any information or progress you could share would be greatly appreciated. Thank you for your assistance. Best regards, Matteo

Hi @matteoberts, I'm sorry to hear that. I'll look into your issue again and get back to you as soon as possible. Your report for the 12th of April is still relevant, I suppose?

Hi @isaozler ,

Thank you for your prompt response.

Yes, the report and the information shared on the 12th of April are still valid. I remain at your disposal for any additional information you might need.

The plugin is very useful and functional, and we would like to keep it, provided the anomaly is resolved.

Thanks again for your assistance.

Best regards,
Matteo