Uninett
What happens when a Source System is decommissioned?
If a user decommissions a Source System, that system will no longer submit incidents to Argus. However, it is assumed the user still wants to keep the incident history in Argus. How can this be supported by Argus? Thoughts:
- Most importantly, Argus should be able to prevent future Incidents to be posted on behalf of the decommissioned Source System - but how?
- User deletes the Source System entry from Argus: This would either cascade-delete all the stored incidents related to the source (a big no-no), or remove the relation from the existing Incidents, thereby fully or partially losing history.
- Signal a "decommissioned state" for an Source System by either
- Deleting the Source's associated User account.
- Setting a boolean flag and/or timestamp on the Source System record to indicate its time of decommission.
I'm leaning partially towards the scenario where the associated user account must be deleted in all scenarios. An Source System with a missing user account could be considered decommissioned, as it no longer has a valid token to submit incidents. However, Argus must also protect against inadvertently removing a user account from a Source System (or, at least, if such a User is deleted, it should be easy to add a new one for that Source). It also isn't unheard of for a source to be decommissioned, only to be revived temporarily again at a later time...
Having a "decommisioned" timestamp (nullable) on the source itself is also handy. The live incident list could exclude them.
