-
Notifications
You must be signed in to change notification settings - Fork 8
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
An issue occurred where system metrics publishing was occurring too close to the minute boundary. Coupled with some changes to the Atlas Aggregators, which added a little bit of delay, this was causing updates to drift between minutes. This resulted in some minutes without updates, and some minutes with 2X value updates. This perturbation of metrics triggered a number of different alarms in the environment. Given that spectatord publishes every 5 seconds with a small variability, and that most system metrics gather cycles are around 100ms, we want the system agent to publish metrics between 10 and 50 seconds after the minute, to ensure the stability of system metrics values. This change adds a function which calculates the initial polling delay that the service will experience at startup. Once that wait period is complete, then all subsequent updates should safely occur within the middle of a minute. The metric publishing log messages produced at info level from an older build of the system agent were helpful in determining the cause of this issue, so the log message is restored to info level, with some delay timing data. Resolves #135.
- Loading branch information
1 parent
caad3c7
commit a5b67ea
Showing
1 changed file
with
60 additions
and
8 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters