✨(backend) Adding /prometheus metrics endpoint #455 #476
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.
implements various metrics for users, documents and the actual django application
Purpose
The purpose of this implementation is to provide detailed insights into the usage patterns and performance of the Django application. By collecting metrics for users, documents, and the application itself, developers and administrators can monitor activity, identify bottlenecks, and optimize performance. These metrics are also essential for integrating with monitoring systems like Prometheus, enabling observability and proactive issue resolution.
Proposal
Introduce a custom Prometheus metrics collector that gathers and exposes detailed information about user activity, document usage, and the application's operational status.
Key Features