Pinging @elastic/ingest-management (Project:fleet)

Jenkins test this

Will this have any effect on where the logs from the processes go? Would be nice if it does as currently it is hard to find the logs for metricbeat for example.

@ruflin yes this changes the location and logs will go to {where_agent_is_installed}/data/logs/{pipeline_name}

e.g: /Users/me/agent/data/logs/default

Is there any reason why we do not use {where_agent_is_installed}/data/{pipeline_name}/logs_ ?

pipeline_name is the name of the output now.

This would ensure that a single place contains everything?

@ph i can change it like this. i did it in this way so we end up with data containing
download install logs
instead of
download install default something-pretty something-else

pipeline = output name? If yes, sounds confusing to me that we talk in the config about outputs but here about pipline?

we call it still PipelineID internally in the code, but what it is it is just and output type out of config e.g default/monitoring/elasticsearch/

Is it type or the name of the output? https://github.com/elastic/beats/blob/master/x-pack/elastic-agent/elastic-agent.yml#L10 The part that is here default or elasticsearch

in the config you posted it would be default. it is the same value you use when specifying output using use_output in streams.
my bad, sorry for confusion i need to slow down window switching

Its is the output name that create an internal pipeline, we ccould do some renaming internally so it's more consistant. but I don't think its a priority now.

@ph i can change it like this. i did it in this way so we end up with data containing
download install logs
instead of
download install default something-pretty something-else

I see your point and I think it's valid, @ruflin wdyt?

On your last comment, no preference as long as the logs are easy accessible.

@michalpristas let's keep it your way :)

💚 Build Succeeded