-
Notifications
You must be signed in to change notification settings - Fork 5
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
Start instance monitoring before instance is launched #252
Start instance monitoring before instance is launched #252
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #252 +/- ##
===========================================
- Coverage 86.56% 84.49% -2.07%
===========================================
Files 85 155 +70
Lines 7448 13540 +6092
Branches 0 1675 +1675
===========================================
+ Hits 6447 11441 +4994
- Misses 1001 2099 +1098 ☔ View full report in Codecov by Sentry. |
ec4530d
to
d6f2278
Compare
1cb503e
to
2afe68a
Compare
…on start Signed-off-by: Mykhailo Lohvynenko <[email protected]>
c62f54c
to
e6b8059
Compare
Signed-off-by: Mykhailo Lohvynenko <[email protected]>
Signed-off-by: Mykhailo Lohvynenko <[email protected]>
e6b8059
to
8056108
Compare
|
ResourceMonitor::ProcessMonitoring() runs on a separate thread and operates with a delay defined by the "poll period" configuration variable.
As a result, ProcessMonitoring() may execute at a moment when instance monitoring has started, but the instance itself has not yet been launched, leading to the following error:
main aos_servicemanager[1659]: (monitoring) Failed to get instance monitoring data: not found (resourceusageprovider.cpp:324)