-
Notifications
You must be signed in to change notification settings - Fork 6
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
Explore show live logs mode #83
Comments
Hi @yuriydzobak ! The feature was added in the release. Could you please check it? I close the issue. If you find any problems with new release please reopen the issue |
@dmitryk-dk I've just checked, and it works perfectly! |
I think I've found the bug. The "Clear logs" button breaks loading the new log entries. Screen.Recording.2024-11-07.at.16.51.59.mov |
I also found a strange bug. The live mode ignores my filter for some reason. Screen.Recording.2024-11-07.at.16.57.34.mov |
Could you check the request via |
Ok, will check, maybe miss something in the handlers |
Does it support live logs in the grafana logs dashboard? |
I am not sure that Grafana supports it on the dashboard, either. Explore works. Need to check. If it is, we will make changes |
MQTT supports it in the dashboard while LOKI doesn't and I only want to use one log datasource and I am currently using LOKI. Even when both support live logs in the explorer tab. |
Ok, need to check and discuss how to better implement this feature |
Does it work with a dashboard to have live logs? |
Hi @archef2000 ! At that moment live logs only work in the explore mode. Can you check this folder ? Here, you can find any docker installations and make files that help you run them. |
Hi,
As VictoriaLogs ahs live tailing mode
It would be nice if plugin will have this feature as well
Loki has it in their plugin
For example open loki play
and it expand ui in explore mode
Maybe Loki has a refresh mode instead of a live tailing mode like VictoriaLogs. However, it would be a useful feature for debugging apps in live mode.
The text was updated successfully, but these errors were encountered: