ETCD Metricbeat module needs polishing and grooming about integrations HOT 6 CLOSED

Agree, we should generate an event per follower.

Related to this, we also need to add support for the current monitoring endpoint and for the v3 store (#9093).

from integrations.

+1 on having one event per follower. The current event should only contain the ids of the followers. To implement such a change non breaking we could introduce a config option to disable follower data in leader metricset. For the new fields / cleaned up fields, we could introduce them as aliases to then be switched over in the next major.

from integrations.

Pinging @elastic/integrations (Team:Integrations)

from integrations.

Mostly fixed here elastic/beats#11280

from integrations.

The metricset leader should be renamed to follower?

from integrations.

As we talked through the chat, the ideal improvement at this moment is:

• To generate an event for each Follower, either in this same metricset using etcd.leader.follower or in a different one using etcd.follower and...
• To update / upgrade the metrics we collect for the leader, in this metricset.

from integrations.