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

Support scheduling distributed captures #88

Open
vakalapa opened this issue Mar 20, 2024 · 2 comments
Open

Support scheduling distributed captures #88

vakalapa opened this issue Mar 20, 2024 · 2 comments
Assignees
Labels
area/captures good first issue Good for newcomers help wanted Extra attention is needed type/enhancement New feature or request

Comments

@vakalapa
Copy link
Contributor

vakalapa commented Mar 20, 2024

Is your feature request related to a problem? Please describe.
Network issues is seen during peak hours and doing packet capture at specific time is not easy as at times it is our midnight.
Having ability to schedule TCP packet capture would be a huge help .

@vakalapa vakalapa added type/enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed area/captures labels Mar 20, 2024
Copy link

This issue is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in 7 days

@github-actions github-actions bot added the meta/waiting-for-author Blocked and waiting on the author label Mar 28, 2024
@vakalapa vakalapa removed the meta/waiting-for-author Blocked and waiting on the author label Mar 28, 2024
@alexcastilio alexcastilio self-assigned this Aug 20, 2024
@alexcastilio
Copy link
Contributor

Hi @vakalapa. Would you have more details to share about your feature request?

Do you want capture to be executed only once at a specific time and day, or you want it to be executed following a periodic schedule (e.g. every day at a specific time)?

Kubernetes' CronJob could be used in both cases but for the 1st option, it needs to be schedule with a big interval, so it could be deleted before next run. For example, scheduling the capture to once per year at specific day and time, then, there's 1 year for the CronJob to be deleted without having it running a second time.

If this is the approach to be followed, a new flag --schedule could be added to the CLI to handle the schedule in the Cron format the job should be run with.

Would that work for the use case you have in mind?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/captures good first issue Good for newcomers help wanted Extra attention is needed type/enhancement New feature or request
Projects
Status: In Progress
Development

No branches or pull requests

4 participants