Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]:unknown metric: [mem3,shard_cache,hit]

Open
#5,886 23 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
erlang

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.

Description

bug needs-triage
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

Dominant language
Erlang
Stars
7k
Forks
1.1k
Avg merge
1d 21h
Merged PRs (30d)
14

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/couchdb

All issues in apache/couchdb

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.