Uploaded image for project: 'translate5'
  1. translate5
  2. TRANSLATE-3806

Log specific additional system events for warranty reasons

    XMLWordPrintable

Details

    • High
    • Add specific or additional log entries for crucial actions in translate5.
    • -

    Description

      problem

      In support from time to time questions of the following type are popping up:

      Who did delete / change XY when?

      For warranty reasons we should log such informations, since sometimes the clients are assuming bugs or wrong setups / configurations for erroneously deleted / changed things.

      To be logged:

      • User deletion (also modification)
      • Task deletion (also modification)
      • Add / remove of language resources to tasks...
      • Delete tasks: Add to log, who deleted them
      • Assign or remove customers from language resources. Also assigning or remove assignment for read/write defaults
      • Changing configs via cmd. Currently it is not logged
      • List to to be continued
      • enabling / disabling maintenance (is logged already, but should not be deleted after x weeks)

      To be defined: How to prevent the default deletion of such events? by a specific flag / level of the events? Or just Ecode?

      Completely separate logging (file based) for such permanent logs (created by an addtional log writer just listening to warranty critical logs)?

      For things being logged due warranty reasons 10 years would be the default duration of keeping things. Must be discussed.

      Attachments

        Issue Links

          Activity

            People

              leonkiz Leon Kiz
              tlauria Thomas Lauria
              Thomas Lauria
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: