[
https://issues.apache.org/jira/browse/MINIFI-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryan Rosander updated MINIFI-296:
----------------------------------
Description:
The logging functionality would be more useful if it could be tuned on a
per-class basis. This would allow us to set more detailed log levels for a
place where trouble is suspected while reducing noise from other areas.
Composable log appenders would allow us to have multiple sinks so that we would
have a log appender that could "phone home" with information while concurrently
logging to disk. Using a processor to do the same may be too onerous; however,
it stands to reason that we may use the processor as the delivery mechanism, so
we may eventually negate this issue entirely if it is decided that we should
ship the log itself via a processor.
was:
The logging functionality would be more useful if it can be tuned on a
per-class basis. This would allow us to set more detailed log levels for a
place where trouble is suspected while reducing noise from other areas.
Composable log appenders would allow us to have multiple sinks so that we would
have a log appender that could "phone home" with information while concurrently
logging to disk. Using a processor to do the same may be too onerous; however,
it stands to reason that we may use the processor as the delivery mechanism, so
we may eventually negate this issue entirely if it is decided that we should
ship the log itself via a processor.
> More configurable logging
> -------------------------
>
> Key: MINIFI-296
> URL: https://issues.apache.org/jira/browse/MINIFI-296
> Project: Apache NiFi MiNiFi
> Issue Type: Improvement
> Components: C++
> Reporter: marco polo
> Assignee: Bryan Rosander
> Priority: Minor
>
> The logging functionality would be more useful if it could be tuned on a
> per-class basis. This would allow us to set more detailed log levels for a
> place where trouble is suspected while reducing noise from other areas.
> Composable log appenders would allow us to have multiple sinks so that we
> would have a log appender that could "phone home" with information while
> concurrently logging to disk. Using a processor to do the same may be too
> onerous; however, it stands to reason that we may use the processor as the
> delivery mechanism, so we may eventually negate this issue entirely if it is
> decided that we should ship the log itself via a processor.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
