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

Copying sysdig sump files to remote storage #1613

Open
jaychan-q opened this issue Apr 7, 2020 · 2 comments
Open

Copying sysdig sump files to remote storage #1613

jaychan-q opened this issue Apr 7, 2020 · 2 comments

Comments

@jaychan-q
Copy link

Hello All, Is there a way to generate sysdig dump files based on the timestamp ? I am trying to copy the dump files to gcp storage and not want to overwrite the files. Currently i am doing this (which generates dumps every 15 min and keeps 5 files).

sysdig -G 900 -W 5 -qw /opt/sysdig_dumps/sysdig-$(date +'%Y%m%d-%H%M%S').scap
This generates files like below and first file gets overwritten after 5th dump file is generated.
sysdig-20200406-212213.scap0
sysdig-20200406-212213.scap1
sysdig-20200406-212213.scap2
sysdig-20200406-212213.scap3
sysdig-20200406-212213.scap4

How do we keep these dump files without getting overwritten and sent to remote storage?

Thanks

@kristopolous
Copy link
Contributor

Logrotate can handle all of this, including the timestamp.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 22, 2023
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2023
@therealbobo therealbobo reopened this Mar 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants