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

The shipper should report itself as FAILED when multiple outputs are configured. #171

Open
Open
The shipper should report itself as FAILED when multiple outputs are configured.#171
Labels
8.7-candidateTeam:Elastic-AgentLabel for the Agent team
@cmacknz

Description

@cmacknz
cmacknz
opened on Nov 10, 2022

The shipper does not support multiple outputs. When multiple outputs are detected in the shipper configuration provided by the agent, the shipper should report itself as in the FAILED state on its next checkin with the agent.

Currently the behaviour configuration multiple outputs is to pick one based on an arbitrary ordering:

elastic-agent-shipper/controller/runner.go

Lines 209 to 220 in 598c8e6

func outputFromConfig(config output.Config, queue *queue.Queue) (Output, error) {
if config.Elasticsearch != nil {
return elasticsearch.NewElasticSearch(config.Elasticsearch, queue), nil
}
if config.Kafka != nil && config.Kafka.Enabled {
return kafka.NewKafka(config.Kafka, queue), nil
}
if config.Console != nil && config.Console.Enabled {
return output.NewConsole(queue), nil
}
return nil, errors.New("no active output configuration")
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    8.7-candidateTeam:Elastic-AgentLabel for the Agent team

    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