fix execution minutes meter using wrong metric (#1967)

The monthly execution minutes meter was using the wrong metric,
`crawlExecSeconds` instead of `monthlyExecSeconds`.
Since the meter is showing minutes used out of the monthly quota, it
should be using `monthlyExecSeconds`.

This is a quick fix, however, this system may need another pass at some
point.

---------
Co-authored-by: sua yoo <sua@suayoo.com>
This commit is contained in:
Ilya Kreymer 2024-07-24 09:14:15 -07:00 committed by GitHub
parent 24c8963dba
commit b288cd81cc
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 4 additions and 2 deletions

View File

@ -395,8 +395,8 @@ export class Dashboard extends LiteElement {
}
let usageSecondsAllTypes = 0;
if (this.org.crawlExecSeconds) {
const actualUsage = this.org.crawlExecSeconds[currentPeriod];
if (this.org.monthlyExecSeconds) {
const actualUsage = this.org.monthlyExecSeconds[currentPeriod];
if (actualUsage) {
usageSecondsAllTypes = actualUsage;
}

View File

@ -39,7 +39,9 @@ export type OrgData = {
bytesStoredUploads: number;
bytesStoredProfiles: number;
usage: { [key: YearMonth]: number } | null;
/* Actual total time used, including time to stop the crawl, gifted, and extra time */
crawlExecSeconds?: { [key: YearMonth]: number };
/* Total time within the monthly time quota */
monthlyExecSeconds?: { [key: YearMonth]: number };
extraExecSeconds?: { [key: YearMonth]: number };
giftedExecSeconds?: { [key: YearMonth]: number };