This message was deleted.
# develocity
s
This message was deleted.
j
specifically, we have it currently set to 17, and have up to 370 scans/minute
(based on the metrics pulled from the info/ingest-queue endpoint)
r
@Javier Campanini the best way would be if you can raise a support ticket and include a support bundle. Then we can analyze the metrics we capture and see how those 17 workers are fairing with your ingest volume. Using the endpoint you can check if your processing rate keeps up with your incoming rate, but using the support bundle we will have a much better picture of things
j
perfect. i'll take a support bundle
ty!
would changing the number of workers require downtime?
r
Np. If you mention me on the ticket I will take a look
j
👍