[Bug]:unknown metric: [mem3,shard_cache,hit]
- Dominant language
- Erlang
- Stars
- 7k
- Forks
- 1.1k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 9
Description
### Version
3.5.0
### Describe the problem you're encountering
Every day one of my CouchDB servers registers millions of "unknown metric" errors.
Example: "unknown metric: [mem3,shard_cache,hit]"
We do not have any 3rd party monitoring tools.
This is a fresh install of CouchDB 3.5.0 and a single node.
### Expected Behaviour
I expect for their not to be millions of these errors as this does not happen on our other CouchDB servers even after a fresh install.
### Steps to Reproduce
_No response_
### Your Environment
_No response_
### Additional Context
_No response_
Contributor guide
Research direction
Start by investigating CouchDB 3.5.0 metric registration and logging for mem3, shard_cache, and hit on a fresh single-node installation. Reproduce the daily unknown-metric errors and compare the behavior with the reporter's other CouchDB servers. Done means the valid metric no longer produces millions of erroneous unknown-metric errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- erlang
- Domain
- databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100