Dependency Track API Timeouts #4596
Replies: 1 comment 3 replies
-
If you're using the sample Grafana dashboard we distribute, be aware that some of the graphs will not show a value if the value is
Edit: Sorry, you wrote it already. It's For that endpoint, can you try migrating to the You could also try to temporarily disable BOM validation in the settings, to see if that helps. BOM validation is the most expensive action performed by the BOM upload endpoints. |
Beta Was this translation helpful? Give feedback.
-
We are experiencing intermittent timeouts when interacting with the Dependency Track API. This occurs approximately 10-20 times per day, but not consistently.
Environment:
All components are hosted in AWS.
Dependency Track is deployed in AWS EKS with 4 CPU and 16GB RAM. No relevant errors are present in the Dependency Track logs.
The database is hosted on an EC2 t4g.medium instance. No relevant errors are present in the database logs.
Dependency Track version: v4.12.1
Database type: PostgreSQL
Observations:
We have Grafana dashboards set up for monitoring Dependency Track. While there are no critical issues evident, we do see some intermittent gaps in the following metrics:

Database Operations
Database Transactions
Average Connection Usage Duration
Problem Reproduction:
We have observed timeouts specifically on PUT requests to the /api/v1/bom endpoint. The requests time out after 300+ seconds.
Troubleshooting Steps Taken:
Verified Dependency Track and database logs for errors.
Checked network connectivity between the EKS cluster and the database instance.
Monitored resource utilization (CPU, memory, I/O) on both the EKS nodes and the database instance.
Adjusted the following Dependency Track configuration parameters (increasing and decreasing values):
ALPINE_DATABASE_POOL_MIN_IDLE
ALPINE_DATABASE_POOL_MAX_SIZE
Increased resources for the Dependency Track pod + 2 CPU and +8GB RAM.
Unfortunately, none of these steps have resolved the timeout issues.
We would appreciate any guidance on localizing and resolving these timeout issues. Could you please provide insights on potential causes and further troubleshooting steps?
Thank you for you time.
Beta Was this translation helpful? Give feedback.
All reactions