Skip to content

Commit 770ece2

Browse files
First draft
1 parent 64d64d7 commit 770ece2

File tree

2 files changed

+19
-5
lines changed

2 files changed

+19
-5
lines changed

docs/reference/alert-schema.asciidoc

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -195,9 +195,15 @@ Type: string[]
195195

196196
Shows the alert’s estimated timestamp, had the alert been created when the source event initially occurred. The value in this field is determined by the way the rule was run:
197197

198-
* **Scheduled run**: Alerts created by scheduled runs have the same timestamp as the `kibana.alert.rule.execution.timestamp` field, which shows when the rule was executed.
198+
* **Scheduled run**: Alerts created by scheduled runs have the same timestamp as the `@timestamp` field, which shows when the alert was created.
199199
* **Manual run**: Alerts created by manual runs have a timestamp that falls within the time range specified for the manual run. For example, if you set a rule to manually run on event data from `10/01/2024 05:00 PM` to `10/07/2024 05:00 PM`, the `kibana.alert.intended_timestamp` value will be a date and time within that range.
200200

201201
Type: date
202202

203+
|N/A | `kibana.alert.rule.execution_type` a|
204+
205+
Shows if an alert was created by a manual run or a scheduled run. The value can be `manual` or `scheduled`.
206+
207+
Type: keyword
208+
203209
|==============================================

docs/serverless/alerts/alert-schema.mdx

Lines changed: 12 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -891,7 +891,7 @@ The non-ECS fields listed below are beta and subject to change.
891891

892892
</DocCell>
893893
</DocRow>
894-
<DocRow>
894+
<DocRow>
895895
<DocCell>`kibana.alert.workflow_assignee_ids`</DocCell>
896896
<DocCell>
897897
List of users assigned to an alert.
@@ -904,17 +904,25 @@ The non-ECS fields listed below are beta and subject to change.
904904

905905
</DocCell>
906906
</DocRow>
907-
<DocRow>
907+
<DocRow>
908908
<DocCell> `kibana.alert.intended_timestamp`</DocCell>
909909
<DocCell>
910910
Shows the alert’s estimated timestamp, had the alert been created when the source event initially occurred. The value in this field is determined by the way the rule was run:
911911

912-
* **Scheduled run**: Alerts created by scheduled runs have the same timestamp as the `kibana.alert.rule.execution.timestamp` field, which shows when the rule was executed.
912+
* **Scheduled run**: Alerts created by scheduled runs have the same timestamp as the `@timestamp` field, which shows when the alert was created.
913913
* **Manual run**: Alerts created by manual runs have a timestamp that falls within the time range specified for the manual run. For example, if you set a rule to manually run on event data from `10/01/2024 05:00 PM` to `10/07/2024 05:00 PM`, the `kibana.alert.intended_timestamp` value will be a date and time within that range.
914914

915-
916915
Type: date
917916

918917
</DocCell>
919918
</DocRow>
919+
<DocRow>
920+
<DocCell> `kibana.alert.rule.execution_type`</DocCell>
921+
<DocCell>
922+
Shows if an alert was created by a manual run or a scheduled run. The value can be `manual` or `scheduled`.
923+
924+
Type: keyword
925+
926+
</DocCell>
927+
</DocRow>
920928
</DocTable>

0 commit comments

Comments
 (0)