[EDR Workflows]Automatic troubleshooting usage callout

[szwarckonrad]

Tracks https://github.com/elastic/kibana/pull/221566 Closes https://github.com/elastic/security-team/issues/12824

With this change, whenever a user selects the Elastic LLM connector within the Automatic Troubleshooting feature, they'll see a callout informing them about the potential costs of using it. Once the callout is acknowledged, it will be dismissed and the closed state will be stored in local storage, so it won’t appear again on future visits.

To enable EIS locally:

export VAULT_ADDR=https://secrets.elastic.co:8200/
vault login --method=oidc
node scripts/eis.js

and run ES server with provided env + start kibana with .dev.yaml entry from the output of the command above.

https://github.com/user-attachments/assets/51a2ce77-ed25-4611-9d62-72e9d09bb789

[elasticmachine]

Pinging @elastic/security-defend-workflows (Team:Defend Workflows)

[szwarckonrad]

@angorayc

Thanks for adding the tour! It just fallback to default when it is part of localstorage key can really cause a problem. I'd recommend not to render relevant component when spaceId is not available. https://github.com/elastic/kibana/pull/224030/files#diff-cdae15c1cd82b4489da67cded901d3bad7fa75e7fa9b0895de2d05c8ceefd819R46

Thanks, that makes sense. Changed.

[elasticmachine]

:green_heart: Build Succeeded

• Buildkite Build
• Commit: 880e84f4ce7fc37ff8bb71811df7631e82f5b70a

Metrics [docs]

Async chunks

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

id	before	after	diff
securitySolution	9.3MB	9.3MB	+369.0B

History

• :broken_heart: Build #308906 failed c3dbff75708a3265ad835c40233d377a82e914b0

cc @szwarckonrad

[kibanamachine]

Starting backport for target branches: 9.0

https://github.com/elastic/kibana/actions/runs/15702592295

[kibanamachine]

💔 All backports failed

Status	Branch	Result
❌	9.0	Backport failed because of merge conflicts You might need to backport the following PRs to 9.0: - [Security Assistant] EIS usage callout (#221566)

Manual backport

To create the backport manually run:

node scripts/backport --pr 224030

Questions ?

Please refer to the Backport tool documentation

[szwarckonrad]

💚 All backports created successfully

Status	Branch	Result
✅	9.0

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation