-
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
[APM] Refactor internal es client #170733
[APM] Refactor internal es client #170733
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
83ff9df
to
aff71b5
Compare
apmIndices
when using internal es clientaff71b5
to
503d161
Compare
) { | ||
const params = { | ||
index: internalESClient.apmIndices.metric, | ||
index: apmIndices.metric, |
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.
why do you need to pass the apmIndices
here from the resources when you could load them from the apm-data-access-plugin ?
import { APMIndices } from '@kbn/apm-data-access-plugin/server';
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.
APMIndices
(that you mention) is a type. apmIndices
is a value (object) produced at runtime.
apmIndices
is produced with:
const apmIndices = await plugins.apmDataAccess.setup.getApmIndices(
coreContext.savedObjects.client
);
Pinging @elastic/apm-ui (Team:APM) |
💛 Build succeeded, but was flaky
Failed CI Steps
Test Failures
Metrics [docs]
History
To update your PR or re-run it, just comment with: |
Related #170031.
The internal Elasticsearch client in APM currently takes
apmIndices
as a required argument. This is due to legacy reasons and no longer needed and should therefore be removed.