Skip to content
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

Document how to get log context #72

Closed
mrdavidlaing opened this issue Jul 23, 2013 · 6 comments

Comments

Projects
None yet
3 participants
@mrdavidlaing
Copy link
Contributor

commented Jul 23, 2013

relocated from #68

Can’t find an easy way of getting the context of the log. Usually the thing that helps identify the issue is actually on the lines above below. Would be nice if could pull back say the 10 lines above and below. Can we do this?

Document how to edit the filters to show all the logs around a particular log

@ghost ghost assigned mrdavidlaing Jul 23, 2013

@mrdavidlaing

This comment has been minimized.

Copy link
Contributor Author

commented Jul 25, 2013

One option is to change your search filter to run from 1 second before to 1 second after the specific event in question.

In addition to being a hassle, this is tends to return too much information; but it is at least a start

@mrdavidlaing

This comment has been minimized.

Copy link
Contributor Author

commented Jul 25, 2013

I've raised an upstream issue to see if its possible to implement a more elegant solution

elastic/kibana#275

@mrdavidlaing

This comment has been minimized.

Copy link
Contributor Author

commented Jul 25, 2013

Relocated from #68

@dpb587

This comment has been minimized.

Copy link
Contributor

commented Jul 25, 2013

Building off the Loggly screenshot... I'd like to see if it's possible to use the query/hash for panel inputs (i.e. ?timepicker[start]=2013-07-25T07:50:12&timepicker[end]=2013-07-25T07:50:12. If it is, we could just add some sort of link to the log message to open a new dashboard in a new window with the time range. Another usage could be a ?table[highlight]=jR4iXPDwQmqGf_P4k0Jc4g which highlights a specific log message.

@sopel

This comment has been minimized.

Copy link
Contributor

commented Aug 6, 2013

Moved to Icebox due to upstream dependency.

@sopel

This comment has been minimized.

Copy link
Contributor

commented Jan 22, 2015

Closed as Won't Fix due to project being retired to the CityIndex Attic.

@sopel sopel closed this Jan 22, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.