Add Metrics Endpoint (Prometheus or JSON)

[greatest0fallt1me]

Description
Expose GET /api/metrics (or /metrics) with request count, latency histogram, error count by route. Format: Prometheus text or JSON. Optional: use prom-client. Protect endpoint in production (e.g. internal only or API key).

Requirements and context

• Must not expose PII
• Use for monitoring and alerting

Suggested execution

• Fork the repo and create a branch
• git checkout -b feature/metrics
• Implement changes
  • Add middleware to record request count and duration; GET /api/metrics returns metrics
  • Example commit message: feat: metrics endpoint for monitoring

Guidelines

• No PII in metrics
• Clear documentation
• Timeframe: 96 hours
• Project details: #

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[Code-Paragon]

@Code-Paragon has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi @greatest0fallt1me , I would like to be assigned to this issue.

Implementation Plan:

Library Integration: I will implement prom-client to expose metrics in the standard Prometheus text format, ensuring seamless integration with standard scraping stacks (Prometheus/Grafana).

Metrics Collection Middleware: I will build a global middleware to track:

http_requests_total (Counter: labeled by method, route, and status code).

http_request_duration_seconds (Histogram: labeled by method, route, and status code).

PII & Cardinality Protection: To strictly prevent PII leakage and metric cardinality explosions, the middleware will sanitize dynamic route parameters before recording them (e.g., standardizing /api/users/12345 to /api/users/:id).

Endpoint Security: I will secure the /api/metrics endpoint by implementing a lightweight API key/Bearer token guard (configured via environment variables), ensuring it is protected from public access in production.

Documentation: I will update the README with instructions on configuring the auth token and configuring a scraper.

ETA: 48 hours.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Code-Paragon to this issue.

[drips-wave]

Congratulations, @Code-Paragon! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on February 26, 2026.

🧑‍💻 @Code-Paragon: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are issued when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Code-Paragon as part of the Stellar Wave Program's 2nd Wave 🥳

😎 @Code-Paragon: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.