Observability: Sentry uptime

[AkhileshNegi]

Summary

Target Issue: #132

• Added a health check endpoint to monitor application status.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: fe8ffab6-cf7e-4eed-a447-42ffc0fa1f5c

📥 Commits

Reviewing files that changed from the base of the PR and between 2884ac6 and 8e3fa09.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (2)

• app/api/health/route.ts
• next.config.ts

---

📝 Walkthrough

Walkthrough

This pull request introduces a new health check API endpoint at app/api/health/route.ts configured for dynamic execution, and updates next.config.ts to allow development requests from ngrok-free.app domains.

Changes

Cohort / File(s)	Summary
Health Check Endpoint app/api/health/route.ts	New API route that responds to GET requests with { status: "ok" }, forces dynamic execution via force-dynamic, and disables caching with Cache-Control: no-store header.
Development Configuration next.config.ts	Added allowedDevOrigins configuration entry to permit requests from *.ngrok-free.app during development.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Poem

🐰 A health check hops into place,
With dynamic force and speedy grace,
ngrok tunnels open the dev door wide,
Status "ok" runs with bunny pride! 🌟

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title 'Observability: Sentry uptime' is partially related to the changeset. While it mentions 'Observability' which aligns with monitoring, the actual changes add a health check endpoint and ngrok configuration for development, but don't appear to directly implement Sentry uptime monitoring.	Clarify whether the health endpoint serves as preparation for Sentry integration, or update the title to more accurately reflect the actual changes: creating a health check API route and configuring development origins.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch monitoring/sentry

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 0/1 reviews remaining, refill in 60 minutes.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Ayush8923]

I don't think ngrok needed for production and staging. This is only for local testing maybe.

[AkhileshNegi]

yes will remove