Skip to content
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

Propagate execution context from Enterprise Search #126801

Closed
lizozom opened this issue Mar 3, 2022 · 0 comments
Closed

Propagate execution context from Enterprise Search #126801

lizozom opened this issue Mar 3, 2022 · 0 comments

Comments

@lizozom
Copy link
Contributor

lizozom commented Mar 3, 2022

Solutions can now utilize useExecutionContext to make sure all outgoing requests (search, saved objects) are properly traced back to a page and an entity (in ES, APM and Fullstory).

// Application ID and current URL are traced automatically.
useExecutionContext({
   page: 'editor'
   id: savedVis.id ?? 'new',
});
  • Call useExecutionContext on the top most react component that renders each page (list, editor, etc).
    • The page names should be short and consistent (no unique identifiers).
    • The id field can be used to track the main entity handled by the page (for example the displayed dashboard). Leave it empty if not applicable (For example on a listing page).
  • If the application code is being rendered within an embeddable or nested elsewhere, make sure to attach child context properly
  • See the testing instructions to make sure data is sent properly to APM.
@lizozom lizozom changed the title Enterprise Search Propagate execution context from Enterprise Search Mar 3, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label Mar 3, 2022
@lizozom lizozom added Team:EnterpriseSearch and removed needs-team Issues missing a team label labels Mar 3, 2022
@lizozom lizozom closed this as completed Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant