You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Andras Piros (JIRA)" <ji...@apache.org> on 2018/12/05 13:31:00 UTC

[jira] [Comment Edited] (OOZIE-3397) Improve logging in NotificationXCommand

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

Andras Piros edited comment on OOZIE-3397 at 12/5/18 1:30 PM:
--------------------------------------------------------------

Thanks for the contribution [~kmarton]! Can you please also add a {{DEBUG}} level message to know about the state or retries? Like {{Trying for the \{0} time out of total {1}}}.


was (Author: andras.piros):
Thanks for the contribution [~kmarton]! Can you please also add a {{DEBUG}} level message to know about the state or replies? Like \{{Trying for the \{0\} time out of total \{1\}}}.

> Improve logging in NotificationXCommand
> ---------------------------------------
>
>                 Key: OOZIE-3397
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3397
>             Project: Oozie
>          Issue Type: Improvement
>    Affects Versions: trunk
>            Reporter: Julia Kinga Marton
>            Assignee: Julia Kinga Marton
>            Priority: Major
>         Attachments: OOZIE-3397.001.patch
>
>
> Around the notification sending (NotificationXCommand) there is not so much logging. For example if the HTTP call fails, the error is suppressed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)