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_status
metric with the following behavior:deployment_status
is set to1
(starting);deployment_status
is set to2
(running);deployment_status
is set to3
(stopped);deployment_status
is set to4
(failed);deployment_status
is set back to2
(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 newdeployment_status
metric.Node operators that relied on
deployment_failed
should switch to usingdeployment_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.