{# Drop counter — Plan 46 idea #3 from the django_grpc audit.
   When dropped_total > 0 we're losing rows under saturation; show as red.
   Plan 58 — split rationale + action into two paragraphs for scannability. #}
<template x-if="health && health.dropped_total > 0">
  <div class="rounded-md border border-red-500/30 bg-red-500/[0.06] p-3 flex items-start gap-3">
    <i data-lucide="alert-triangle" class="w-4 h-4 text-red-300 mt-0.5 flex-shrink-0"></i>
    <div class="text-[13px] text-red-100">
      <div class="font-medium">Error logger queue saturated</div>
      <div class="text-[12px] text-red-200/80 mt-1 space-y-1">
        <p>
          <span class="font-mono font-medium" x-text="health.dropped_total"></span>
          events dropped since process start — the writer can't keep up with the
          incoming error rate, so older events are being discarded before they reach the DB.
        </p>
        <p>
          <span class="font-medium text-red-100">Next step:</span>
          look at the highest-severity event types below to find the source of the storm.
          Once the underlying issue is fixed, restart
          <code class="font-mono text-red-100">cmdop-server-api</code> to reset the counter.
        </p>
      </div>
    </div>
  </div>
</template>