7fa2b61b29
Tweaks to how execution time is tracked for more accuracy + excluding waiting states: - don't update if crawl state is in a 'waiting state' (waiting for capacity or waiting for org limit) - rename start states -> waiting states for clarity - reset lastUpdatedTime if two consecutive updates of non-running state, to ensure non-running states don't count, but also account for occasional hiccups -- if only one update detects non-running state, don't reset - webhooks: move start webhook to when crawl actually starts for first time (db lastUpdatedTime is not yet + crawl is running) - don't set lastUpdatedTime until pods actually running - set crawljob update interval to every 10 seconds for more accurate execution time tracking - frontend: show seconds in 'Execution Time' display |
||
|---|---|---|
| .. | ||
| backend.yaml | ||
| configmap.yaml | ||
| frontend.yaml | ||
| ingress.yaml | ||
| minio.yaml | ||
| mongo.yaml | ||
| namespaces.yaml | ||
| networkpolicies.yaml | ||
| operators.yaml | ||
| priorities.yaml | ||
| role.yaml | ||
| secrets.yaml | ||
| service.yaml | ||
| signer.yaml | ||