-
Type:
Task
-
Resolution: Unresolved
-
None
-
Affects Version/s: None
-
Component/s: Main back-end mechanisms (Worker, Logging, etc.)
-
High
-
Add specific or additional log entries for crucial actions in translate5.
-
Emptyshow more show less
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 UI or cmd. Currently it is not logged
- All failed login attempts
- All attempts to illegally increase access privileges (priviledge escalation)
- 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.
- relates to
-
TRANSLATE-2217 List refactoring and code maintenance needs in translate5
- Selected for dev
1.
|
Log audit logs for User model |
|
Final pull request | Sanya Mikhliaiev |
2.
|
Log audit logs for Customer model |
|
Final pull request | Sanya Mikhliaiev |
3.
|
Log audit logs for Task model |
|
Final pull request | Sanya Mikhliaiev |
4.
|
Add audit log for all failed login attempts |
|
Final pull request | Sanya Mikhliaiev |