From c778b0a5a9e3086ef5738e59d7a22159945f34e2 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Thu, 6 Aug 2026 02:25:27 -0700 Subject: [PATCH 1/2] fix(cli): state the 100-row server cap in alert/alert-event --limit flag help The alert list and alert-event list endpoints reject limit > 100 with InvalidParameter. incident list already documents the cap in its --limit flag help; mirror the same wording so the Flags section alone is enough to get the first call right (the long description mentions the cap, but --help readers who grep Flags never see it). --- internal/cli/alert.go | 2 +- internal/cli/alert_event.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/cli/alert.go b/internal/cli/alert.go index d460193..1f216a5 100644 --- a/internal/cli/alert.go +++ b/internal/cli/alert.go @@ -111,7 +111,7 @@ func newAlertListCmd() *cobra.Command { cmd.Flags().BoolVar(&muted, "muted", false, "Show ever-muted only") cmd.Flags().StringVar(&since, "since", "24h", "Start time") cmd.Flags().StringVar(&until, "until", "now", "End time") - cmd.Flags().IntVar(&limit, "limit", 20, "Max results") + cmd.Flags().IntVar(&limit, "limit", 20, "Max results (max 100)") cmd.Flags().IntVar(&page, "page", 1, "Page number") cmd.Flags().StringVar(&fields, "fields", "", "Comma-separated fields to project in json/toon output (e.g. alert_id,title,alert_severity,created_at); ignored in table mode. Use to avoid dumping the full nested record.") diff --git a/internal/cli/alert_event.go b/internal/cli/alert_event.go index dbb7024..4e8c0fb 100644 --- a/internal/cli/alert_event.go +++ b/internal/cli/alert_event.go @@ -104,7 +104,7 @@ func newAlertEventListCmd() *cobra.Command { cmd.Flags().StringVar(&integrationType, "integration-type", "", "Comma-separated integration types") cmd.Flags().StringVar(&since, "since", "1h", "Start time") cmd.Flags().StringVar(&until, "until", "now", "End time") - cmd.Flags().IntVar(&limit, "limit", 20, "Max results") + cmd.Flags().IntVar(&limit, "limit", 20, "Max results (max 100)") cmd.Flags().IntVar(&page, "page", 1, "Page number") cmd.Flags().StringVar(&fields, "fields", "", "Comma-separated fields to project in json/toon output (e.g. event_id,alert_id,event_severity,event_status,event_time,title); ignored in table mode. Defaults to these compact event fields. Long strings are truncated as needed to keep structured output below 16 KiB.") From 99dc3dc4dac9bbcc81dbac10f2f8167bf1e62e81 Mon Sep 17 00:00:00 2001 From: ysyneu Date: Thu, 6 Aug 2026 02:40:51 -0700 Subject: [PATCH 2/2] fix(cli): state the 100-row cap on insight incidents --limit too Same shared page-query validator as alert/alert-event/incident list; same wording. --- internal/cli/insight.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/cli/insight.go b/internal/cli/insight.go index f3b4a5f..a2e02bd 100644 --- a/internal/cli/insight.go +++ b/internal/cli/insight.go @@ -138,7 +138,7 @@ func newInsightIncidentsCmd() *cobra.Command { cmd.Flags().StringVar(&since, "since", "7d", "Start time") cmd.Flags().StringVar(&until, "until", "now", "End time") - cmd.Flags().IntVar(&limit, "limit", 20, "Max results") + cmd.Flags().IntVar(&limit, "limit", 20, "Max results (max 100)") cmd.Flags().IntVar(&page, "page", 1, "Page number") return cmd