Idea ID: 2840089

UCMDB History and Archiving DB for 10 years

Status : Waiting for Votes
Waiting for Votes
See status update history
8 months ago

Hello ,  as suggested by Gabi Medan  i post a new idea on    how to solve  a common problem in EU where law for some  vertical markets asks to retain history data up to 10 years.  

I see many interested in   enhance the product  in order to satisfy this  request.  Not sure  with which kind of  tools/external tools/db tools to be created  in order to have  an archive that can be accessed and examined

I attach the discussion mails in the forum 

 

This feature is of high interest  since some years.... so please vote it  to make RND work on a solution 

 

Labels:

Other
  • Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team
  • Hi

    We currently store all history for 6 years 5+1, no exceptions

    I think the general performance of retrieving history today is poor, and as such an general design review must be considered.

    the basic requirements is that an "user" must be able to

    Fetch data from a limited time period (start date - end date)  within minutes

    on at least a 10 year period.

    They must be able to see both END1 / END2 from the same CI entry point.

    We should be able to report changes on a "query" overtime ( snapshot before/after) in a much more detailed way than today

    From a technical standpoint it must be considered.

    If storing History in current way is the right way? maybe add some new technology (COSO, document..?) provide it embedded and for large deployments as external component.

    We should be able to purge history for a set of defined CI's (Query?) (not only CIT) to ensure we can remove all traces of data from CIHistory, if so required by business or law.

    /Glen

     

     

  • Hello,   i ask  the community to try to refine the requirement with possibilities to be investigated.  Customer wants the "history"  finish.  OF course there is no sense to preserve the history of all but i presume  only data related to  configurations related to business services.  I do not think it is of interest recall to which hypervisor the vm was linked.... Maybe  a new attribute on topology views to mark them for "long history enabling"..... 

    I know this is poor brainstorming but with the help of the community maybe some thing more solid as requirement could come.... I need your ideas around this matter