-
Notifications
You must be signed in to change notification settings - Fork 8k
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
[Fleet] Replace Console API with internal API #186899
[Fleet] Replace Console API with internal API #186899
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
65192a4
to
c30c5a0
Compare
/ci |
Pinging @elastic/fleet (Team:Fleet) |
c30c5a0
to
7ca9544
Compare
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
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.
LGTM
Summary
Closes #160194
Parts of the Fleet debugger currently use the Console API to query Fleet indices and Ingest Saved Objects. This PR replaces those uses with internal API endpoints that use Elasticsearch and Saved Objects clients.
Affected parts:
.kibana-ingest
index to retrieve saved objects of a given type.The following example shows the difference between the saved object response before and after this change:
Before
After
Testing
Go to
app/fleet/_debug
and check the various parts described above.Screenshots
Checklist