#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Domino Cluster Reporting tool

Reference:  SPR #SKURA6X9XT

Customer would like to have a built-in tool within Domino to report cluster replication failures including details such as below:

Example-:

Document count
Database size
Count in difference
Replication type and setting

Error message if encountered during replication

 

Reference:  SPR #GFAL8TAHYY

Another related SPR for enhancement request regarding request for cluster replication probes to be included in DDM.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Feb 5 2019
  • Needs review
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    07 Feb 01:31

    Great idea! I agree this 100%

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    16 Jan 11:51

    My additional suggestions:

     

    Make it possible to select additional SCR logging via notes.ini setting(s). Make one of these have a level that allows SCR replication events to be logged to their own text-based logs in IBM_TECHNICAL_SUPPORT like there is for SEMDEBUG and a few others. Make the output in these "SCR logs" be in a csv format like the example below:

     

    [SCR-Clu]:“server from”;”server to”;”path and dbname”;”access”;”added”;”deleted”;”updated”;”KB rec”;”KB sent”;"Error messages"

     

    Make these additional "SCRlogs" be handled by the automatic routine that deletes old logs and stuff from IBM_TECHNICAL_SUPPORT.

     

    In organizations that work under strict regulations, I fail to see how they are able to use SCR replication at all, since it is virtually impossible to document what has happened, when, by whom, how many and so on. Think that would fail miserably in any audit.