This article explains how to analyze changes, track events, and troubleshoot manual actions using the Logs tab.
Content:
Purpose
The Urbantz Logs Tab serves as a centralized audit trail and monitoring system that provides transparency and traceability for all platform activities. It captures critical events including resource updates, configuration changes, user actions, and system operations to support compliance, troubleshooting, and operational analytics.
Key Functions
Transparency & Compliance: Maintains a complete audit trail of all platform activities for regulatory compliance and accountability.
Troubleshooting: Enables support teams and administrators to quickly identify what went wrong, when, and who was responsible for changes.
Operational Monitoring: Tracks automated processes like optimizations, announcements, and notifications to ensure system reliability.
How to Use the Logs Tab
Access: Available to users with appropriate permissions on the Administration section of Urbantz.
Filtering: Use the built-in filters to narrow down logs by:
- Log type (ACCESS, TASK, ROUND, OPTIMIZATION, etc.)
- Date/time range
Log Categories: The system categorizes logs into 17 types including:
- TASK: Task creation, updates, and status changes
- ROUND: Round creation and round editor operations
- OPTIMIZATION: Optimization launches
- ACCESS: Login attempts and user access events
- NOTIFICATION: SMS and communication logs
- GENERAL: Platform and flow updates
Example:
Below is the result of a log analysis performed on optimization activity. By filtering for the "Optimization" type and selecting a specific date range, one can identify all optimization events that occurred during that period.
In this example, we can see that two users initiated optimizations through the Round Editor (RE) interface.
Best Practices
Use Specific Time Ranges: Always narrow down your search with precise date/time filters to improve performance and reduce clutter.
Combine Multiple Filters: Use log type filters together with date ranges for more targeted results. For example, filter by "TASK" + specific date when investigating task-related issues.
Search by Resource Names: When possible, search using specific resource identifiers like task IDs, round names, or hub names rather than generic terms.
Comments
0 comments
Please sign in to leave a comment.