[Maps] Add execution context

[thomasneirynck]

Summary

Closes #121116

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[thomasneirynck]

@elasticmachine merge upstream

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[nreese]

thanks for looking into this. This is great as it will add better tracing for how kibana and maps effects cluster health. Do we need to add execution_context for tile requests?

Can you also update the docs in https://github.com/elastic/kibana/blob/main/docs/user/troubleshooting/trace-query.asciidoc and add that maps tracked in the "warning" section

[thomasneirynck]

Do we need to add execution_context for tile requests?

@nreese I don't know if this is possible, since the tile-request use the transport-client directly.

@mshustov is it possible to add execution-context params here? e.g.

kibana/x-pack/plugins/maps/server/mvt/get_tile.ts

Line 48 in 2cb2bd4

const tile = await context.core.elasticsearch.client.asCurrentUser.transport.request(

[nreese]

LGTM
code review

[mshustov]

@mshustov is it possible to add execution-context params here? e.g.

It will be attached automatically. If you want to provide plugin-specific metadata, you can wrap a call with:

await service.withContext({
  type: '...',
  name: '...',
  id: '...',
  description: '....',
},
async () => {
  await context.core.elasticsearch.client.asCurrentUser.transport.request( ...
})

[nreese]

LGTM

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 2072bd2
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
maps	757	758	+1

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
maps	2.5MB	2.5MB	+818.0B

History

• 💔 Build #19908 failed d7bcc0a
• 💚 Build #19398 succeeded 99be656
• 💚 Build #19253 succeeded 52bc22e
• 💔 Build #19218 failed df1dad8

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream