Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rundeck Log still created in localhost altought migrate to S3 storage #24

Open
Fahri28 opened this issue Mar 15, 2018 · 3 comments
Open

Comments

@Fahri28
Copy link

Fahri28 commented Mar 15, 2018

Hi,

i have installed rundeck in ec2 instance and want to move every project-job log into S3 storage. i use Rundeck S3 Log plugin to implement this, but i just wonder why the job log still created twice both in localhost (var/lib/rundeck/logs) and in S3 storage, instead it should only be in S3 storage bucket

@gschueler
Copy link
Member

the logs are first written to local storage, then uploaded to s3. after that they can be removed from local storage if you want, but rundeck does not automatically remove them (currently)

if that is desired can you file an issue on the rundeck project?

@triwats
Copy link
Contributor

triwats commented Jul 24, 2019

Going back to this it certainly seems advantageous to maintain the log on the local machine for debugging purposes.

@doniz
Copy link

doniz commented Oct 3, 2024

Can we have an option to delete log files from the local storage? By default that option can be false to prevent deleting from the local storage, but users may use that option as they like.

I do see plugin anyway deletes the log files from the bucket: https://github.com/rundeck-plugins/rundeck-s3-log-plugin/blob/master/src/main/java/org/rundeck/plugins/S3LogFileStoragePlugin.java#L408, having an option to also delete from the local storage would help to have a proper retention that can be managed by Rundeck cleanup feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants