[ITF] Logs reachability is not there in case of Service Only Usecase

[ishleenk17]

As part of the Service Only Use case for ITF, there is currently a known issue for collecting logs. The logs are accessed by the elastic agent through a path configured in docker files like this.

${SERVICE_LOGS_DIR}/mysql:/var/log/mysql SERVICE_LOGS_DIR is Alias for Logs.Folder.Agent as mentioned here as well.

This placeholder is used by elastic agent. In the case of All on Cloud usecase, it works fine since the agent and service are all on the same cluster.

In the case of service alone usecase, the agent is on the local system and the service is in a cluster. Hence logs aren't reachable. We should figure out a way of giving access to these log files to the local agent

[kuisathaverat]

oblt-cli 5.1.0 has a new command to synchronize the logs folders from the pod to a local folder every 10 seconds, that local folder is the point that the local Elastic Agent has to listen for the logs. The following command will work in deployment done with oblt-cli 5.1.0.

CLUSTER_NAME=ess-integrations-v2-oferv
LOCAL_FOLDER=/tmp/logs
oblt-cli packages logs remote --cluster-name "${CLUSTER_NAME}" --output-folder "${LOCAL_FOLDER}"

[botelastic[bot]]

Hi! We just realized that we haven't looked into this issue in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!