[ https://issues.apache.org/jira/browse/ARIA-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15974334#comment-15974334 ]
ASF GitHub Bot commented on ARIA-138: ------------------------------------- GitHub user mxmrlv opened a pull request: https://github.com/apache/incubator-ariatosca/pull/103 ARIA-138-Make-logging-more-informative You can merge this pull request into a Git repository by running: $ git pull https://github.com/apache/incubator-ariatosca ARIA-138-Make-logging-more-informative Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-ariatosca/pull/103.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #103 ---- ---- > CLI output verbosity levels > --------------------------- > > Key: ARIA-138 > URL: https://issues.apache.org/jira/browse/ARIA-138 > Project: AriaTosca > Issue Type: Story > Reporter: Maxim Orlov > Assignee: Maxim Orlov > > The CLI should support the display of the following logging levels: > default: execution logs: simple representation of executed operations > -v : execution logs: representation with time stamps and logging levels > -vv : execution logs: retrieve the stacktrace of any failed operation. > -vvv : all configured loggers should be set to {{debug}} level; any CLI > errors should be logged and printed with their stack trace as well. > (both the default and the first level of logging format should be > configurable). > Note that all of the operations logs should be saved in the storage. This > issue relates only to the way the logs are displayed in the CLI. -- This message was sent by Atlassian JIRA (v6.3.15#6346)