Repository navigation
feat(grafana): chart the tracker's event-loop delay - #143
Merged
Merged
Conversation
The event-loop delay gauges were exported and used by the capacity guide and the EventLoopLag alert, but the dashboard did not show them. The Signaling row now has three panels: subscribers, signaling traffic, and event-loop delay (p50, p99, max, in seconds).
# Conflicts: # CHANGELOG.md
This file contains hidden or 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
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.
The
openstreamgrid_event_loop_delay_{p50,p99,max}_secondsgauges drive the capacity guide and theOpenStreamGridEventLoopLagalert (#137), but the dashboard did not chart them.The Signaling row now has three panels, each 8 columns wide:
The k8s README dashboard description is updated. The monitoring-metrics test confirms that the new queries use exported metrics.