Custom Trace Views

Custom views let you save filter configurations, column layouts, and sorting preferences for the Traces page. This is useful for creating role-specific dashboards, recurring debugging workflows, or team-shared analysis setups.

​

Why Use Custom Views?

Instead of reconfiguring filters every time you open the Traces page, create views for common scenarios:

• Production Errors - Filter to failed traces in production environment
• High Latency - Show traces exceeding a duration threshold
• Specific Agent - Focus on traces from a particular agent or workflow
• Cost Analysis - Sort by token usage with cost columns visible

​

Creating a Custom View

​

Step 1: Configure Your Filters

Start by setting up the filters you want to save:

1. Navigate to Observability → Traces
2. Use the filter bar to add conditions:
   • Time range - Select a relative range like “Past 24 hours” or “Past 7 days”
   • Status - Filter by success, error, or specific status codes
   • Environment - Filter by production, staging, development
   • Duration - Set minimum/maximum duration thresholds
   • Custom attributes - Filter by any attribute you’ve added to spans

​

Step 2: Configure Columns

Customize which columns appear in the trace list:

1. Click the Configure Columns button in the toolbar
2. Toggle columns on/off:
   • Name - Trace/span name
   • Duration - Total execution time
   • Status - Success/error status
   • Tokens - Total token usage
   • Cost - Estimated cost
   • Environment - Deployment environment
   • Timestamp - When the trace started
   • Custom attributes you’ve defined
3. Drag columns to reorder them

​

Step 3: Set Sorting

Click on any column header to sort by that field. Click again to toggle between ascending and descending order.

​

Step 4: Save the View

1. Click the Save View button (or the dropdown next to “Views”)
2. Enter a name for your view (e.g., “Production Errors - Last 24h”)
3. Optionally add a description
4. Choose visibility:
   • Private - Only you can see this view
   • Team - All team members can access this view
5. Click Save

​

Managing Views

​

Switching Between Views

1. Click the Views dropdown in the toolbar
2. Select from your saved views or team views
3. The page updates with the saved configuration

​

Editing a View

1. Load the view you want to edit
2. Make your changes to filters, columns, or sorting
3. Click Save View → Update Current View

​

Deleting a View

1. Click the Views dropdown
2. Hover over the view you want to delete
3. Click the trash icon
4. Confirm deletion

​

Setting a Default View

1. Click the Views dropdown
2. Click the star icon next to your preferred view
3. This view will load automatically when you open the Traces page

​

Example Views

Here are some useful views to create for your team:

​

Production Errors

​

High Token Usage

​

Slow Requests

​

Agent Debugging

​

Sharing Views with Your Team

Team views are visible to all members of your Netra project:

1. When saving a view, select Team visibility
2. Team members will see it in their Views dropdown under “Team Views”
3. Only the creator or project admins can edit/delete team views

This is useful for:

• Standardizing how your team investigates issues
• Onboarding new team members with pre-configured views
• Creating role-specific dashboards (e.g., “On-Call View”, “Cost Review”)

​

Tips for Effective Views

1. Use descriptive names - Include the key filter criteria in the name (e.g., “Prod Errors - 24h” not just “Errors”)
2. Keep views focused - Create multiple specific views rather than one complex view
3. Use relative time ranges - “Past 24 hours” stays relevant; fixed date ranges become stale
4. Document with descriptions - Add notes about when to use each view
5. Review periodically - Delete views that are no longer useful

​

Next Steps

• Comparing Traces - Compare traces side-by-side for debugging
• Traces Overview - Learn more about traces and spans