Alhamdulillah, RamadanHacks winners are here 🏆 1️⃣ Mahfuz – 1st place – mahfuz.ilg.az/ 2️⃣ Pixel Pilgrim – 2nd place – hajj.buzz/ 3️⃣ Hajj Coach – 3rd place – hajjcoach.app/ Next steps for winners: * Create a NEAR wallet * Sign the funding agreement * Receive their prize via a Potlock donation campaign so the community can transparently support them JazakumAllahu khairan to everyone who built, judged, mentored, and shared feedback. This is just the beginning InShaAllah. #RamadanHacks #PRAYSAP

Quick question for Qivam.com, currently I don't have any monitoring and observability built into Qivam. My current setup is as follows: DB -> To check total API keys being used (In Active state) Cloudflare -> To get rough idea of site/domain traffic Cloudwatch -> AWS side metrics (horrific UI btw) There is no single place I can go and see all of this in one place or to quantify the growth of the platform. For example, seeing how many request a particular endpoint is receiving on given time range, total traffic using the APIs (Cloudflare analytics might include bots and crawlers) For this I'm only looking forward to adding a middleware that sends a log with some data like the timestamp, method (GET/POST/etc), path (the endpoint hit), status code, response time in ms, response size in bytes, the API key from the x-api-key header (only the first 8 chars), user agent, and the client IP. Now, even though I'm not logging anything sensitive like personal data, just basic metadata to understand how the API is being used. I believe in building in the open. So before I start on this, any thoughts? Anything you'd want handled differently?