-
Notifications
You must be signed in to change notification settings - Fork 40
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
Stop collecting Propolis metrics on instance stop #4495
Conversation
When Nexus responds to a sled-agent notification that the instance is stopped and its Propolis server is gone, hard-delete the assignment record and ask `oximeter` to stop collecting from it.
This is the first commit in what I expect to be a series that makes metric producer/collector assignments more robust and flexible. It doesn't resolve #3808, but it prevents the problem from getting worse, by asking To test this, I built and installed the control plane on my Helios machine, and created an instance in the console. That instance has ID
And here is the
Propolis registers using the instance ID as its primary producer ID, so we can see that in the Next, I stopped the instance in the console, and we can see both the assignment record in the table is gone, and the
And in
As a final test, I started the instance again, and things went back to the expected state, with In a follow-up PR, I'll include some work to remove existing assignments and update the table schema slightly to help keep track of producers during future automated updates. |
Thanks @gjcolombo, I've added an item about ensuring metric registrations follow the instance's state in #3742, and have added a note referring to that in b866993. Appreciate the thoughtful review, as always! |
This closes #3812 |
When Nexus responds to a sled-agent notification that the instance is stopped and its Propolis server is gone, hard-delete the assignment record and ask
oximeter
to stop collecting from it.