-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Improve alerts #18080
Merged
Merged
Improve alerts #18080
Conversation
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
github-actions
bot
added
area/health
area/daemon
area/database
area/tests
area/aclk
labels
Jul 8, 2024
stelfrag
force-pushed
the
improve_alerts
branch
3 times, most recently
from
July 12, 2024 14:22
f7a3144
to
b5cc0c4
Compare
Add health version 2 Calculate alert version and store in database Add alert capability Add some checks
Code cleanup
Always process pending queue
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
Cleanup table aliases Add DEFINEs for alert delays Add missing newline
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
reviewed
Jul 16, 2024
thiagoftsm
previously approved these changes
Jul 16, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After changes, the PR worked as expected on my environment. I had alerts from both parent and child.
thiagoftsm
approved these changes
Jul 17, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I ran the branch after last commits, and I am having my alerts on cloud as expected, LGTM!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Improve the agent to cloud alert communication. The goal is to reduce messages transmitted during agent start or reconnect.
Agents calculate and send a version with each alert. When agent -- cloud link is established the start alerts streaming command carries the version of the alerts the cloud is aware.
A version match on the agent side ensures that we don't transmit transitions that the cloud already knows
New tables
Holds alerts transitions to be processed. Also used to de-duplicate alert transitions
Holds pending alerts transitions to be send to the cloud
Holds last alert version after being submitted to the cloud
netdatacli aclk-state
adjusted to reflect changesRemoved fields
Pending Min Seq ID
,Pending Max Seq ID
andLast Submitted Seq ID
Added
Checkpoints
: number of checkpoint requests received from the cloudAlert count
: number of alert transitions sent to the cloudAlert snapshot count
: number of snapshots sent to the cloud due to checkpoint failuresTest Plan