如何启用FusionAuth系统事件日志？1.6.1版本无事件捕获问询

Hey there! Let's figure out why you're not seeing any event logs in FusionAuth 1.6.1—you’re totally right to think there might be a missing configuration step here. I’ve helped a few folks troubleshoot this exact issue with older FusionAuth versions, so let’s walk through the key checks:

1. First, Check Tenant-Level Event Settings #

FusionAuth lets you control event logging per tenant, so this is the first place to look:

• Log into your FusionAuth admin dashboard
• Head to Tenants, pick the tenant you’re working with, then go to the Event Log tab
• Make sure the Enable Event Log toggle is flipped on
• Under Event Types, don’t forget to check the boxes for the specific events you want to track (like logins, registrations, token failures—none of these are enabled by default!)
• Hit Save to lock in those changes

2. Verify System-Wide Event Log Configuration #

Next, confirm the system-level settings are allowing events to be saved:

• Go to Settings > System, then scroll down to the Event Log section
• Ensure Enable Event Log is set to "Yes"
• Double-check the Retention Period—even if it’s set to a day, events should still show up temporarily, so this isn’t usually the issue unless it’s set to zero.

3. Trigger a Test Event to Validate #

Once your settings are updated, do something that should generate an event to test things out:

• Log in a user (even a failed login works!)
• Register a new test user
• Revoke an existing user’s token
  Then pop back to the Event Log page for your tenant—you should see that event show up if everything’s configured right.

4. Check Database Permissions & Logs #

If you’re self-hosting FusionAuth, the database user might not have the right permissions to write event logs:

• Make sure the database user FusionAuth uses has INSERT and SELECT access to the event_log table
• Take a peek at FusionAuth’s application logs (look in the logs folder of your installation, or container logs if you’re using Docker) for any errors about failing to write to the database—those can point to permission issues or migration problems.

5. Version-Specific Notes for 1.6.1 #

Since 1.6.1 is an older release, keep these in mind:

• Some newer event types (like advanced webhook events) aren’t available here, so don’t expect those to show up
• If you upgraded to 1.6.1 from an earlier version, make sure you ran the required database migration scripts—skipped migrations can break event logging entirely.

If you’ve gone through all these steps and still don’t see events, try restarting the FusionAuth service to make sure all config changes take effect. That often fixes any lingering issues!

内容的提问来源于stack exchange，提问作者David Wilson