feat(backend): add Prometheus monitoring and metrics #37
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.
Description
This PR introduces Prometheus monitoring to the feedback backend to improve observability.
It adds a new
/metricsendpoint (exposed on port${METRICS_PORT}, defaulting to 3099 as perserver.js) that exposes key application metrics for scraping.Changes Made
prom-clientas a new backend dependency.PrometheusScrapeAgentandHTTPServerto handle metrics collection and exposure.server.jsto initialize the agent and register new metrics.feedback_app_api_calls_total)feedback_app_webhook_events_total)feedback_app_registrations_total,feedback_app_failures_total)feedback_app_ratings_histogram)docker-compose.ymlto expose the new metrics port and add theMETRICS_PORTenvironment variable.How to Test
feedback_app_metrics.curlcommand again and verify that thefeedback_app_registrations_totalcounter and thefeedback_app_ratings_histogram_counthave incremented.