Viewing Logs

The Logs tab is where you browse, search, and investigate log entries for your project.

Accessing the Logs Tab

From the Projects dashboard:

1. Click View Logs on any project card
2. Or open a project and click the Logs tab

Logs Page Layout

Page Header

• Heading: "Recent Logs"
• Controls:
  • Columns button - Toggle which index columns are visible
  • Add Filter button - Create filters to narrow results
  • Refresh icon - Reload logs manually

Logs Table

The table displays your log entries with the following columns:

Default Columns

• Level - Log severity (displayed as colored badge)
• Count - Number of times this log occurred
• Last Seen - When the log was last received (relative time)

Dynamic Columns

• One column for each indexed field in your project settings
• Toggle visibility using the Columns button
• Column headers match your index names (e.g., context.userId)

Actions Column

Each row has two action buttons:

• View Detail - Opens the full log payload in a modal
• View Timeline - Displays a chronological history of occurrences for this specific log, subject to your current deduplication settings

Managing Column Visibility

Click the Columns button to open the column menu:

• Shows all indexed fields from your project settings
• Check/uncheck fields to show/hide columns
• Checked columns display a checkmark icon
• Changes apply immediately to the table

Column Organization

Hide columns you don't need for your current investigation. Different investigations may need different column configurations.

Filtering Logs

Click Add Filter to create a new filter.

Filter Components

Each filter has:

1. Field Selector - Choose which field to filter

   • Available fields: all indexes, raw indexes, and "level"
   • Placeholder: "Filter field"

2. Operator (for raw indexes only)

   • Only shown if the field is a raw indexed field
   • Options:
     • = (equals)
     • > (greater than)
     • ≥ (greater than or equal)
     • < (less than)
     • ≤ (less than or equal)

3. Value Input

   • For raw indexes with operators: Number input
   • For hashed indexes or = operator: Dropdown with existing values
   • Dropdown includes "All" option plus all distinct values for that field

4. Remove Filter button - Click to remove this filter

Filter Behavior

• Multiple filters can be applied simultaneously
• Filters work together (AND logic)
• Remove filters if results become too narrow
• Changes apply immediately

Exact Match Only

Due to hashed indexing for privacy, Logstyx supports exact match queries only for hashed fields. Partial or fuzzy text search is not available. See Limitations.

Filter Examples

Example 1: Filter by level

• Field: level
• Value: ERROR
• Result: Shows only error-level logs

Example 2: Filter by numeric range

• Field: data.responseTime (raw index)
• Operator: >
• Value: 1000
• Result: Shows logs where response time > 1000ms

Example 3: Filter by user

• Field: context.userId
• Value: user_12345
• Result: Shows logs for that specific user

Sorting Logs

Click any column header to sort:

• First click: Sort ascending
• Second click: Sort descending
• Sort applies to the entire result set

Common sorting patterns:

• Last Seen - Find most recent or oldest logs
• Count - Find most/least frequent logs
• Level - Group by severity

restricted sorting

Due to privacy-focused hashed indexing, Logstyx does not support sorting by indexed fields. See Limitations.

Viewing Log Details

Click the View Detail button on any log row to open the Log Detail modal.

Log Detail Modal

Modal Title: "Log Detail"

Fields shown:

• Level - Log severity
• Count - Number of occurrences
• Device - Device information (JSON format)
• Last Seen - Date and time string
• Context - Context data (JSON format)
• Data - Log payload data (JSON format)

Click Close to exit the modal.

Viewing Timeline

Click the View Timeline button on any log row to open the Timeline modal.

Timeline Modal

Modal Title: "Log Timeline"

Contents:

• Bar chart showing log counts over time
• Events related to the selected log
• Visual representation of activity patterns

Click Close to exit the modal.

Using Timeline

Timeline is useful for understanding what happened before and after a specific event, helping you debug complex issues with multiple related logs.

Pagination

Navigate through log pages using the pagination controls at the bottom:

• Shows current page and total pages
• Click page numbers to jump to specific pages
• Use arrow buttons for previous/next page

Log Level Colors

Logs are color-coded by severity:

• Info - Blue/normal color
• Warning - Yellow/orange color
• Error - Red color
• Critical - Dark red/urgent color

Colors help you quickly identify severity when scanning the table.

Common Workflows

A) Investigate Recent Errors

1. Open the Logs tab
2. Click Add Filter
3. Select field: level
4. Select value: ERROR
5. Sort by Last Seen (descending)
6. Click View Detail on recent errors
7. Check Timeline to see related events

B) Find Slow Requests

1. Add filter on data.responseTime (raw index)
2. Set operator: >
3. Enter value: 1000 (milliseconds)
4. Review results to identify slow operations
5. Click View Detail to see full request context

C) Track User Activity

1. Add filter on context.userId
2. Select the specific user
3. Review all logs for that user
4. Use Timeline to see user's journey
5. Identify patterns or issues

D) Monitor Critical Issues

1. Add filter: level = CRITICAL
2. Check Count to see frequency
3. Click View Detail for stack traces
4. Use information to create alerts or fix issues

Tips for Effective Investigation

Building Filters

• Start broad, then narrow down
• Use multiple filters for precise queries
• Remove filters if results are empty
• Combine level filters with field filters

Column Management

• Show only relevant columns for current task
• Hide noisy columns to focus on key data
• Adjust columns per investigation type

Using Counts

• High counts indicate repeated issues
• Low counts might be edge cases
• Sort by count to prioritize fixes

Refresh Behavior

• Logs update automatically in real-time
• Click Refresh to force immediate update
• Use refresh after making system changes