Add Application Logs documentation to Dashboard guide by Jibaru · Pull Request #3311 · clerk/clerk-docs

Jibaru · 2026-04-21T18:53:58Z

Adds a new "Logs" section under Clerk Dashboard with an Application Logs overview and a supported events reference page covering all ~100+ event types.

🔎 Previews:

https://clerk.com/docs/pr/irueda-user-5222-add-system-logs-documentation/guides/dashboard/logs/application-logs

Screenshots

What does this solve? What changed?

Adds a new "Logs" section under Clerk Dashboard with an Application Logs overview and a supported events reference page
Application Logs overview covers filtering (event type, actor, subject, trace ID, device, date range), log detail view, and retention per plan
Supported events page catalogs all ~100+ event types grouped by category (sign-up, sign-in, user, session, organization, billing, SCIM, etc.)
Nav structure supports future additions (e.g., Email Logs) as siblings under "Logs"

Deadline

Probably this week.

Other resources

https://linear.app/clerk/issue/USER-5222/add-system-logs-documentation

Adds a new "Logs" section under Clerk Dashboard with an Application Logs overview and a supported events reference page covering all ~100+ event types.

vercel · 2026-04-21T18:54:02Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Apr 24, 2026 7:50pm

Collapse the Application Logs sub-tree into a single page so each log type lives at one nesting level under Logs, with Supported events as an in-page section. Prepares the structure for Email, SMS, and Admin logs without duplicated reference pages. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

- Point the Dashboard link at the actual Logs page (`/~/logs`). - Use the repo's relative `/pricing` convention. - Name Production and Development explicitly in the retention note. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

manovotny · 2026-04-21T23:05:50Z

Pushed some changes directly in 29b4de6.

Swapped the Logs link from the Dashboard root to /~/logs
Changed the pricing link from absolute to relative (/pricing)
Tightened the retention note to name Production and Development explicitly

I'll leave the rest as inline comments.

manovotny · 2026-04-21T23:05:51Z

+
+Retention periods apply equally to Production and Development instances.
+
+## Supported events


I'm guessing these 100+ events transcribed by hand. What's the plan to keep it in sync with the Dashboard's Event Catalog?

I think it could be good to have a script at least to perform these updates, something like:

Add a new event (or update/remove a current one)

Run the script

Copy the output to the docs repo

It stills manually, but could work so far.

We have other scripts to keep things in sync that we could borrow inspiration from.

This can be a follow up PR(s). I just want us keeping longer-term maintenance in mind.

Can you link me to the repo/source files where these originate from?

They originate from this proto file:
https://github.com/clerk/clerk_go/blob/main/api/shared/event_stream/payloads.proto

We are using the ones that have only option tag called system_log for this application logs.

Task for creating the sync script → https://linear.app/clerk/issue/DOCS-11699/add-a-sync-for-application-log-events

Thanks! I see that you have it assigned, I could also take it on, just in case.

@Jibaru you're welcome to take a stab at it. I assigned it because I didn't want to lose track of it.

Distinguishes a public breach database match (`pwned`) from an admin- or policy-triggered mandatory reset (`compromised`) so folks filtering logs know which signal they're looking at. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

Correct the retention periods for Business (60 → 30 days) and Enterprise (120 → 30 days) plans to match the actual values.

Remove duplicate user-scoped email address and phone number event sections (user.email_address.* and user.phone_number.*) and add missing verified events (email_address.verified, phone_number.verified) to the standalone event tables.

Update web3 wallet event types to match the proto system_log definitions by removing the `user.` prefix.

Jibaru · 2026-04-23T14:31:41Z

Adding this too

manovotny · 2026-04-23T15:43:18Z

Adding this too

Two thoughts:

I'm torn if the Logs folder should have beta on it. Application Logs for sure.
For all betas, we add a warning callout at the top. Since there's just one page (for now), you don't have to make a partial, but here's some examples for Expo and MCP server we have for right now. This should go at the very top of the Application Logs page.

Add a beta warning callout at the top of the Application Logs page and a (Beta) tag to the navigation entry in the manifest.

The note about payloads being omitted from the list view exposed backend implementation details not relevant to users.

Jibaru · 2026-04-23T19:44:43Z

Updated with all of your feedback. Only missing the url we are going to use to redirect to the Logs Dashboard. @brunol95 @manovotny

Move the web3 wallet subsection alongside Email address and Phone number at the top level so its placement matches its prefix-less identifiers, and tighten the descriptions to match the generic phrasing those sibling sections use. Mark the page title as beta. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

The (Beta) manifest tag and the beta WARNING callout added in fc3530f already signal beta status, so keep the page title clean. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

manovotny · 2026-04-23T19:57:51Z

Pushed some changes directly in 1acbfdf.

Promoted Web3 wallet events out of the User events nest to a top-level section alongside Email address and Phone number, since the identifiers no longer carry the user. prefix. Tightened the descriptions to match the generic phrasing those sibling sections use.
Dropped my local (beta) from the page title — the (Beta) manifest tag and the beta WARNING callout already cover it.

