From af84cd71ad23e2b2001cdacf7a238441100f2074 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Tue, 2 Sep 2025 10:43:46 +0530 Subject: [PATCH 1/3] Update scheduled-views-best-practices.md --- .../scheduled-views/scheduled-views-best-practices.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/manage/scheduled-views/scheduled-views-best-practices.md b/docs/manage/scheduled-views/scheduled-views-best-practices.md index 52f90290a9..61e8161c20 100644 --- a/docs/manage/scheduled-views/scheduled-views-best-practices.md +++ b/docs/manage/scheduled-views/scheduled-views-best-practices.md @@ -222,6 +222,8 @@ _view=nice_view_man | timeslice 1d | sum(_count) by _timeslice, status_code ## FAQ -### Upgrade your scheduled views to avoid negative count results +### How to avoid negative count results? -The existing scheduled views will use the `Int` data type for the `count` operator, giving a negative count value after crossing the maximum integer value of `2147483647`. To resolve this, create a new scheduled view with the same starting date as the old scheduled view. These new scheduled views will utilize the `Long` data type for the `count` operator and will not provide negative values. +Validate if you are using the scheduled views created before August 28th, 2024. The scheduled views created before this date will use the `Int` data type for the `count` operator, inturn resulting in a negative count value after crossing the maximum integer value of `2147483647`. + +To resolve this, create a new scheduled view with the same starting date as the old scheduled view. These new scheduled views will utilize the `Long` data type for the `count` operator and will not provide negative values. From 1f26784cbaebb25cbe1684a527f5f7c1de7d9fbf Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Tue, 2 Sep 2025 11:35:38 +0530 Subject: [PATCH 2/3] Update docs/manage/scheduled-views/scheduled-views-best-practices.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/manage/scheduled-views/scheduled-views-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manage/scheduled-views/scheduled-views-best-practices.md b/docs/manage/scheduled-views/scheduled-views-best-practices.md index 61e8161c20..f6124d59ad 100644 --- a/docs/manage/scheduled-views/scheduled-views-best-practices.md +++ b/docs/manage/scheduled-views/scheduled-views-best-practices.md @@ -224,6 +224,6 @@ _view=nice_view_man | timeslice 1d | sum(_count) by _timeslice, status_code ### How to avoid negative count results? -Validate if you are using the scheduled views created before August 28th, 2024. The scheduled views created before this date will use the `Int` data type for the `count` operator, inturn resulting in a negative count value after crossing the maximum integer value of `2147483647`. +Validate if you are using the scheduled views created before August 28, 2024. The scheduled views created before this date will use the `Int` data type for the `count` operator, inturn resulting in a negative count value after exceeding the maximum integer value of `2147483647`. To resolve this, create a new scheduled view with the same starting date as the old scheduled view. These new scheduled views will utilize the `Long` data type for the `count` operator and will not provide negative values. From 4d109c8491b91792dd1cd2cee103e714fb2e6ade Mon Sep 17 00:00:00 2001 From: Jagadisha V Date: Tue, 2 Sep 2025 11:37:14 +0530 Subject: [PATCH 3/3] minor fix --- blog-service/2024/12-31.md | 2 +- docs/manage/scheduled-views/scheduled-views-best-practices.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/blog-service/2024/12-31.md b/blog-service/2024/12-31.md index 44a904fb50..f2872dfad4 100644 --- a/blog-service/2024/12-31.md +++ b/blog-service/2024/12-31.md @@ -564,7 +564,7 @@ We're excited to announce the release of the updated version of Azure Functions We're happy to announce a change to the behaviour of the `count` operator to return `Long` values. Previously, the `count` operator returned `Int` data type which could lead to a negative value if the maximum integer value was exceeded. With this change, we are changing the data type of the count operator result from `Int` to `Long` data type. -This change will apply to all new queries. Any existing queries as part of various content types - Log Search, Scheduled Search, [Lookup Table](/docs/search/lookup-tables/manage-update-lookup-tables/#upgrade-the-lookup-table-to-avoid-negative-count-results), [Scheduled Views](/docs/manage/scheduled-views/scheduled-views-best-practices/#upgrade-your-scheduled-views-to-avoid-negative-count-results), and Saved Search will also seamlessly transition to show `Long` values in case of `Int` overflow. +This change will apply to all new queries. Any existing queries as part of various content types - Log Search, Scheduled Search, [Lookup Table](/docs/search/lookup-tables/manage-update-lookup-tables/#upgrade-the-lookup-table-to-avoid-negative-count-results), [Scheduled Views](/docs/manage/scheduled-views/scheduled-views-best-practices/#how-to-avoid-negative-count-results), and Saved Search will also seamlessly transition to show `Long` values in case of `Int` overflow. ### August 27, 2024 (Collection) diff --git a/docs/manage/scheduled-views/scheduled-views-best-practices.md b/docs/manage/scheduled-views/scheduled-views-best-practices.md index 61e8161c20..da00bdf031 100644 --- a/docs/manage/scheduled-views/scheduled-views-best-practices.md +++ b/docs/manage/scheduled-views/scheduled-views-best-practices.md @@ -222,7 +222,7 @@ _view=nice_view_man | timeslice 1d | sum(_count) by _timeslice, status_code ## FAQ -### How to avoid negative count results? +### How to avoid negative count results Validate if you are using the scheduled views created before August 28th, 2024. The scheduled views created before this date will use the `Int` data type for the `count` operator, inturn resulting in a negative count value after crossing the maximum integer value of `2147483647`.