Event Logs
Complete Activity Timeline
Event logs provide a chronological record of all system events including enrollment, profile changes, impersonation sessions, and platform interactions. They serve as your digital trail for troubleshooting and compliance purposes.
What Are Event Logs?
Event logs are detailed records of system activities that capture every significant action taken within the TALON platform. These logs provide visibility into member behavior, system operations, and support activities for troubleshooting and audit purposes.
- Account registrations and activations
- Profile updates and changes
- Password resets and security changes
- Login and logout events
- Healthcare provider searches
- Member impersonation sessions
- Profile modifications by support
- Case creation and updates
- Account unlocks and resets
- Support notes additions
- Data synchronization processes
- System maintenance activities
- Error occurrences and exceptions
- Configuration changes
- Security-related events
- Group enrollment processes
- Employer configuration changes
- Mass communication sends
- Report generation and exports
- Engagement tracking updates
How to Access Event Logs
Search for and select the specific member whose activity logs you need to review.
Look for the "Event Logs" tile within the member's profile interface.
Understanding Log Entries
Event log entries follow a consistent format that includes timestamps, event types, and detailed descriptions. Here's an example of typical log entries:
Common Use Cases
Event Log Use Cases
"Member says they can't log in, but their account appears active."
Solution: Check event logs for failed login attempts, password reset requests, or account lockout events to identify the root cause.
"Suspicious activity reported on member account."
Solution: Review login patterns, IP addresses, and unusual activity timeframes to determine if unauthorized access occurred.
"Member claims they didn't change their information."
Solution: Trace profile modification events to see who made changes, when they occurred, and what specific data was altered.
"Member can't find providers they're looking for."
Solution: Examine search query logs to understand what terms they used and optimize their search strategy.
Best Practices
When investigating issues, begin by narrowing down the time period when the problem occurred to reduce log volume and focus your analysis.
Identify recurring issues, timing patterns, or unusual activity that might indicate systematic problems or security concerns.
When troubleshooting specific issues, focus on events within the relevant timeframe rather than reviewing entire log history.
Combine event log information with session recordings, support notes, and member feedback for complete understanding.
Add important event log findings to support notes so other team members can benefit from your investigation.
Escalate suspicious patterns, security concerns, or system issues discovered through event log analysis to appropriate teams.
Privacy and Security Reminder
Event logs contain sensitive member activity data. Use this information solely for legitimate support purposes and maintain strict confidentiality. Never share event log details with unauthorized personnel.
Integration with Other Support Tools
Powerful Combinations
Event logs work best when combined with other support tools. Use them together for comprehensive member support and issue resolution.
Tool Combinations for Maximum Effectiveness
- Event Logs + Session Recordings: See what happened (logs) and watch how it happened (recordings)
- Event Logs + Support Notes: Understand technical events and human context together
- Event Logs + Member Profile: Connect activity patterns with member demographics and preferences
- Event Logs + Impersonation: Review past events, then test current functionality safely
Pro Tip
When troubleshooting complex issues, start with event logs to identify when problems began, then use session recordings to see exactly what the member experienced, and document your findings in support notes.