Auto reload messages

[schickling]

I think it would be a huge improvement if there'd be an option to enable auto reloading for messages and the activity graph.
Perhaps an input field for the refresh interval would also be nice.

[lennartkoopmann]

Thanks. Scheduled for the new web interface.

[schickling]

Great 👍

[SjonHortensius]

interface-wise I think the best method of implementing this would be adding an icon next to "Highlight messages from today" ( I initially expected that button to toggle refreshing )

[proptiger-com]

When streams auto refresh is coming ???

[Behner]

Is this coming soon?

[kroepke]

we can add a simple auto refresh to the page, however the messages cannot be loaded via ajax yet, so refreshing the entire page will not be user friendly, because it might reload while you interact with it.

I'll still leave this in for 0.21 because so many people ask for it all the time.

[SjonHortensius]

Fetching the messages through AJAX would be preferable but is not a requirement. It is doable to fetch the current page through XHR; and get the specific dom-nodes and replace them in the current page unobtrusively. This removes the need to reload the page which is indeed somewhat unfriendly

[kroepke]

well, the problem is that the code really isn't set up for this right now.
Especially all the charts will not simply be updated, so we need to improve the infrastructure for a proper solution.
I'm not sure we want to go the pjax route, but we'll figure out something out :)

[jakepin21]

has the auto reload feature been added and where can i find it?
thx

[rakodev]

+1

[mwhooker]

Looking forward to this

[tomahock]

+1 this is would be awesome

[nmarshall-cst]

+1

[jshearer]

This is a vital feature to me. +9999

[psteyn]

+1 this would be really useful to us.

[vladimir-lu-work]

Is this something where SSE would be helpful to implement, given that it's been around in HTML5 for a bit now?

+1

[lawre]

+1 here as well. This is the only reason why we haven't ditched Splunk yet

[jthomas332]

+1 Would be a very valuable addition to the interface.

[teon]

+100 - i feel graylog is ok for looking at the past - but I want to use it to look at the log "present" state and without feature like tail -f it's not possible.

[traviscrist]

Is this issue ever going to be resolved?

Its existed since 2013 and is a key feature for any logging framework in a live server environment.

[zexxon]

We have made several major improvements to the UI in the upcoming 1.1 release, which is one of the reasons we held off on implementing this feature. Will scope for the next maintenance/minor release and see if we can get it in post 1.1. It should be interesting to see how it performs vs. Kibana and Splunk since we are able to buffer log messages via the app server.

[traviscrist]

That would be great to see this in the next release. One of our teams biggest complaints with using graylog is the inability to access live logs. If we can resolve that issue via a version update our users would be in great shape.

Thanks!

[hernandesbsousa]

+1

[thenetexperts]

any update on this one?

[shakalandy]

Some more beer for this one ;)

[HerrmannHinz]

+1
where should i donate?

[jshearer]

Jeez I've been following this ticket for a loooong time. Still nothing. D'oh

[tomahock]

It was supposed to be in 1.2 version:
https://twitter.com/_lennart/status/593195512414613504

[lennartkoopmann]

@tomahock it is on the roadmap for 1.2 but we cannot guarantee yet that it will definitely make it in.

We understand that this is a frequently requested feature but we want to get the implementation right and not rush this. There are many ways to shoot your own foot with this so it might take a bit more time.

[xargs-P]

+1 :-)
... and a 1,000,000 Internet points to Graylog when they get this in.

[tomahock]

@lennartkoopmann we love feedback :D

[hwinkel]

+1

[umatomba]

+1 )))

[Brennwert]

+1

[bymodude]

+1

I just spent a day getting log messages into Gelf Format and into the Graylog2 server, due to this issue and seeing that its been open for 2 years (and therefore its clearly not a priority for the graylog2 team?), I am probably just going to throw that away and go Kibana/Splunk etc instead.

I don't know what peoples use cases are, but for me this is such a basic thing that I just assumed this would of course be possible.

Seriously I am certain this costs you hundreds if not thousands of potential users. I seldomly provide feedback like this when features are missing, normally I just move on, I guess others came across this glaring omission and just moved on similarly.

[dedene]

This is also one of the only reasons we are not using Graylog (yet).

+1

[jshearer]

Yet again I would like to add my two cents here. Add this already

On Sat, Oct 24, 2015 at 2:48 PM Peter Dedene notifications@github.com
wrote:

This is also one of the only reasons we are not using Graylog (yet).

+1

—
Reply to this email directly or view it on GitHub
#133 (comment)
.

[sv72]

Was very enthousiastic at first when I just installed GrayLog as a possible replacement of Splunk. That was until I found out that there's no (near) realtime view. This is what we use a lot in our current Splunk setup for debugging issues on our webshops.

Seeing that this feature request already exists for 2,5 years I don't think I'm going to wait for this.
Too bad though, I think the concept of Graylog is pretty great.

[brandongalbraith]

Hey all! I'm not affiliated with Graylog at all, but this is pretty disheartening. Not that the feature isn't here yet, but because of every +1 or complaint here without a pull request.

If you're signaling interest for a feature (+1), fine. But complaining that an open source project that you're providing no contribution to should prioritize a feature because you want it? That is not what open source is about.

Graylog is pretty damn incredible for an open source project. And it is far better than alternatives (ie Splunk) considering the cost. If someone from Graylog reads this, I'd encourage you to lock this issue and address this feature as you'd like

[lennartkoopmann]

Everyone, it looks like we will have this in Graylog v2.0:

[dedene]

@lennartkoopmann Awesome! 👍

[dennisoelkers]

Implemented in Graylog2/graylog2-server#1783.