example: elasticsearch, kibana, and filebeat ~elk #272
Conversation
| @@ -0,0 +1,46 @@ | |||
| # converge-elk | |||
|
|
|||
| A Converge example that sets up a single node docker-based [ELK](https://www.elastic.co/webinars/introduction-elk-stack) stack. | |||
There was a problem hiding this comment.
maybe could you explain what "ELK" stands for the first time you use it?
|
|
||
| ### Vagrant | ||
|
|
||
| In the [Vagrantfile](./Vagrantfile), change the file provisioner source to point to a version of the converge binary built with the `linux/amd64` OS architecture. |
There was a problem hiding this comment.
Could you provide step-by-step instructions? Like:
- Browse to the releases page (w/ link)
- Unzip it to
x/y/z - Point
configValuetox/y/z
There was a problem hiding this comment.
Better yet, could the code in this example be extended to do that for the user? The fewer steps the better!
There was a problem hiding this comment.
we'll want to update this again when https://github.com/ChrisAubuchon/vagrant-converge is ready but I went ahead and scripted out the converge download as part of vagrant provisioning. now you only have to run vagrant up.
| After provisioning completes, you should be able to access the url for the Kibana interface by running: | ||
|
|
||
| ```shell | ||
| echo "http://$(terraform output ip):5601/" |
There was a problem hiding this comment.
why is this using echo? That won't open a browser or anything.
There was a problem hiding this comment.
I know. It is just a command that provides an easy way to access the full url for kibana so that you can paste it in your browser. Would changing the sentence above to something like
"After provisioning completes, you should be able to retrieve the url for the Kibana interface by running:"
make it more clear?
There was a problem hiding this comment.
My email got lost, looks like. Yes, that sounds perfect!
There was a problem hiding this comment.
nope, not lost but I guess you do lose the position in the thread when replying via email
|
|
||
| ## Graphs | ||
|
|
||
|  |
There was a problem hiding this comment.
need an explanation of this graphic, please
|
Yeah, that would be perfect! On 20 Sep 2016, at 8:46, Ryan Eschinger wrote:
|
ryane
force-pushed
the
feature/example-elk
branch
from
878d3c6 to
3b77be3
Compare
ryane
force-pushed
the
feature/example-elk
branch
from
3b77be3 to
86bb814
Compare
|
I believe all comments were addressed. ready for review again |
| params = { | ||
| user-name = "{{param `user-name`}}" | ||
| } | ||
| depends = ["module.packages/task.epel-install"] |
There was a problem hiding this comment.
depending on a task inside another module is unsupported. It works, but it probably won't in the future. I thought we had disallowed it, actually. Depending on module.packages gets you the same result.
| task "filebeat-install" { | ||
| check = "yum list installed filebeat" | ||
| apply = "rpm -ivh https://download.elastic.co/beats/filebeat/filebeat-1.3.0-x86_64.rpm" | ||
| depends = ["module.docker/task.docker-install"] |
There was a problem hiding this comment.
This should be module.docker too
| docker.image "elasticsearch-image" { | ||
| name = "elasticsearch" | ||
| tag = "2.4.0" | ||
| depends = ["module.docker/task.docker-start"] |
| docker.image "kibana-image" { | ||
| name = "kibana" | ||
| tag = "4.6.0" | ||
| depends = ["module.docker/task.docker-start"] |
There was a problem hiding this comment.
module.docker.
These will clean up your graph as well.
There was a problem hiding this comment.
fixed, tested, and updated graph image
|
all green |
example: elasticsearch, kibana, and filebeat ~elk
No description provided.