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

logstash config in docs out of date #302

Closed
rueberger opened this issue Mar 17, 2018 · 4 comments
Closed

logstash config in docs out of date #302

rueberger opened this issue Mar 17, 2018 · 4 comments
Milestone

Comments

@rueberger
Copy link

Hi there - great work with this lib. Just discovered it and it's changing my life.

Also just getting started with the whole ELK thing, logstash 6.2.2 doesn't like the example config in the docs, crashes. The options for the elasticsearch output plugin appear to have changed drastically https://www.elastic.co/guide/en/logstash/current/plugins-outputs-elasticsearch.html.

Any ideas on what might work now?

@rueberger
Copy link
Author

This filter seems to do the trick:

filter {
  json {
    source => "message"
  }
}

But what I'm still missing is how I can take advantage of the nice tree structure afforded by eliot in kibana

@itamarst
Copy link
Owner

I'll fix the docs, thanks.

The Kibana UI lets you sort columns. Typical pattern I've done is:

  1. Find all messages with specific task_uuid.
  2. Sort by task_level. Depending on version of Kibana/ES this is more or less tricky, basically as long as it realizes it's a list of integers it should do the right thing. If it decides it's a strings or something it messes up.

If you succeed at sorting, the result is visually like a tree.

@itamarst
Copy link
Owner

What's your use case for Eliot, by the way? I.e. what kind of application?

@itamarst itamarst added this to the 1.4.0 milestone Mar 17, 2018
@rueberger
Copy link
Author

Thanks for the tip I'll have to give that a try - I'll report back to this issue if I figure out something good. Also I should add that the filter above only parses logs produced by Message, one would need to add filters for all used action types to capture those as well.

This is for a data munging app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants