Feature/cloudwatch - #18
Merged
Merged
Conversation
- Added LoggingAspect to record API entry and exit (method, URI, duration) - Added AccessLogFilter to classify and log final request results: - INFO for successful 2xx responses - WARN for expected 4xx client errors - ERROR for unexpected 5xx server errors with stack traces
- Updated AccessLogFilter to merge general @AccessNote messages with per-request details (e.g., "Health Check failed - Query parameters are not allowed") - Added helper to safely combine messages for 4xx and 5xx cases - Ensured consistent formatting across success, warning, and error logs
Add fallback handling in AccessLogFilter for requests blocked by Spring Security. Ensures 401 (Unauthorized) and 403 (Forbidden) responses are logged with meaningful default messages and codes even when Security filters bypass controller logic. - Added safe attribute reader to avoid literal "null" in logs
…mats - Added logback-spring.xml to define structured JSON output for file logs - Configured STDOUT appender with human-readable pattern for local debugging - Introduced ACCESS logger for AccessLogFilter to log independently from root logger - Enabled <springProperty> to dynamically read LOG_DIR from Spring environment
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
4 times, most recently
from
October 30, 2025 06:53
f0fc1f3 to
1bc1d20
Compare
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 07:40
1bc1d20 to
8b2e75b
Compare
…uring CI - The server no longer includes a WWW-Authenticate challenge header, so RestAssured's passive basic() auth was not retrying after 401. Using preemptive().basic() ensures credentials are sent on the first request
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 07:58
8b2e75b to
0bdd16f
Compare
- Added Spring Boot Actuator dependency - Exposed `health`, `info`, and `metrics` endpoints in application.yml - Introduced timedS3 wrapper to record S3 operation latency using Micrometer - Enhanced Packer build with step-by-step validation to ensure each provisioner succeeds
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 17:28
0bdd16f to
1d98062
Compare
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 17:58
1d98062 to
e5d03d9
Compare
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 18:02
e5d03d9 to
761f377
Compare
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
from
October 30, 2025 18:12
761f377 to
aa44e05
Compare
- Let the script do it at once
IsaacTai13
force-pushed
the
feature/cloudwatch
branch
2 times, most recently
from
October 30, 2025 18:49
538a8c5 to
d83aa79
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.