Go and Process collectors are not adding component labels to the emitted metrics.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- observability-sre
Research direction
Start in pkg/metric/metric.go around line 96 and trace how the registerer wraps the Go and process collectors. Reproduce the emitted metrics and verify that both collector sets include the component label; done means the label is present in their output.
Written by the indexing model from the issue text.
Description
Even though the registerer that is used to register go and process collectors are wrapped with component label, it's not actually in the emitted metrics: https://github.com/hyperledger/firefly-common/blob/main/pkg/metric/metric.go#L96
- Dominant language
- Go
- Stars
- 5
- Forks
- 15
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from hyperledger-firefly/common
-
Difficulty 4/5 3-5 days Newbie friendliness 58/100
hyperledger-firefly/common#245 · 1 reaction ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
hyperledger-firefly/common#236 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
hyperledger-firefly/common#188 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
hyperledger-firefly/common#156 · 2 comments ·
-
Intermittent test failureMay be free again @EnriqueL8 claimed this 902 days ago, and no pull request is open. Open
hyperledger-firefly/common#136 · 1 assignee ·
All issues in hyperledger-firefly/common
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
blinklabs-io/dingo#5368 ·
Maintainers usually reply within 1 day
-
difficulty: easy enhancement frontend good first issue help wanted priority: P2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
rafaelsilvabr/pdfHandler#18 ·
-
Difficulty 2/5 1-2 days Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day