Child pages
  • Unresolved issues - Get Audit Trails

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

History on (un)resolved issues

Bemærk: der er ikke taget stilling til hvordan dette hænger sammen med auditframeworket/logning:"En speciel notifikations-service er audit-servicen. Denne service vil altid modtage notifikationer om handlinger, og logge dem i audit-frameworket. Der bør være defineret andre standard-services som kan logge og advare på forskellige niveauer." NOT RELEVANT ANY MORE

Skal denne tilbyde service til at gemme audittrails for ben og klienter? Kunne også være lokation af filer (til når/hvis de bliver væk) COVERED BY scenario description.
Do we need an internal log 'database'? it is included here on the assumption that it help in optimisation. IMPLEMENTATION DEPENDENT
Do we need an internal log 'database'? it is included here on the assumption that it help in optimisation. COVERED BY scenario description.
Is the logging level always defined by the SLA, or can the decision be left open to the pillars (f.x. logging of internal status queue) NO MORE LOGGING

Section
Column
width80%
  • Needs somehow to ensure that audit trail contains information from all possible contributors (see BITMAG-212@jira in list)
  • Spike must be evolved as specified in issue  BITMAG-207@jira
  • Can later be extended to include more than one FileID (see BITMAG-208@jira)
  • Consider how audit trail may or cannot be reconstructed after loss of file (discovered by integrity check)
Column
JIRA Issues
width400px
urlhttps://sbforge.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+BITMAG+AND+resolution+%3D+Unresolved+AND+component+%3D+%22Audit+trail%22+ORDER+BY+priority+DESC&tempMax=1000
Section
Column