dmoerner · 2026-04-23T19:58:01Z

~~Nice work @Jibaru! The web3 wallet events look out of place under the "User" heading, perhaps they should have their own heading like email and phone~~. It looks like Michael just fixed that 😂

manovotny · 2026-04-24T14:30:47Z

All we're waiting on is the final url, correct?

Jibaru · 2026-04-24T14:34:11Z

All we're waiting on is the final url, correct?

Yes, and an approval from project leader

The Enterprise plan offers custom retention periods rather than a fixed 30-day limit. Update the retention table to reflect this.

Add Application Logs documentation to Dashboard guide

73ec48a

Adds a new "Logs" section under Clerk Dashboard with an Application Logs overview and a supported events reference page covering all ~100+ event types.

Jibaru requested a review from a team as a code owner April 21, 2026 18:53

manovotny and others added 2 commits April 21, 2026 17:02

vercel Bot deployed to Preview April 21, 2026 23:06 View deployment

manovotny reviewed Apr 22, 2026

View reviewed changes

Update docs/guides/dashboard/logs/application-logs.mdx

f76bdad

vercel Bot deployed to Preview April 22, 2026 14:35 View deployment

vercel Bot deployed to Preview April 22, 2026 14:41 View deployment

Jibaru added the do not merge label Apr 22, 2026

brunol95 reviewed Apr 22, 2026

View reviewed changes

Comment thread docs/guides/dashboard/logs/application-logs.mdx Outdated

brunol95 reviewed Apr 22, 2026

View reviewed changes

Comment thread docs/guides/dashboard/logs/application-logs.mdx Outdated

fix(docs): Update Application Logs retention for Business and Enterprise

4313b85

Correct the retention periods for Business (60 → 30 days) and Enterprise (120 → 30 days) plans to match the actual values.

vercel Bot deployed to Preview April 22, 2026 20:34 View deployment

vercel Bot deployed to Preview April 22, 2026 20:46 View deployment

docs(logs): Remove user prefix from web3 wallet event types

d7a5491

Update web3 wallet event types to match the proto system_log definitions by removing the `user.` prefix.

vercel Bot deployed to Preview April 22, 2026 21:12 View deployment

Jibaru requested a review from manovotny April 23, 2026 14:10

brunol95 reviewed Apr 23, 2026

View reviewed changes

Comment thread docs/guides/dashboard/logs/application-logs.mdx Outdated

docs(logs): Add beta indicators to Application Logs

fc3530f

Add a beta warning callout at the top of the Application Logs page and a (Beta) tag to the navigation entry in the manifest.

vercel Bot deployed to Preview April 23, 2026 19:41 View deployment

docs(logs): Remove internal payload implementation note

7ed39a6

The note about payloads being omitted from the list view exposed backend implementation details not relevant to users.

vercel Bot deployed to Preview April 23, 2026 19:43 View deployment

manovotny and others added 2 commits April 23, 2026 14:56

Drop redundant (beta) from page title

1acbfdf

The (Beta) manifest tag and the beta WARNING callout added in fc3530f already signal beta status, so keep the page title clean. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>

vercel Bot deployed to Preview April 23, 2026 19:59 View deployment

docs(logs): Update Enterprise retention to Custom

78d5bed

The Enterprise plan offers custom retention periods rather than a fixed 30-day limit. Update the retention table to reflect this.

vercel Bot deployed to Preview April 24, 2026 14:45 View deployment

update link to logs

711b91a

vercel Bot deployed to Preview April 24, 2026 19:50 View deployment


		Retention periods apply equally to Production and Development instances.

		## Supported events

Conversation

Jibaru commented Apr 21, 2026 • edited by manovotny Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔎 Previews:

What does this solve? What changed?

Deadline

Other resources

Uh oh!

vercel Bot commented Apr 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

manovotny commented Apr 21, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

manovotny Apr 21, 2026

Choose a reason for hiding this comment

Uh oh!

Jibaru Apr 22, 2026

Choose a reason for hiding this comment

Uh oh!

manovotny Apr 22, 2026

Choose a reason for hiding this comment

Uh oh!

Jibaru Apr 22, 2026

Choose a reason for hiding this comment

Uh oh!

manovotny Apr 22, 2026

Choose a reason for hiding this comment

Uh oh!

Jibaru Apr 22, 2026

Choose a reason for hiding this comment

Uh oh!

manovotny Apr 23, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Jibaru commented Apr 23, 2026

Uh oh!

manovotny commented Apr 23, 2026

Uh oh!

Uh oh!

Jibaru commented Apr 23, 2026

Uh oh!

manovotny commented Apr 23, 2026

Uh oh!

dmoerner commented Apr 23, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

manovotny commented Apr 24, 2026

Uh oh!

Jibaru commented Apr 24, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Jibaru commented Apr 21, 2026 •

edited by manovotny

Loading

vercel Bot commented Apr 21, 2026 •

edited

Loading

dmoerner commented Apr 23, 2026 •

edited

Loading