Trunk 6514 performance markers #5663
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



Description of what I changed
In this pull request, I have introduced SLF4J
performancemarkers to thelog.debugstatements that were originally added in TRUNK-6436 to monitor OpenMRS startup performance. This change allows developers and system administrators to easily filter or redirect performance-related logs by targeting the "performance" marker.The following changes were implemented:
PERFORMANCE_MARKERusingMarkerFactory.getMarker("performance")in multiple core and web classes.ModuleUtil.java,WebModuleUtil.java,Listener.javaandInitializationFilter.java.Issue I worked on
see https://issues.openmrs.org/browse/TRUNK-6514
Checklist: I completed these to help reviewers :)
mvn clean packageright before creating this pull request and added all formatting changes to my commit.