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

[D4C] Add handling to better surface cloud-defend unit state failure errors #158409

Closed
mitodrummer opened this issue May 24, 2023 · 2 comments
Closed
Assignees
Labels
enhancement New value added to drive a business result v8.9.0

Comments

@mitodrummer
Copy link
Contributor

Image

Elastic Defend (endpoint) is peaking into to this data and adding error panels inside the "input" dropdown on the right of the "agent status page". Our integration won't surface our error payloads, so this ticket is to track adding something similar to what endpoint does for cloud_defend.

It might be helpful to include a link to a "troubleshooting" section of our integration readme, and then specific "component" errors could have their own resolutions we point the user towards. e.g uncommenting capabilities

@mitodrummer mitodrummer added Team: Cloud Native Integrations v8.9.0 enhancement New value added to drive a business result labels May 24, 2023
@mitodrummer
Copy link
Contributor Author

Looks like the fleet team has this on their radar: #154634

@mitodrummer mitodrummer self-assigned this May 31, 2023
@norrietaylor
Copy link
Member

This should be ready for testing in 8.9

@norrietaylor norrietaylor self-assigned this Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result v8.9.0
Projects
None yet
Development

No branches or pull requests

2 participants