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

Shutdown function should never leave data behind #494

Open
iamemilio opened this issue May 16, 2022 · 0 comments
Open

Shutdown function should never leave data behind #494

iamemilio opened this issue May 16, 2022 · 0 comments
Labels
enhancement p3 Priority 3 work items

Comments

@iamemilio
Copy link
Contributor

iamemilio commented May 16, 2022

When explicitly calling the shutdown function, the expectation is that the execution of the code is being paused until all the data in queue is sent to NR1. This is not always the case, and sometimes longer harvest cycle data types like metrics can get left behind if the app shuts down before their harvest cycle. The shutdown should force a flush of all data that is queued for sending to NR1 by force.

@iamemilio iamemilio changed the title Shutdown function shoud Shutdown function should never leave data behind May 16, 2022
@iamemilio iamemilio added this to Awaiting User Input in Go Engineering Board via automation May 16, 2022
@iamemilio iamemilio moved this from Awaiting User Input to Triage in Go Engineering Board May 16, 2022
@Ak-x Ak-x added the p3 Priority 3 work items label Jun 27, 2022
@Ak-x Ak-x moved this from Triage to Ice Box in Go Engineering Board Jun 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement p3 Priority 3 work items
Projects
Development

No branches or pull requests

2 participants