temporalio / temporalio/temporal
i get taskqueue history metics,it has abort all 80000 activities metrics.it is to large for promethues to pull
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
i get taskqueue history metics,it has abort all 80000 activities metrics.it is to large for promethues to pull
Actual Behavior
i get taskqueue history metics,it has abort all 80000 activities metrics.it is to large for promethues to pull
Steps to Reproduce the Problem
Specifications
- Version:
- Platform:
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
Start by reproducing the taskqueue history metrics behavior described in the issue and inspect the Prometheus scrape response. Determine why roughly 80,000 activity metrics are emitted and define a smaller, scrapeable result; done means the history metrics can be collected successfully without exceeding Prometheus's pull capacity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, prometheus
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100