The logging and monitoring service has been created#8
Open
KAMALDEEN333 wants to merge 2 commits intoMyFanss:mainfrom
Open
The logging and monitoring service has been created#8KAMALDEEN333 wants to merge 2 commits intoMyFanss:mainfrom
KAMALDEEN333 wants to merge 2 commits intoMyFanss:mainfrom
Conversation
Author
|
Hi @abdegenius Conflit as been resolved kindly review and merge |
Author
|
Hi @abdegenius are u available. |
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
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.
The Logging has been created ensuring it has the below concept and all criterias were met
Integrated a logging service such as Winston, Pino, or extend NestJS's built-in Logger.
Supported for log levels: info, warn, error, debug.
Included context such as timestamps, class/method names, request IDs (where applicable).
Logged formatting: JSON or human-readable based on environment (development vs production).
Captured logs from:
Application lifecycle events (startup, shutdown)
HTTP requests/responses
Errors/exceptions (should integrate with Global Exception Filter)
Custom business events
Monitoring
Integrate lightweight metrics collection (e.g., using Prometheus, OpenTelemetry, or a SaaS tool like Datadog, Sentry, New Relic).
Track metrics such as:
Request count and duration
Error rates
Uptime and memory usage
CPU load (optional)
(Optional) Set up health checks using NestJS's @nestjs/terminus
🧩 Deliverables
A LoggerService or reusable wrapper for logging across the app
Environment-based logging configuration
Metrics/monitoring module setup
Documentation on how to use the logger and interpret the metrics
Example usage in one or more modules (controllers/services)
✅ Acceptance Criteria
Logs are consistent and include meaningful context
Logging can be toggled or filtered via environment config
Monitoring service is integrated and exposes metrics endpoint (e.g., /metrics for Prometheus)
Logging works in harmony with Global Exception Filter
No sensitive data is accidentally logged
All tools and configurations are documented for team use
Activity