Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-1959

Add service upgrade/downgrade logging

        Details

        • Type: New Feature
        • Status: Closed
        • Priority: Major
        • Resolution: Won't Fix
        • Affects Version/s: 3.6.0
        • Fix Version/s: Sponsored
        • Component/s: Staff Interface
        • Labels:
          None

          Description

          Use monolog in 4.0 to log upgrade/downgrades which are currently stored in invoices in a verbose form. See CORE-1763.

          The logs should be accessible on a per-client basis on their client profile, probably as part of a larger log system.

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            tyson Tyson Phillips (Inactive) added a comment -

            What information does this aim to log exactly? I think this should be broken into two parts that don't necessarily need to be done at the same time:

            1. Log the information (to file? to database?)
            2. Display the information - if this should be displayed in the UI, it would be better to have it logged to the database, which would necessitate a separate logger for doing so
            Show
            tyson Tyson Phillips (Inactive) added a comment - What information does this aim to log exactly? I think this should be broken into two parts that don't necessarily need to be done at the same time: Log the information (to file? to database?) Display the information - if this should be displayed in the UI, it would be better to have it logged to the database, which would necessitate a separate logger for doing so
            Hide
            Permalink
            admin Paul Phillips added a comment -

            The information logged should be similar to the previous long-form invoices that the system generated so that it would be possible to tell what the customer had, and what they got after the upgrade. If logged to file, (or database for that matter), it would probably be ok to store the data in JSON format.

            I would lean toward storing in a database so that it can be easily referenced from Blesta (possibly an option on the service to view the history in the future), and so that we can store a longer history (We may not want records to be rotated out so quickly).

            Show
            admin Paul Phillips added a comment - The information logged should be similar to the previous long-form invoices that the system generated so that it would be possible to tell what the customer had, and what they got after the upgrade. If logged to file, (or database for that matter), it would probably be ok to store the data in JSON format. I would lean toward storing in a database so that it can be easily referenced from Blesta (possibly an option on the service to view the history in the future), and so that we can store a longer history (We may not want records to be rotated out so quickly).
            Hide
            Permalink
            admin Paul Phillips added a comment -

            This is being replaced by CORE-2388

            Show
            admin Paul Phillips added a comment - This is being replaced by CORE-2388

              People

              • Assignee:
                Unassigned
                Reporter:
                admin Paul Phillips
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: