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

Add deployment_status metric #5720

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

isum
Copy link
Member

@isum isum commented Nov 29, 2024

This PR adds a new deployment_status metric with the following behavior:

  • Once graph-node has figured out that it should index a deployment, deployment_status is set to 1 (starting);
  • When the block stream is created and blocks are ready to be processed, deployment_status is set to 2 (running);
  • When a deployment is unassigned, deployment_status is set to 3 (stopped);
  • If a temporary or permanent failure occurs, deployment_status is set to 4 (failed);
    • If indexing manages to recover from a temporary failure, the deployment_status is set back to 2 (running);

No other values for deployment_status should be expected.

Closes #5405

Breaking changes

The deployment_failed metric is removed and the failures are reported by the new deployment_status metric.

Node operators that relied on deployment_failed should switch to using deployment_status.

Testing

The new metric was tested on a local graph-node and Prometheus setup. I have tested various scenarios such as errors, pauses, restarts and the metric behaves as expected and reports correct values.

@isum isum self-assigned this Nov 29, 2024
@fordN fordN requested a review from mangas December 3, 2024 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Update deployment_failed to better reflect syncing status
1 participant