Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-6287

Add the INFO log level to audit log prune events

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Core features
    • None
    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      • Currently, the crowd.manager.audit.AuditLogPruner only captures ERROR messages.
      • We need access to the prune log messages for the successful events, as these messages help us understand if the audit events are deleted by the auditLogPrunerJob.
      • Without the INFO messages, it is impossible to investigate whether the application removed the audit logs.

            [CWD-6287] Add the INFO log level to audit log prune events

            SET Analytics Bot made changes -
            Support reference count New: 1
            Sunil Kumar C made changes -
            Link Original: This issue is cloned from CWD-6286 [ CWD-6286 ]
            Sunil Kumar C made changes -
            Description Original: h3. *Issue Summary*
            * Currently, the *crowd.manager.audit.AuditLogPruner* only captures ERROR messages.
            * We need to review the prune log messages for the successful events, as these messages help us understand if the audit events are deleted.
            * Without the INFO messages it is impossible to investigate if the audit logs were removed by the application.
            		New: h3. *Issue Summary*
             * Currently, the *crowd.manager.audit.AuditLogPruner* only captures _ERROR_ messages.
             * We need access to the prune log messages for the successful events, as these messages help us understand if the audit events are deleted by the {_}*auditLogPrunerJob*{_}.
             * Without the INFO messages, it is impossible to investigate whether the application removed the audit logs.
            Sunil Kumar C made changes -
            Summary Original: Change the prune log level from INFO to DEBUG New: Add the INFO log level to audit log prune events
            Sunil Kumar C made changes -
            Description Original: h3. *Issue Summary*
             * Currently, the scheduled jobs such as _*auditLogPrunerJob*_ among others in the Crowd, can't be modified. (They are set to 12:00 AM system time by default).
             ** !image-2024-08-22-14-53-23-748.png|width=473,height=154!
             * Please provide an option to modify these CRON jobs to meet the customer's requirements.             		New: h3. *Issue Summary*
            * Currently, the *crowd.manager.audit.AuditLogPruner* only captures ERROR messages.
            * We need to review the prune log messages for the successful events, as these messages help us understand if the audit events are deleted.
            * Without the INFO messages it is impossible to investigate if the audit logs were removed by the application.
            Sunil Kumar C made changes -
            Link New: This issue is cloned from CWD-6286 [ CWD-6286 ]
            Sunil Kumar C created issue -

              Unassigned Unassigned
              91d55d8c0ba7 Sunil Kumar C
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:

                  Estimated:
                  Original Estimate - 40h
                  40h
                  Remaining:
                  Remaining Estimate - 40h
                  40h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified