-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[Entity Analytics] [Entity Store] Show errors on entity store enablement #198263
base: main
Are you sure you want to change the base?
Conversation
Pinging @elastic/security-entity-analytics (Team:Entity Analytics) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @tiansivive ! Overall looks good. Focussed review on SO parts and left some qs.
}, | ||
{ | ||
type: 'data_backfill', | ||
backfillFn: (document) => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you are adding a new default field to the schema that is optional we don't need to run this backfill operation, leaving it undefined
should be fine. Or does null
mean something specific in this case?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, it was meant to clearly state there was no value as its optional. I wasn't sure whether just leaving it undefined would work. I'll update
error: { | ||
type: 'object', | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we searching over this value? If not then we don't need to include it in mappings.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so I dont need to add a migration for it? I can just "silently" add it to the saved object?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ended up removing the migration, seems like that is the correct way to do this since we never want to search on errors. Please do let me know if there are other concerns wrt the SO @jloleysens
...ity_solution/public/entity_analytics/components/entity_store/components/dashboard_panels.tsx
Outdated
Show resolved
Hide resolved
...ity_solution/public/entity_analytics/components/entity_store/components/dashboard_panels.tsx
Outdated
Show resolved
Hide resolved
...ity_solution/public/entity_analytics/components/entity_store/components/dashboard_panels.tsx
Outdated
Show resolved
Hide resolved
...ugins/security_solution/server/lib/entity_analytics/entity_store/entity_store_data_client.ts
Outdated
Show resolved
Hide resolved
...security_solution/server/lib/entity_analytics/entity_store/saved_object/engine_descriptor.ts
Outdated
Show resolved
Hide resolved
⏳ Build in-progress, with failures
Failed CI StepsHistory
|
b5a88c1
to
29b6fea
Compare
… src/core/server/integration_tests/ci_checks'
Summary
This PR adds user feedback for errors that happen when enabling the entity store.
Any errors during the async setup of store resources will show up as toasts, whist initial INIT request failures will appear as an error callout.