Details

      Description

      Currently, the new las2peer logger enforces a "use local file-based logging only" approach. This is not good. Logging should be refactored to notify the monitoring as default.

      Also the duplicate timestamps and the logging class entry itself could be removed from the files, since they take up a considerable amount of space without adding any information.

      Also, service custom messages should maybe be put into a separate local file (additionally to them being also sent to the monitoring node) to allow service developers to quickly check their messages while developing a success model for their service.

       

      All in all, we should put some effort in improving monitoring and logging, and then write a short article about this in our wiki.

        Attachments

        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              janbe Jan Benscheid
              Reporter:
              pedela Peter de Lange
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                8/May/18

                Time Tracking

                Estimated:
                Original Estimate - 1 day, 1 hour, 30 minutes
                1d 1h 30m
                Remaining:
                Time Spent - 1 hour Remaining Estimate - 1 day, 30 minutes
                1d 30m
                Logged:
                Time Spent - 1 hour Remaining Estimate - 1 day, 30 minutes
                1h