Usage and Logs
While Platform Insights gives you a real-time snapshot, the Usage and Logs section provides historical analysis tools for tracking trends, diagnosing issues, and auditing connector behavior over specific time periods.
Usage Monitor
The Usage Monitor lets you examine platform metrics across configurable date ranges. Navigate to Insights & Monitoring > Usage Monitor to access it.
Selecting a Time Period
Use the date range picker at the top of the page to define your analysis window.
| Preset | Range |
|---|---|
| Last 24 Hours | Rolling 24-hour window from the current time. |
| Last 7 Days | The previous 7 calendar days. |
| Last 30 Days | The previous 30 calendar days. |
| Custom | Select a start date and end date manually. |
Available Metrics
The metric dropdown lets you select which measurement to chart. The following metrics are available.
| Metric | Unit | Description |
|---|---|---|
| Query Count | Count | Total number of queries executed across all users and data sources. |
| Query Runtime | Minutes | Cumulative execution time for all queries. |
| Active Users | Count | Unique users with at least one interaction per day. |
| Data Transferred | MB / GB | Volume of data returned from Edge nodes to the Coordinator. |
| Error Rate | Percentage | Proportion of queries that returned an error response. |
| P95 Latency | Milliseconds | The 95th-percentile query latency, indicating typical worst-case response time. |
Filtering and Grouping
You can filter and group usage data to isolate specific patterns.
| Filter | Options |
|---|---|
| Data Source | Select one or more connected data sources. |
| User | Filter by individual user or group. |
| Query Type | SELECT, INSERT, UPDATE, DELETE, or DDL. |
| Status | Success, Error, or Timeout. |
Group by Data Source, User, or Day to segment the chart into separate series for comparison.
To identify your most resource-intensive queries, filter by Query Runtime and group by User. This reveals which users or workflows consume the most compute.
Connector Log
The Connector Log provides a detailed, searchable record of every interaction between Edge nodes and your data sources. Navigate to Insights & Monitoring > Connector Log.
Log Entry Fields
Each log entry contains the following fields.
| Field | Description |
|---|---|
| Timestamp | The exact date and time of the event (in your workspace timezone). |
| Connector | The data source connector that handled the event (e.g., snowflake-prod). |
| Event Type | The type of activity: query, schema_refresh, connection_test, sync. |
| Status | The outcome: success, error, timeout. |
| Duration | How long the operation took, in milliseconds. |
| User | The user who initiated the action (or system for automated operations). |
| Query Preview | A truncated preview of the executed SQL statement (first 200 characters). |
| Error Detail | If the status is error, the full error message from the data source. |
Searching and Filtering
The log supports full-text search and column-level filters.
- Search bar: Enter keywords to search across all fields (e.g., a table name, error keyword, or user email).
- Connector dropdown: Filter to a specific data source.
- Status dropdown: Show only successes, errors, or timeouts.
- Date range: Narrow the log to a specific time window.
Exporting Logs
You can export the filtered log view for offline analysis or compliance auditing.
| Format | Description |
|---|---|
| CSV | Comma-separated values. Compatible with spreadsheets and data tools. |
| JSON | Structured format suitable for ingestion into log aggregation systems. |
Click the Export button in the top-right corner of the log panel. The export respects your current filters and date range.
Connector logs are retained for 90 days by default. Contact your workspace administrator to adjust the retention period if your compliance requirements differ.
Interpreting Common Patterns
| Pattern | Possible Cause | Recommended Action |
|---|---|---|
| Spike in error rate | Data source maintenance or credential expiration. | Check the connector log for specific error messages and verify source availability. |
| Gradual increase in P95 latency | Growing data volumes or inefficient queries. | Review slow queries and consider indexing or query optimization. |
| Drop in active users | Seasonal variation or access issues. | Cross-reference with user management to check for deactivated accounts. |
| High data transfer volume | Large result sets or frequent full-table scans. | Add filters or pagination to reduce result set sizes. |
Next Steps
- Platform Insights -- Return to the real-time dashboard for current status.
- Events and Notifications -- Set up alerts based on usage thresholds.