Remove old/redundant loggers
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
We have a few loggers that are trying to write an audit trail type logs :
- ActivityLogger
- SecurityLogger
- AdminLogger
In my mind, these all should be piped through the SecurityLogger as that decorates the logs with user and ip and then logged appropriately.
Steps to Reproduce
All audit type logs should be logged under the securitylog
Acceptance Criteria
make sure the logs are coming out of security logs
dotCMS Version
latest
Proposed Objective
Please Select
Proposed Priority
Please Select
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
No response
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are identified in the issue. Start by locating ActivityLogger, SecurityLogger, and AdminLogger and tracing their audit-log callers. Done means audit-type logs are emitted through SecurityLogger and retain the required user and IP context, with tests or verification covering the affected log paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, security
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100