Infrastructure Hosts Alert Column Width Fix

Fix to Issue #233398.

Problem Analysis

The issue was that when OpenTelemetry schema (semconv) is selected, the alerts column was taking up too much space compared to when System Integration schema (ecs) is used.

Root Cause

1. Schema-dependent columns: When OpenTelemetry schema is selected, the network columns (rx/tx) are hidden based on this condition:

   searchCriteria.preferredSchema !== 'semconv'

2. Fixed width allocation: The alerts column had a fixed width of 95px, while metric columns used percentage-based widths (12% when alerts are shown, 16% when not shown).

3. Insufficient responsive calculation: The column width calculations didn't account for the presence/absence of network columns based on the schema.

Solution Implemented

1. Dynamic Metric Column Width Calculation

const showNetworkColumns = searchCriteria.preferredSchema !== 'semconv';
const metricColumnsWidth = useMemo(() => {
  if (displayAlerts) {
    return showNetworkColumns ? '12%' : '16%';
  }
  return showNetworkColumns ? '16%' : '20%';
}, [displayAlerts, showNetworkColumns]);

2. Dynamic Title Column Width Calculation

const titleColumnWidth = useMemo(() => {
  if (displayAlerts) {
    return showNetworkColumns ? '15%' : '20%';
  }
  return showNetworkColumns ? '20%' : '25%';
}, [displayAlerts, showNetworkColumns]);

3. Reduced Alert Column Width

• Changed from width: '95px' to width: '80px' for a more compact alerts column

Width Allocation Summary

ECS Schema (with network columns):

• With alerts: Alerts: 80px, Title: 15%, Metrics: 12% each (5 columns), Network: 12% each (2 columns)
• Without alerts: Title: 20%, Metrics: 16% each (5 columns), Network: 12% each (2 columns)

OpenTelemetry Schema (without network columns):

• With alerts: Alerts: 80px, Title: 20%, Metrics: 16% each (5 columns)
• Without alerts: Title: 25%, Metrics: 20% each (5 columns)

Files Modified

• /x-pack/solutions/observability/plugins/infra/public/pages/metrics/hosts/hooks/use_hosts_table.tsx