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 Security solutions #126799

Closed
Tracked by #102629
lizozom opened this issue Mar 3, 2022 · 4 comments · Fixed by #131805
Closed
Tracked by #102629

Propagate execution context from Security solutions #126799

lizozom opened this issue Mar 3, 2022 · 4 comments · Fixed by #131805
Assignees
Labels
8.2 candidate considered, but not committed, for 8.2 release 8.3 candidate Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team:Security Solution Platform Security Solution Platform Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture

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 added the Team:Security Solution Platform Security Solution Platform Team label Mar 3, 2022
@lizozom lizozom changed the title Security solutions Propagate execution context from Security solutions Mar 3, 2022
@yctercero yctercero added the 8.2 candidate considered, but not committed, for 8.2 release label Mar 3, 2022
@peluja1012 peluja1012 added 8.3 candidate technical debt Improvement of the software architecture and operational architecture labels Mar 24, 2022
@xcrzx xcrzx assigned xcrzx and unassigned yctercero May 6, 2022
@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. Team:Detection Rule Management Security Detection Rule Management Team labels May 11, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/security-detections-response (Team:Detections and Resp)

@elasticmachine
Copy link
Contributor

Pinging @elastic/security-solution (Team: SecuritySolution)

@yctercero
Copy link
Contributor

Hey @lizozom ! @xcrzx has taken over this as he's doing some other related performance work.

@lizozom
Copy link
Contributor Author

lizozom commented May 16, 2022

@xcrzx hit me up if you need any help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.2 candidate considered, but not committed, for 8.2 release 8.3 candidate Team:Detection Rule Management Security Detection Rule Management Team Team:Detections and Resp Security Detection Response Team Team:Security Solution Platform Security Solution Platform Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. technical debt Improvement of the software architecture and operational architecture
Projects
None yet
6 participants