DependencyTrack / DependencyTrack/dependency-track
Too many metrics requests causing SQL link failure
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 811
- Avg merge
- 8h 39m
- Merged PRs (30d)
- 237
Description
### Current Behavior
I used a database pool. Can I set a maximum request volume for metrics requests? If there are too many, or can I simply disable this loop update feature
### Steps to Reproduce
1. system update metrics;
2. sql connect timeout;
3.new api request error;
### Expected Behavior
Less metrics requests
### Dependency-Track Version
4.12.x
### Dependency-Track Distribution
Container Image
### Database Server
PostgreSQL
### Database Server Version
_No response_
### Browser
Google Chrome
### Checklist
- [x] I have read and understand the [contributing guidelines](https://github.com/DependencyTrack/dependency-track/blob/master/CONTRIBUTING.md#filing-issues)
- [x] I have checked the [existing issues](https://github.com/DependencyTrack/dependency-track/issues) for whether this defect was already reported
Contributor guide
Research direction
No source files, tests, or entry points are named. Start by tracing the database pool and metrics update loop described in the reproduction, then verify the SQL timeout and subsequent API request behavior. Done means metrics requests are reduced or the loop can be disabled without breaking API requests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, postgresql
- Domain
- backend, databases, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100