Skip to content

Commit b444d37

Browse files
authored
Update create-real-time-alert.md
1 parent 9761d93 commit b444d37

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

i18n/ja/alerts/alerts/scheduled-searches/create-real-time-alert.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,10 @@ Real-time alerts are scheduled searches that run nearly continuously. That means
99

1010
When an alert condition is satisfied Sumo Logic triggers the selected alert type. Sumo Logic examines ingested data in a rolling window using the Time Range you define. Any time a new result is found, another email is sent.
1111

12+
:::note
13+
Only use real time schedules when you know your data is ingested within a few minutes of its creation. The [receipt time](../../search/get-started-with-search/build-search/use-receipt-time.md) should be within a few minutes of your log's [message time](/docs/search/get-started-with-search/search-basics/built-in-metadata). See how to [troubleshoot timestamp discrepancies](/docs/send-data/collector-faq#troubleshooting-time-discrepancies).
14+
:::
15+
1216
Real-time alerts are not duplicated, which means that if a specific raw log message has triggered an alert once already, that same log message will not trigger an alert a second time.
1317

1418
For example, if **Message X** caused an alert to be sent at **Time T**, and Sumo Logic detects **Message X** again at **Time T+1**, Sumo Logic does not send a second alert at **Time T+1**. But if Sumo Logic detects **Message Y** at **Time T+1**, a new alert is sent, because the root cause is different.

0 commit comments

Comments
 (0)