Merged
Conversation
mangas
approved these changes
Feb 14, 2025
isum
force-pushed
the
ion/add-deployment-synced-metric
branch
from
716f738 to
ec3a4c4
Compare
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
2 participants
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.
This PR adds a new
deployment_syncedmetric that indicates whether a deployment has reached the chain head since it was deployed.Possible values for the metric:
0- means that the deployment is not synced;1- means that the deployment is synced;If a deployment is not running, the metric reports no value for that deployment.
Closes #5813
Example of the metric in use
* All values in the example are for the same subgraph deployment.