Kibana version: 7.17.1
Describe the bug:
Seen in user logs:
invalid event logged: [event.duration]: "event.duration" must be a safe number; {
"@timestamp":"2022-03-15T17:11:57.912Z",
"event":{"provider":"alerting","action":"active-instance","kind":"alert","category":["infrastructure"],
"start":"2021-11-22T14:00:33.597Z",
"duration":9774684315000000},
That's one long rule execution! Back-of-the-envelope calculation on how long 9774684315000000 nanoseconds are: 113 days, and the GOOG concurs:
Steps to reproduce:
- not clear
Expected behavior:
An error should not occur.
Seems like we need to catch numbers bigger than Number.MAX_SAFE_INTEGER and either send that max value, or figure out if we can send a floating point or some other representation.
Kibana version: 7.17.1
Describe the bug:
Seen in user logs:
That's one long rule execution! Back-of-the-envelope calculation on how long 9774684315000000 nanoseconds are: 113 days, and the GOOG concurs:
Steps to reproduce:
Expected behavior:
An error should not occur.
Seems like we need to catch numbers bigger than
Number.MAX_SAFE_INTEGERand either send that max value, or figure out if we can send a floating point or some other representation.