mirror of
https://github.com/NarrativeScience-old/log.io.git
synced 2026-04-25 17:15:52 +03:00
[GH-ISSUE #61] Show history #46
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/log.io-NarrativeScience-old#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kosmasgiannis on GitHub (Mar 31, 2013).
Original GitHub issue: https://github.com/NarrativeScience-old/log.io/issues/61
In the previous version of the software, there was the option to show some lines of the file logged previously. It was a very useful feature and I hope it will come up again in a future release.
@msmathers commented on GitHub (Apr 15, 2013):
I would like to reintroduce history screens, however I think it warrants an architectural discussion. One of the tenants of v0.3.x is that the server/client has to work with 3rd party harvesters such as logstash, and therefore the server/client can't rely on the ability to access logs directly from their source file.
Therefore I see two options to address this:
Any thoughts?
@gu3st commented on GitHub (Apr 15, 2013):
I just felt that the history was the "killer feature" of log.io (for me at least). The streaming view isn't always useful as a lot of my debugging is "work work work.. oh, something broke, what do logs say" then going and opening log.io to look at what failed.
I'm indifferent as to the actual implementation as I only use the stock harvester/server, although knowing that I could theoretically build in my harvester into a node or PHP app is fairly interesting.
@jochenonline commented on GitHub (Apr 16, 2013):
Exactly!
Am 15.04.2013 21:10 schrieb "Dustin Dawes" notifications@github.com:
@zeflash commented on GitHub (May 2, 2013):
Crap. I upgraded without really looking because I though getting rid of forever was nice - and now the thing I used the most is gone. Bummer. I already spent way too much time to upgrade, now I should downgrade?
aaarggghhhh!
@ddarbyson commented on GitHub (Jun 29, 2013):
It seems natural to have history, without it Log.io feels incomplete. Reviewing history is critical to determine how the server was preforming while away. Catching application errors in real-time is only half the battle.
I really hope to see Log.io introduce History w/ Filters.
@nuomi commented on GitHub (Oct 6, 2013):
vote on this one!
@Removed-5an commented on GitHub (Dec 9, 2013):
upvote!
@Removed-5an commented on GitHub (Dec 10, 2013):
Looks like this project isn't very active anymore, anyone up for forking it?
@Dual-Boot commented on GitHub (Dec 10, 2013):
Hi,
It seems there is only 2 persons to do the job.
I think there is no need to fork but any people who has skills
for this project could join it.
On my side, I can made test but I am not a dev.
Do not forget that is an Open Source project.
Best regards,
/
/-------------------------------------
| Guy CARRÉ |
| ************* |
| PostMaster - WikiMaster - SysAdmin |
| |
| "Free Your Mind. Think Open Source" |
| april.org |
| |
|_____________________________________|
----- Mail original -----
De: "5an1ty" notifications@github.com
À: "NarrativeScience/Log.io" Log.io@noreply.github.com
Envoyé: Mardi 10 Décembre 2013 11:06:41
Objet: Re: [Log.io] Show history (#61)
Looks like this project isn't very active anymore, anyone up for forking it?
—
Reply to this email directly or view it on GitHub .
@zeflash commented on GitHub (Dec 10, 2013):
It's the concept of open source on github: fork it, tweak it. If you're up to it.
I've reverted to pre 0.3 myself, it was easier. Many forks with regex filtering are available.
@Dual-Boot commented on GitHub (Dec 10, 2013):
Too much fork kill the fork ;-)
There is a need to focus on one project or 2-3 forks .
If there is more thant 10 forks why do not contribute directly on the first project ?
That is a real question.
Regards,
/
/-------------------------------------
| Guy CARRÉ |
| ************* |
| PostMaster - WikiMaster - SysAdmin |
| |
| "Free Your Mind. Think Open Source" |
| april.org |
| |
|_____________________________________|
----- Mail original -----
De: "Alex" notifications@github.com
À: "NarrativeScience/Log.io" Log.io@noreply.github.com
Cc: "Dual-Boot" guycarre@free.fr
Envoyé: Mardi 10 Décembre 2013 12:11:32
Objet: Re: [Log.io] Show history (#61)
It's the concept of open source on github: fork it, tweak it. If you're up to it.
I've reverted to pre 0.3 myself, it was easier. Many forks with regex filtering are available.
—
Reply to this email directly or view it on GitHub .
@Removed-5an commented on GitHub (Dec 10, 2013):
Unfortunately I'm not skilled enough to adjust it myself. Anyone up for the task and willing to contribute to the project?
@Dual-Boot commented on GitHub (Dec 10, 2013):
I am not a dev, but I can make tests.
I already have a log.io instance working.
/
/-------------------------------------
| Guy CARRÉ |
| ************* |
| PostMaster - WikiMaster - SysAdmin |
| |
| "Free Your Mind. Think Open Source" |
| april.org |
| |
|_____________________________________|
----- Mail original -----
De: "5an1ty" notifications@github.com
À: "NarrativeScience/Log.io" Log.io@noreply.github.com
Cc: "Dual-Boot" guycarre@free.fr
Envoyé: Mardi 10 Décembre 2013 14:10:49
Objet: Re: [Log.io] Show history (#61)
Unfortunately I'm not skilled enough to adjust it myself. Anyone up for the task and willing to contribute to the project?
—
Reply to this email directly or view it on GitHub .
@zeflash commented on GitHub (Dec 10, 2013):
@Dual-Boot I agree with you, but it's up to the original project managers to accept contributions. If they feel those contributions do not go towards the solution they want to provide, they are free to refuse them.
Their vision is more real-time monitoring, and less relying on actual files. It makes sense it some cases (monitoring a lot of machines) but it's not that interesting for us (or me at least) when I just need to remote-check & monitor one server.
I feel it's just a matter of priorities here. The original dev(s) might have other things on their plate at the moment. I can live with pre 0.3 even if refresh is a bit buggy sometimes. If history actually makes it in 0.3 (I would up-version it to 0.4 in that case ;) ) then even better, I'll upgrade again!
@msmathers commented on GitHub (Aug 1, 2014):
This is being worked and will likely be included in the next release.
@LaKing commented on GitHub (Aug 6, 2014):
That is great news. I also miss that feature atm.
@m00gl3 commented on GitHub (Sep 8, 2014):
I wanted to add my request for this very important feature. If I close my browser all the log history is gone.
Do you have an estimate as to when this new release will be out?
Also, what is the latest version to have this feature?
@wadevogt commented on GitHub (Mar 11, 2015):
+1 for this feature... Love the app, but it would be so much more useful if I could see the history.
@dhatawesomedude commented on GitHub (Apr 11, 2015):
@msmathers any possible timeline for that next release?
@cooksimo commented on GitHub (May 18, 2015):
+1 this would be really useful, any updates?
@nelsonomuto commented on GitHub (Sep 2, 2015):
+1
@Ben1980 commented on GitHub (Feb 9, 2016):
+1
@ralphotowo commented on GitHub (Feb 9, 2016):
+1
@franciskim commented on GitHub (Jun 25, 2016):
+1
@tuhoanganh commented on GitHub (Dec 23, 2016):
+1
@rodrigoblz1 commented on GitHub (Apr 17, 2017):
+1
@lalitprasanth commented on GitHub (Feb 12, 2018):
+1
@anvial commented on GitHub (Jul 6, 2018):
+1
@MagicMagnate commented on GitHub (Aug 28, 2018):
+1
@RafaelMiquelino commented on GitHub (May 13, 2020):
Is this feature currently implemented? If so, how can I enable it? Thanks.
@alv000h commented on GitHub (Jun 16, 2020):
Use of redis for persistence / history purposes is not an option?
@zhouguangming commented on GitHub (Jan 27, 2021):
+1
@briangt commented on GitHub (Oct 22, 2021):
+1