The dgraph_active_mutations_total monitoring metric disappears
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 21.8k
- Forks
- 1.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 9
Description
Describe the bug
In certain environments, the dgraph_active_mutations_total monitoring metric disappears. During local debugging, I observed that this key only exists after a write request is triggered. This behavior might be unexpected as the metric disappears suddenly in production without any restarts.
To Reproduce
Steps to reproduce the behavior:
Deploy Dgraph version v24.0.2 in the local environment.
Monitor the dgraph_active_mutations_total metric.
By default, this key does not exist; it appears after a write request.
Expected behavior
The dgraph_active_mutations_total metric always exists.
Screenshots
Environment
- Version [e.g. v24.0.2]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Deploy Dgraph v24.0.2 locally and monitor dgraph_active_mutations_total before and after sending a write request. Trace where this monitoring metric is created or exposed, then verify that it remains present from startup through write activity without requiring a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100