[GH-ISSUE #131] Persistent Log Display #103

New issue

Open

opened 2026-02-26 05:31:20 +03:00 by kerem · 9 comments

kerem commented

2026-02-26 05:31:20 +03:00

Owner

Originally created by @sitz on GitHub (Sep 19, 2014).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/131

I was wondering if we can allow the logs on screen to persist unless explicitly told to clear it up.
If, during analysis, someone accidentally refreshes the page, everything is gone as of now!

Can you suggest a good way to load a configurable number of lines from the file (something like tail -n 1000) whenever the web page is refreshed or, opened up for the first time?
Everything else displayed in real time works for me.

Originally created by @sitz on GitHub (Sep 19, 2014). Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/131 I was wondering if we can allow the logs on screen to persist unless explicitly told to clear it up. If, during analysis, someone accidentally refreshes the page, everything is gone as of now! Can you suggest a good way to load a configurable number of lines from the file (something like `tail -n 1000`) whenever the web page is refreshed or, opened up for the first time? Everything else displayed in real time works for me.

kerem commented

2026-02-26 05:31:21 +03:00

Author

Owner

@jansegre commented on GitHub (Oct 1, 2014):

+1 on that!
I know the main feature of log.io is log aggregation, but for the time being lack of a history is why I'm still not using it. Most of the time I miss aggregation is when tracking down a specific error which is a mess if the logs are distributed.
I may try to add this feature in the near future if I get the time for it. I'll open a PR if I do.

@jansegre commented on GitHub (Oct 1, 2014): +1 on that! I know the main feature of log.io is log aggregation, but for the time being lack of a **history** is why I'm still not using it. Most of the time I miss aggregation is when tracking down a specific error which is a mess if the logs are distributed. I may try to add this feature in the near future if I get the time for it. I'll open a PR if I do.

kerem commented

2026-02-26 05:31:21 +03:00

Author

Owner

@ssimono commented on GitHub (Dec 3, 2014):

@ssimono commented on GitHub (Dec 3, 2014): +1

kerem commented

2026-02-26 05:31:21 +03:00

Author

Owner

@hanneshal commented on GitHub (Dec 4, 2014):

Just a note: A simple local storage mechanism (save+read+delete) might be the solution with the smallest footprint without turning log.io to logstash.

@hanneshal commented on GitHub (Dec 4, 2014): Just a note: A simple local storage mechanism (save+read+delete) might be the solution with the smallest footprint without turning log.io to logstash.

kerem commented

2026-02-26 05:31:21 +03:00

Author

Owner

@arthurlutz commented on GitHub (Jan 19, 2015):

@arthurlutz commented on GitHub (Jan 19, 2015): +1

kerem commented

2026-02-26 05:31:21 +03:00

Author

Owner

@Alex30555 commented on GitHub (Jan 26, 2015):

@Alex30555 commented on GitHub (Jan 26, 2015): +1