#053: Email/System Monitoring (ELK Stack)#98
Open
samieazubike wants to merge 3 commits intoGildado:mainfrom
Open
#053: Email/System Monitoring (ELK Stack)#98samieazubike wants to merge 3 commits intoGildado:mainfrom
samieazubike wants to merge 3 commits intoGildado:mainfrom
Conversation
- Added logger.ts for structured JSON logging with multiple transports (console, file, Elasticsearch). - Introduced child logger support and contextual logging helpers for performance metrics, transactions, and security events. feat(monitoring): Add alerting service for error rates and performance thresholds - Created alerting.ts to monitor error rates and response times, triggering alerts when thresholds are exceeded. - Implemented email notifications for alerts and cooldown periods to prevent alert storms. feat(monitoring): Introduce metrics collector for performance tracking - Developed metrics.ts to track HTTP request metrics, error rates, and database query performance. - Exposed metrics via /api/monitoring/metrics endpoint and integrated with Elasticsearch. feat(monitoring): Add distributed tracing service - Created tracing.ts for W3C Trace Context-compatible distributed tracing. - Supports nested spans and logging of trace information to Elasticsearch. chore(docker): Set up ELK stack for centralized logging and monitoring - Added docker-compose.elk.yml to run Elasticsearch, Logstash, and Kibana. - Configured Logstash pipeline for processing JSON logs from the backend. chore(docker): Create Kibana setup script for index patterns - Added setup-kibana.sh to automate the creation of index patterns and dashboards in Kibana.
|
Hey @samieazubike! 👋 It looks like this PR isn't linked to any issue. If this PR is for one of the issues assigned to you as part of a Wave, please link it to ensure your contribution is tracked properly. You can do this by adding a keyword to the PR description (e.g.,
|
Collaborator
|
Hi @samieazubike there seems to be conflict can you resolve please |
Collaborator
|
Hello @samieazubike Kindly resolve conflicts and push again |
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
2 participants
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.
#57 feat(logging): Implement centralized logging service with Winston
feat(monitoring): Add alerting service for error rates and performance thresholds
feat(monitoring): Introduce metrics collector for performance tracking
feat(monitoring): Add distributed tracing service
chore(docker): Set up ELK stack for centralized logging and monitoring
chore(docker): Create Kibana setup script for index patterns