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

Agents runs into an 'Unhealthy' state and KPI count is displayed as '0' under 'Unhealthy' header on Agents table. #96949

Closed
ghost opened this issue Apr 13, 2021 · 3 comments
Labels
bug Fixes for quality problems that affect the customer experience Team:Agent Agent Team

Comments

@ghost
Copy link

ghost commented Apr 13, 2021

Kibana version: 7.13.0 Snapshot Kibana cloud environment
Host OS and Browser version: Windows, All

Build Details:
Build number: 40223
Commit: 302ee56
Artifacts: https://artifacts-api.elastic.co/v1/search/7.13.0-SNAPSHOT

Preconditions:

  • Kibana Environment should exist.
  • Endpoint security and Agent should be installed

Steps to Reproduce:

  1. Navigate to 'Integration' tab under 'Fleet' section.
  2. Add Endpoint Security Integration to existing 'Default Policy'.
  3. Navigate to 'Policies' tab and Click on Edit button of Endpoint Security Integration policy.
  4. Now update your Integration Policy to Detect Mode and Save the changes.
  5. Now enroll an Agent from 'Agents' tab. Notice that the agent has been installed successfully and is in Healthy state
  6. After Sometime, Observe that Agents runs into an 'Unhealthy' state and KPI count is displayed as '0' under 'Unhealthy' header on Agents table.

Expected Result:
Agents should remain in 'Healthy' state and KPI count should display correct count for all the Status header on Agents table.

What's working:
This issue is not occurring if the agent is in Healthy state

What's not working:
Status ribbon remains Green if the Agent went into an Unhealthy State
It should be displayed as 'Yellow' instead as per color coding

Unhealthy Agent

@ghost ghost added the bug Fixes for quality problems that affect the customer experience label Apr 13, 2021
@botelastic botelastic bot added the needs-team Issues missing a team label label Apr 13, 2021
@amolnater-qasource
Copy link

Reviewed & Assigned to @EricDavisX

@EricDavisX EricDavisX removed their assignment Apr 13, 2021
@EricDavisX EricDavisX added the Team:Agent Agent Team label Apr 13, 2021
@botelastic botelastic bot removed the needs-team Issues missing a team label label Apr 13, 2021
@EricDavisX
Copy link
Contributor

we can confirm this after the changes for Fleet Server are found working - it may be a dupe of one fixed already as part of development.

@dikshachauhan-qasource
Copy link

Hi @EricDavisX ,

We are closing this for now as per our comment posted on #93910_ comment.

We will re-open it if found it reproducible on later builds.

Thanks
QAS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Team:Agent Agent Team
Projects
None yet
Development

No branches or pull requests

3 participants