Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-28516

Display an error if logging stack not configured when required (e.g. on ZAP report request)

    XMLWordPrintable

Details

    • Improvement
    • Status: New
    • Not specified
    • Resolution: Unresolved
    • None
    • None
    • WsWorkunits
    • None

    Description

      Currently, if a ZAP report is requested and the logAccess has not been defined (or defined incorrectly?), the ZAP report is produced and silently creates an empty log file.

      EclWatch should produce a warning/error that highlights the issue.
      NB: it should still continue to produce a ZAP report, as it is still useful without logging.

      The content of the ZAP report log could also contain the warning/info. as to why it's empty.

      Attachments

        Activity

          People

            wangkx Kevin Wang
            jakesmith Jake Smith
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: