[ 
https://issues.apache.org/jira/browse/MINIFI-296?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031315#comment-16031315
 ] 

ASF subversion and git services commented on MINIFI-296:
--------------------------------------------------------

Commit 73ecc6671b2c2ca0d1fe650094e35be172ed6096 in nifi-minifi-cpp's branch 
refs/heads/master from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=nifi-minifi-cpp.git;h=73ecc66 ]

MINIFI-296 - Configurable logging, spdlog 0.13.0

Logger pattern specification and atomic logger delegate

This closes #104.

Signed-off-by: Aldrin Piri <[email protected]>


> 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)

Reply via email to