[
https://issues.apache.org/jira/browse/METRON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15644797#comment-15644797
]
ASF GitHub Bot commented on METRON-541:
---------------------------------------
Github user merrimanr commented on the issue:
https://github.com/apache/incubator-metron/pull/347
@mmiklavc Good question. We definitely need to exclude the SLF4J bindings
that we don't use. The most common one is the Log4J2 binding that Storm brings
along ("org.apache.logging.log4j:log4j-slf4j-impl").
It could be argued that we don't need to exclude the binding we are using
("org.slf4j:slf4j-api") and control the version through dependency management
as you suggest. The downside I see there though is that if we ever did want to
change the logging implementation we would have to go through all the poms and
exclude that binding (what's already been done here). As it stands, changing
the logging implementation is as simple as changing the binding in the
metron-platform/analytics pom files and adding logging configuration files.
> Set log levels for Metron components
> ------------------------------------
>
> Key: METRON-541
> URL: https://issues.apache.org/jira/browse/METRON-541
> Project: Metron
> Issue Type: Bug
> Reporter: Ryan Merriman
> Assignee: Ryan Merriman
> Priority: Critical
>
> When running unit or integration tests the log output is very verbose. This
> makes it difficult to determine what the problem is when something goes wrong
> and also intermittently causes Travis to hit it's output threshold and fail.
> The log levels should be consistent across all components and there should be
> logging profiles available for different scenarios.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
