[
https://issues.apache.org/jira/browse/METRON-622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15795748#comment-15795748
]
ASF GitHub Bot commented on METRON-622:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/393
The logs for this container are written to /usr/share/apache-storm/logs/
instead of /var/log/storm. That's probably why you don't see them. That's
just the way they configured it in this Docker image but I'm sure it's easy
enough to change.
You can also view the logs through the Storm UI. The one catch is that
once you drill into a specific log (will give you a 404 initially) you have to
replace the ip address (it's an internal Docker container IP and not accessible
outside of the Docker host) with the Docker machine ip.
I agree those are nice add ons. This is a pretty significant PR as is so I
tried to keep the scope as small as possible while still providing the ability
to flow data end to end. The first one isn't too bad and I think it fits
nicely into a separate PR. The 2nd one is trival, I'm fine with configs being
loaded initially and will make that change. The 3rd one might be easy, you
have the environment setup so maybe you could experiment with it (I will help)?
The last one will definitely require some work and should be a separate PR.
> 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)
