[
https://issues.apache.org/jira/browse/METRON-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795505#comment-15795505
]
ASF GitHub Bot commented on METRON-622:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/393
There were several examples added to the README. The last one "Run sensor
data end to end" will result in data flowing into an ES index if executed
properly. If you are able to successfully follow the examples then it works.
There is also a "Usage" section that explains how to check the container status
and lists the UIs.
I would argue that the topologies are not moot just because indices are not
installed. What if I'm working on a new parser class? I will more likely be
inspecting the enrichments topic to verify the new parser is working correctly
rather than looking at the indices. That would come later.
Maybe the scope of the PR is different than what you are expecting? This
originally was intended to be a light-weight development environment that
allows a developer to work on or troubleshoot specific parts of the Metron
flow, not an end-to-end solution. We already have something for that (vagrant
quickdev).
> Create a Metron Docker Compose application
> -------------------------------------------
>
> Key: METRON-622
> URL: https://issues.apache.org/jira/browse/METRON-622
> Project: Metron
> Issue Type: New Feature
> Reporter: Ryan Merriman
>
> This is an alternative to the Vagrant quick-dev approach of creating a local
> Metron environment for development and testing. It is intended to be leaner
> and easier to manage. This compose application will contain separate images
> for each of the services that Metron depends on as well as the Metron
> services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
