Skip to content

Commit 3a572ad

Browse files
authored
Update 2025-07-28-alerts.md
1 parent afac3bf commit 3a572ad

File tree

1 file changed

+2
-12
lines changed

1 file changed

+2
-12
lines changed

blog-service/2025-07-28-alerts.md

Lines changed: 2 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -8,22 +8,12 @@ keywords:
88
hide_table_of_contents: true
99
---
1010

11-
To help you optimize query execution and improve data retrieval efficiency, we’ve introduced time range limits for sub-queries in scheduled searches.
11+
We've introduced time range limits for sub-queries in scheduled searches. This change helps you prevent long-running, inefficient queries, especially those impacting system stability and that drive up costs. While maintaining flexibility, these optimizations protect system health and reduce operational overhead.
1212

13-
Key benifits of this enhancements include:
13+
Key benefits of this enhancements include:
1414

1515
- Improved query performance and responsiveness.
1616
- Encourage efficient search practices.
1717
- Support sustainable resource usage.
1818

19-
**Who benefits**
20-
21-
Data analysts, IT operations, and security engineers seeking faster, more efficient investigations without compromising functionality.
22-
23-
**Why it matters?**
24-
25-
Inefficient long-term queries cost millions in compute resources and delay resolution times. This update keeps our platform high-performing and cost-effective, without sacrificing power or usability.
26-
27-
This change helps prevent long-running, inefficient queries, especially those impacting system stability and driving up costs. While maintaining flexibility, these optimizations protect system health and reduce operational overhead.
28-
2919
[Learn more](/docs/alerts/scheduled-searches/schedule-search/#step-3-time-range).

0 commit comments

Comments
 (0)