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.
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 think it might be good to state that regardless of if the agent loses network connectivity then the events are added to the local queue. Then we can state that if the agent loses network connectivity events in the queue will fail to send, are retried and stored according to the agent's retry logic. Depending on how long the network issues persist they may be pushed out automatically, if the event is still being retried.
On another note, events that are rate limited will be retried in perpetuity until the event is successfully delivered, or the event receives a 5XX error code in which case the retry logic kicks in.
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.
For prolonged network outages events can be manually retried https://support.pagerduty.com/docs/pagerduty-agent-integration-guide#manage-the-queue