Skip to content
This repository was archived by the owner on Sep 17, 2024. It is now read-only.
This repository was archived by the owner on Sep 17, 2024. It is now read-only.

[Fleet] Parametrize and functionalize the check for the number of beats processes (currently only validates that 1 is running but 2 are the default) #218

Closed
#1153
Closed
[Fleet] Parametrize and functionalize the check for the number of beats processes (currently only validates that 1 is running but 2 are the default)#218
#1153
Assignees
mdelapenya
Labels
Team:Elastic-AgentLabel for the Agent teamarea:testAnything related to the Test automationenhancementNew feature or requestgood first issueGood for newcomerspriority:lownice to have, low impactsize:Sless than 1 daytriagedTriaged issues will end up in Backlog column in Robots GH Project
@mdelapenya

Description

@mdelapenya
mdelapenya
opened on Aug 11, 2020

By default, there are two instances for the metricbeat process, one for monitoring the processes

cc/ @EricDavisX

Metadata

Metadata

Assignees

Labels

Team:Elastic-AgentLabel for the Agent teamarea:testAnything related to the Test automationenhancementNew feature or requestgood first issueGood for newcomerspriority:lownice to have, low impactsize:Sless than 1 daytriagedTriaged issues will end up in Backlog column in Robots GH Project

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions