-
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
[RAM] ResponseOps saved object updates #152857
Conversation
Pinging @elastic/response-ops (Team:ResponseOps) |
Pinging @elastic/uptime (Team:uptime) |
ec7fe69
to
fdf0ab5
Compare
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.
left comments on some additional fields we may be able to comment out
other than that, LGTM; going to pound on it for a while now ...
...core/server/integration_tests/saved_objects/migrations/group2/check_registered_types.test.ts
Show resolved
Hide resolved
// traceparent: { | ||
// type: 'text', | ||
// }, | ||
params: { |
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.
params
and state
are JSON bags, so likely don't need to be indexed.
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 think it was failing test because we are using _source to get this attributes and since they are not mapped anymore, source was not working anymore.
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.
hmmm .... that doesn't seem right - the _source
should always contain the JSON blob we index. It should be there regardless if it's indexed/mapped any more.
But ... not hard for me to believe that someone would use a runtime field on here, which would be a little easier to do with a field, than if it was in _source - certainly faster if for some reason this is done at runtime. Maybe telemetry?
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.
let me re-check/search and give you the right answer here
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.
ok You are right! we were able to not index these two, I tried multiple time and tests are not failing!
…bana into alerting-saved-object-updates
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.
LGTM
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.
Woohoo! Got rid of the JSON bags!
LGTM!
…bana into alerting-saved-object-updates
💚 Build Succeeded
Metrics [docs]Saved Objects .kibana field count
Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
monitoring: { | ||
properties: { | ||
run: { | ||
properties: { |
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.
@XavierM Sorry I'm a bit late with this comment since the PR has been already merged, but:
Until it's too late and we can't introduce non-additive changes to the mappings anymore, can we consolidate and refactor the monitoring
and lastRun
objects? These two objects contain similar data, and it's confusing for a lot of devs, including me, @jpdjere, @maximpn etc.
You can see how our code looks like that has to deal with these two objects, it's more complex than should be:
Summary
This PR is just the first phase for response ops to go through their saved object attributes. The idea is to comment out all the attributes that we all agree that we do not need to filter/search/sort/aggregate on.
After, in a second phase/PR, we will create a new file who will represent all of attributes in our saved object as a source of truth. Then, we will generate our SO mappings from this source of truth to register our saved object.
Phase 3, we will try to generate also our type from our source of truth.