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.

Sign up for GitHub

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

Jump to bottom

elastic-agent status cmd does not show beats components #2976

Closed
olegsu opened this issue Jul 2, 2023 · 2 comments
Closed

elastic-agent status cmd does not show beats components #2976

olegsu opened this issue Jul 2, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@olegsu
Copy link

olegsu commented Jul 2, 2023

Running BC image of Elastic-Agent (8.9.0).
Deployed on local kind cluster, connected to ESS environment.

I have deployed Elastic-Agent and installed KSPM integration.
🟢 I see in Kibana all the documents.
🟢 I see the Fleet agent view the integration
image

🔴 elastic-agent status command does not show cloudbeat process. When running with --output json the component is part of the response

image
image
@olegsu olegsu added the bug Something isn't working label Jul 2, 2023
@jlind23
Copy link
Contributor

jlind23 commented Jul 3, 2023

This might by an impact of a recent change to the status command introduced by @leehinman : #2890
Could you please try the "full" option?

@olegsu
Copy link
Author

olegsu commented Jul 3, 2023

Thank you @jlind23 for a quick response.
Indeed, --output full shows all the details.
Closing this, I guess I missed that change somehow.

@olegsu olegsu closed this as completed Jul 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@olegsu @jlind23