JOC - JobScheduler Operations Center
  1. JOC - JobScheduler Operations Center
  2. JOC-465

Toggle display of log source and of debug output in log view window

    Details

      Description

      Current Situation

      • Log output is created
        1. from the JobScheduler Master or Agent that writes messages e.g. about start and termination of tasks
        2. from any output to stdout/stderr that is caused by shell jobs
        3. from messages that are added by API jobs and by Monitors - this includes messages at info level and any debug level.
      • Log output from the three sources is combined in the log file. When displaying log output that includes a large number of debug messages then the log is hard to read for users.

      Desired Behavior

      • The JOC Cockpit log view window should allow to select the log output from above sources 1) to 3), e.g. to limit log output to stdout/stderr.
      • The JOC Cockpit log view window should allow to toggle between enabling and disabling the display of debug output.
        • The toggle should be available for all debug levels, e.g.
          • specifying debug1 will disable messages for any debug levels.
          • specifying debug3 wiill disable messages for debug levels debug1, debug2, debug3.
        • The toggle default value is to suppress debug messages.

      Maintainer Notes

      • This feature is not assigned to a specific release for now. You can vote for this issue to make it real.
      • Your input is welcome: let us know your comments about the handling of debug output with logs..

        Issue Links

          Activity

          Hide
          Atul Pathak added a comment -

          At present we use the STDOUT to append the application log generated by our Python programme to the main job scheduler log. The requirement is to be able to isolate and view only the application log.

          I am unable to visualize how the proposed enhancement work. Is there a diagram / picture you can share to better understand this?

          Will we need to modify our application logs in some way for the job scheduler to handle it? Will we still need to STDOUT in a certain way?

          Are you suggesting that the Job will always run in Debug level 3( maximum debug) and then the toggle button hides/shows the respective data?

          Show
          Atul Pathak added a comment - At present we use the STDOUT to append the application log generated by our Python programme to the main job scheduler log. The requirement is to be able to isolate and view only the application log. I am unable to visualize how the proposed enhancement work. Is there a diagram / picture you can share to better understand this? Will we need to modify our application logs in some way for the job scheduler to handle it? Will we still need to STDOUT in a certain way? Are you suggesting that the Job will always run in Debug level 3( maximum debug) and then the toggle button hides/shows the respective data?
          Hide
          Andreas Püschel added a comment -

          Hi Atul Pathak,

          we updated the issue description to reflect the capability to limit log output to stderr/stdout (which is the output of shell jobs resp. your python scripts).

          Let us know if this matches your requirements.

          Show
          Andreas Püschel added a comment - Hi Atul Pathak , we updated the issue description to reflect the capability to limit log output to stderr/stdout (which is the output of shell jobs resp. your python scripts). Let us know if this matches your requirements.
          Hide
          Andreas Püschel added a comment -

          Hi Atul Pathak,

          we updated the issue description to better answer your questions:

          • You do not have to modify your application logs. The new log view window allows to
            • filter log output to exclusively show e.g. output to the stdout/stderr channels as created from your jobs (show exclusively the application log)
            • optionally allow debug output to be displayed with your log. You can select up to which debug levels you want to see debug log output.
          • The filtering is done with the log view window that provides a number of check boxes to select from which sources you want to see log output.

          This feature is available with release 1.12.5

          Best regards
          Andreas

          Show
          Andreas Püschel added a comment - Hi Atul Pathak , we updated the issue description to better answer your questions: You do not have to modify your application logs. The new log view window allows to filter log output to exclusively show e.g. output to the stdout/stderr channels as created from your jobs (show exclusively the application log) optionally allow debug output to be displayed with your log. You can select up to which debug levels you want to see debug log output. The filtering is done with the log view window that provides a number of check boxes to select from which sources you want to see log output. This feature is available with release 1.12.5 Best regards Andreas

            People

            • Assignee:
              Sourabh Agrawal
              Reporter:
              Andreas Püschel
              Approver:
              Santiago Aucejo Petzoldt
            • Votes:
              3 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: