-
-
Notifications
You must be signed in to change notification settings - Fork 26.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microservice pattern: Exception tracking #2694
Labels
Comments
can you assign it to me? |
Please assign me this issue. |
This issue has been automatically marked as stale because it has not had recent activity. The issue will be unassigned if no further activity occurs. Thank you for your contributions. |
stale
bot
added
the
status: stale
issues and pull requests that have not had recent interaction
label
Jan 24, 2024
stale
bot
removed
the
status: stale
issues and pull requests that have not had recent interaction
label
Mar 24, 2024
iluwatar
added
info: help wanted
status: stale
issues and pull requests that have not had recent interaction
labels
Mar 24, 2024
stale
bot
removed
the
status: stale
issues and pull requests that have not had recent interaction
label
Mar 24, 2024
@iluwatar can you assign me this one? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
The Exception Tracking design pattern in microservices architecture involves the centralized handling and logging of exceptions that occur across different services. This pattern is essential for monitoring, debugging, and maintaining the health of a distributed system by providing a unified view of errors and their origins.
Main Elements of the Pattern:
References
Acceptance Criteria
The text was updated successfully, but these errors were encountered: