Functions

Monitor Clerk with MrCron

MrCron mirrors Clerk total users, signup counts, and active session counts every 5 minutes so you can watch auth health alongside errors and analytics.

How MrCron monitors Clerk

  • Total users on your Clerk instance.
  • Signup count for the last 24 hours.
  • Active session count at the last sync.
  • Auth-failure detection with an amber Rotate key CTA when the secret key stops working.
  • Alert rules that fire on signup thresholds via any notification channel.

What you will see

Total users, signups (24h), active sessions on your project card.

Auth flow: API Key. Credentials are stored encrypted at rest with AES-256-GCM and never returned to your browser.

Start monitoring Clerk

Sign in, create a project, and connect Clerk in under a minute. First check ships in the free tier.

Start monitoring Clerk

Frequently asked questions

What Clerk credentials does MrCron need?
A Clerk secret key from the API keys page in the Clerk dashboard. MrCron stores it encrypted at rest and only decrypts it inside the sync worker.
Does MrCron read user records?
No. MrCron reads aggregate counts (total users, signups, sessions). Individual user records are never fetched.
How fresh is the signup count?
Refreshed every 5 minutes on the shared sync cycle. The count is a rolling 24h total.
Can I alert on a signup drop?
Yes. Create an alert rule on the clerk_signups_24h metric with a threshold below your baseline and route it to any notification channel.
Want the full concept-level detail? See MrCron docs for how projects, checks, and sync cadence work.