Understanding Agent Status Value Matching and Check-in Criteria in Elastic Stack

Elastic Stack Elastic Agent
1

Hello,

I have several questions regarding the agent status value matching as well as check-in criteria in Elastic Stack.

  1. How is the matching process between unit.state field values for agent status information in Index Management -> Data Stream -> logs-elastic_agent-default and the agent status values in Management -> Fleet carried out?

Here are the unit.state field values:

  • STARTING
  • CONFIGURING
  • HEALTHY
  • DEGRADED
  • FAILED
  • STOPPING
  • UPGRADING
  • ROLLBACK

And the Agent Status values:

  • Healthy
  • Unhealthy
  • Updating
  • Offline
  • Inactive
  • Unenrolled

  1. I understand that Agent status is based on check-ins. What exactly is checked during these check-ins that determine the Agent status? Is it the individual Agent connection status, the status of the bits composing the Agent, the connection status between Fleet and Agent, or some other factors?

  2. Up to which Agent status do Beats operate and transmit data? Specifically, does the Agent status check ensure the status check of Beats?

Any insight or guidance on these questions would be greatly appreciated. Thanks in advance for your help and expertise!

2

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.