#observability

Dbauszus Are there any recommendations how to finetune the usage anomaly detection and warnings. We get these every day on various projects. We host web applications which are not continuosly used. Sometimes just for an hour each day. Sometimes just for an hour each week. Would it be possible to flag usage anomalies as regular/expected use in order to build up a model and only warn if the usage in fact significantly deviates from previous occurances flagged as expected.

system Hi @community-backoffice! Thanks for posting. I'm here to help! If you'd like to speak with a human team member, just let me know. I'd like to gather some details to better understand your use case for querying historical logs via the Vercel CLI. Could you share: - What specific log data you need your agents to access (function logs, build logs, edge logs, etc.) - How far back in history you need to query logs - What your current workflow looks like when agents need to access server logs - Any specific CLI commands or functionality you've tried This will help the team understand the requirements for this feature request.

ADALIGO **Xiaoshenwang110 4568 You protected the system fast, but lost the history of what happened. Once a project is deleted on Vercel, its logs are usually deleted too and can’t be accessed anymore from the dashboard. 👉 Not really recoverable after deletion, unless support can help or you had logs stored elsewhere.**

Pauline P. Narvas Is your application client-side rendered static site? Static site requests don’t appear in runtime, only function invocations do. This is expected behavior for React apps without server-side functionality.

ADALIGO If your React app is purely client-side rendered (CSR) or a static site, this is expected. Vercel runtime logs only capture **server-side invocations**, like API routes or serverless functions. Static pages served by React won’t appear in runtime logs, even if traffic is coming in. A couple of things you could check: * Are you using **Next.js** with any server-side functions or API routes? Those logs will show. * If not, you’d need to route logging through a serverless function to capture requests in Vercel logs.

Emma Taylor Great overview, thanks for sharing this. One thing I’ve noticed with Vercel is how much the edge network and image optimization help without extra configuration. Even basic projects feel faster once deployed. The preview deployments are also really useful for testing changes before going live, especially when working in a team. It reduces a lot of guesswork. This kind of summary is helpful for people who are new to Vercel and trying to understand where the performance gains actually come from.