Skip to content
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

Update deployment_failed to better reflect syncing status #5405

Open
azf20 opened this issue May 13, 2024 · 0 comments · May be fixed by #5720
Open

Update deployment_failed to better reflect syncing status #5405

azf20 opened this issue May 13, 2024 · 0 comments · May be fixed by #5720
Assignees
Labels
monitoring ops Relevant to Graph Node Ops subgraph errors

Comments

@azf20
Copy link
Contributor

azf20 commented May 13, 2024

The deployment_failed metric is only created/updated once the block stream has been set up, but not when starting up a deployment fails, e.g. because it references a non-existent chain

This makes it harder to detect failed subgraphs. We should update (and maybe rename) this metric so that it better captures syncing status

starting - a node figured that it should run the deployment and is working on starting it; that should be set as early as possible
running - everything's fine, we are processing blocks
failed - something went wrong

@azf20 azf20 added monitoring ops Relevant to Graph Node Ops labels May 13, 2024
@fordN fordN unassigned lutter Jun 6, 2024
@isum isum linked a pull request Nov 29, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
monitoring ops Relevant to Graph Node Ops subgraph errors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants