Skip to content

Always provide the Elasticsearch output unit configuration to Heartbeat when using the shipper #1476

@cmacknz

Description

@cmacknz

Heartbeat has a new feature where it will make queries directly to the Elasticsearch configured as the output. To do this it creates an internal Elasticsearch client from the Elasticsearch output settings provided to the beat. Additionally, Heartbeat only supports the Elasticsearch output and all other outputs types should be removed from the v1 and v2 agent spec files.

When Heartbeat is configured to use the shipper, the agent must provide both the shipper output configuration and the Elasticsearch output configuration.

CC @andrewvc @emilioalvap

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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