-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Response Ops][Alerting] ES query rule error Executing Rule default:.es-query has resulted in Error: Cannot set properties of undefined (setting 'order') - TypeError: Cannot set properties of undefined (setting 'order')
#182755
Comments
Pinging @elastic/response-ops (Team:ResponseOps) |
Nice! I could have sworn I saw a message like in the logs recently, and had remembered while opening a different issue, so tried to find it again. But couldn't. I think I looked in qa and prod, but not staging 🤦🏻♂️ OHHHH .... I don't see it in serverless, only in ESS! I checked prod, and it's happening with other fields as well. For searching, use |
Some of the fields/locations I've found over the last 90 days:
I wouldn't be surprised if some of these were caused by calls to ES that went bad somehow - which are likely not as critical as when it's not an ES call that goes bad. So we may be able to defer fixing some of these, if needed. type:
gte:
timeFieldName:
index:
actionId:
getFlapping:
scheduledAt:
meta:
fields:
title:
|
Error counts from the production logs Bug with ES query multi-terms Related to search source
Accessing field from
Other |
Seen in the logs of the staging overview cluster. Looks like it's happening in the
build_agg
functionkibana/x-pack/plugins/triggers_actions_ui/common/data/lib/build_agg.ts
Line 117 in 0c0cf0a
The text was updated successfully, but these errors were encountered: