fix: include next_run_at in the realtime triggers usage reporting (#3383

)

Co-authored-by: Hengfei Yang <[email protected]>

src/service/ingestion/mod.rs

@@ -224,6 +224,12 @@ pub async fn evaluate_trigger(trigger: Option<TriggerAlertData>) {
  &alert.stream_name,
  &alert.name
  );
+
+ let next_run_at = Utc::now().timestamp_micros()
+ + Duration::try_minutes(alert.trigger_condition.silence)
+ .unwrap()
+ .num_microseconds()
+ .unwrap();
  // After the notification is sent successfully, we need to update
  // the silence period of the trigger
  _ = db::scheduler::update_trigger(db::scheduler::Trigger {
@@ -232,14 +238,11 @@ pub async fn evaluate_trigger(trigger: Option<TriggerAlertData>) {
  module_key,
  is_silenced: true,
  is_realtime: true,
- next_run_at: Utc::now().timestamp_micros()
- + Duration::try_minutes(alert.trigger_condition.silence)
- .unwrap()
- .num_microseconds()
- .unwrap(),
+ next_run_at,
  ..Default::default()
  })
  .await;
+ trigger_data_stream.next_run_at = next_run_at;
  }
  trigger_data_stream.end_time = Utc::now().timestamp_micros();
  // Let all the alerts send notifications first