core@core-01 ~ $ fleetctl list-units
UNIT                                                    MACHINE                         ACTIVE          SUB
es-data@5fa786ce1a764d83a05513f79d554885.service        5fa786ce.../172.17.8.101        active          exited
es-discovery@5fa786ce1a764d83a05513f79d554885.service   5fa786ce.../172.17.8.101        inactive        dead
es@5fa786ce1a764d83a05513f79d554885.service             5fa786ce.../172.17.8.101        active          running
log-entries@5fa786ce1a764d83a05513f79d554885.service    5fa786ce.../172.17.8.101        active          running
core@core-01 ~ $ systemctl show es@5fa786ce1a764d83a05513f79d554885.service | grep Wants
Wants=system-es.slice log-entries@5fa786ce1a764d83a05513f79d554885.service es-data@5fa786ce1a764d83a05513f79d554885.service
core@core-01 ~ $ fleetctl status es-discovery@5fa786ce1a764d83a05513f79d554885.service
● es-discovery@5fa786ce1a764d83a05513f79d554885.service - Elasticsearch Discovery Service
   Loaded: loaded (/run/fleet/units/es-discovery@5fa786ce1a764d83a05513f79d554885.service; linked-runtime; vendor preset: disabled)
   Active: inactive (dead)