Skypilot currently only allows you to decide if you forward all logs to GCP or not.
Instead, we would prefer to be able to decide that on a case by case basis.
Specifically, when using skypilot in a kubernetes environment, we may not want the log forwarding capabilities to apply, but if the target environment are VMs managed through SSH, we will want the fluent-bit agent to be injected into those jobs.
Ideally this is something that can be enabled/disabled on a request by request basis (a task configuration that can be overridden by setting something like logs: destionation-name and where destination-name is configured on the server side).
https://docs.skypilot.co/en/latest/cloud-setup/external-logging.html
Skypilot currently only allows you to decide if you forward all logs to GCP or not.
Instead, we would prefer to be able to decide that on a case by case basis.
Specifically, when using skypilot in a kubernetes environment, we may not want the log forwarding capabilities to apply, but if the target environment are VMs managed through SSH, we will want the fluent-bit agent to be injected into those jobs.
Ideally this is something that can be enabled/disabled on a request by request basis (a task configuration that can be overridden by setting something like
logs: destionation-nameand wheredestination-nameis configured on the server side).https://docs.skypilot.co/en/latest/cloud-setup/external-logging.html