Hashtags Rotator: Crash Testing Guide

Hashtag Rotator Observability

🚦 Endpoint Testing • 🧠 Crash Diagnostics • 🛰️ Edge Coverage • 📡 Geo Routing

“You’re not just debugging — you’re building civic observability with global reach.”

🔥 Crash Tracing Guide

To view live crashes and trace 500 errors:

• Open your Vercel dashboard
• Go to Logs → Filter by Function, Level, and Status: 500
• Look for EDGE_FUNCTION_INVOCATION_FAILED or missing environment variables

🧪 Endpoint Testing Suite

GET /api/health → { status: "ok", edgeRegion: "iad1" } GET /api/cron → { message: "Cron ran successfully" } GET /api/trends?region=ke → [ "#KenyaElections2025", "#JusticeForYouth" ] GET /kenya-trends → Geo-routed rewrite (KE IP → Kenya trends) 

🌍 Recent Edge Activity

• sfo10 – San Francisco, USA
• cpt10 – Cape Town, South Africa
• fra10 – Frankfurt, Germany
• lhr10 – London, United Kingdom
• iad10 – Washington, D.C., USA

Even failed requests (500 errors) get counted by edge regions. They show up in logs and observability graphs — proving public reach even during errors.

Author: Peter M. Mutiti | Investigative Journalist & Civic Technologist

MIT License © 2025 Peter M. Mutiti · View License