fix: ensure enrichment fields are always available in column selection

[shahargl]

close #5264

Summary

Fixed issue where enrichment fields would not appear in the column selection settings if they weren't present in the first 50 rows of data.

Problem

When a feed/preset doesn't contain any enrichment fields in the first 50 rows, the 'Enrich fields' column option becomes disabled and unavailable for selection. This happens because the column selection only shows columns that exist in the current dataset.

Solution

• Added a predefined list of common enrichment fields that are always available for selection
• These fields are now searchable even when they don't exist in the current data
• Maintains existing functionality while ensuring enrichment fields are always accessible

Common Enrichment Fields Added

• ticket_id, ticket_url, ticket_type, ticket_status
• environment, service, region, cluster, namespace
• pod, container, host, instance, application
• team, owner, runbook_url, dashboard_url
• logs_url, metrics_url, impacted_customer_name
• severity_override, priority, escalation_policy
• on_call_engineer, alert_enrichment

Testing

• Users can now search for "enrich" in the column settings and find enrichment fields
• Column selection works regardless of whether enrichment data exists in current alerts
• No duplicate columns when enrichment fields exist in both data and predefined list

Closes #5264

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
keep	Ready	Preview	Comment	Aug 26, 2025 2:16pm