@oneuptime/common 11.5.11 → 11.5.13

package/Server/Utils/AI/SRE/TelemetryImprovementTaskTrigger.ts

@@ -0,0 +1,114 @@
+import ObjectID from "../../../../Types/ObjectID";
+import CodeFixTaskType from "../../../../Types/AI/CodeFixTaskType";
+import CodeFixTaskContext from "../../../../Types/AI/CodeFixTaskContext";
+import BadDataException from "../../../../Types/Exception/BadDataException";
+import AIRun from "../../../../Models/DatabaseModels/AIRun";
+import Service from "../../../../Models/DatabaseModels/Service";
+import ServiceService from "../../../Services/ServiceService";
+import SubjectCodeFixRun from "./SubjectCodeFixRun";
+import CaptureSpan from "../../Telemetry/CaptureSpan";
+
+/*
+ * AI SRE — the service-scoped instrumentation-improvement triggers:
+ * ImproveLogging and ImproveTracing. One click on a service's Logs or
+ * Traces page opens a draft PR that improves that service's logging or
+ * tracing hygiene — parameterized log messages, correct severities, spans
+ * on uninstrumented paths, proper exception recording — WITHOUT changing
+ * behavior.
+ *
+ * Like FixFromIncident and FixPerformance these are human-triggered from a
+ * user-facing endpoint (POST /ai-investigation/
+ * create-telemetry-improvement-task), so there is no project opt-in flag —
+ * the human in the loop IS the gate — and every unmet gate FAILS EARLY
+ * with a clear message. The recipe's grounding is the SERVICE: repository
+ * resolution at task-details time uses the service name (name-match /
+ * only-repository), the same path the incident-subject recipes use.
+ */
+export default class TelemetryImprovementTaskTrigger {
+  /*
+   * Gate and enqueue an ImproveLogging / ImproveTracing CodeFix run for a
+   * telemetry service. The caller must already have loaded the service
+   * under the USER's permissions (the access check) — this method reads
+   * and writes as root.
+   *
+   * Throws BadDataException naming the failed gate: unsupported recipe, no
+   * GitHub-App repository, a duplicate active run for the same service, or
+   * (via enqueueSubjectCodeFixRun) the daily fix-run budget.
+   */
+  @CaptureSpan()
+  public static async createTelemetryImprovementTask(data: {
+    projectId: ObjectID;
+    telemetryServiceId: ObjectID;
+    taskType: CodeFixTaskType;
+    userId: ObjectID;
+  }): Promise<AIRun> {
+    if (
+      data.taskType !== CodeFixTaskType.ImproveLogging &&
+      data.taskType !== CodeFixTaskType.ImproveTracing
+    ) {
+      throw new BadDataException(
+        `Task type "${data.taskType}" is not a telemetry-improvement recipe. Supported: ${CodeFixTaskType.ImproveLogging}, ${CodeFixTaskType.ImproveTracing}.`,
+      );
+    }
+
+    const service: Service | null = await ServiceService.findOneById({
+      id: data.telemetryServiceId,
+      select: {
+        _id: true,
+        name: true,
+        projectId: true,
+      },
+      props: { isRoot: true },
+    });
+
+    if (
+      !service ||
+      service.projectId?.toString() !== data.projectId.toString()
+    ) {
+      throw new BadDataException("Telemetry service not found.");
+    }
+
+    // Gate — a repository the agent can actually open a PR against.
+    const hasConnectedRepository: boolean =
+      await SubjectCodeFixRun.hasGitHubAppConnectedRepository(data.projectId);
+
+    if (!hasConnectedRepository) {
+      throw new BadDataException(
+        "No GitHub-App-connected repository exists for this project, so the agent has nowhere to open the pull request. Connect one under AI > Code Repositories.",
+      );
+    }
+
+    /*
+     * Gate — per-(service, recipe) dedupe: repeated clicks must not fan
+     * out into duplicate PRs.
+     */
+    const existingRun: AIRun | null =
+      await SubjectCodeFixRun.findNonTerminalRunForTelemetryService({
+        projectId: data.projectId,
+        taskType: data.taskType,
+        telemetryServiceId: data.telemetryServiceId.toString(),
+      });
+
+    if (existingRun) {
+      throw new BadDataException(
+        `An ${
+          data.taskType === CodeFixTaskType.ImproveLogging
+            ? "improve-logging"
+            : "improve-tracing"
+        } task is already queued or running for this service. Track its progress on the AI > Tasks page.`,
+      );
+    }
+
+    const taskContext: CodeFixTaskContext = {
+      telemetryServiceId: data.telemetryServiceId.toString(),
+      serviceName: service.name || undefined,
+    };
+
+    return SubjectCodeFixRun.enqueueSubjectCodeFixRun({
+      projectId: data.projectId,
+      taskType: data.taskType,
+      userId: data.userId,
+      taskContext,
+    });
+  }
+}

package/Server/Utils/Monitor/MonitorResource.ts

@@ -1,6 +1,10 @@
 import MonitorProbeService from "../../Services/MonitorProbeService";
 import MonitorService from "../../Services/MonitorService";
-import MonitorStatusTimelineService from "../../Services/MonitorStatusTimelineService";
+import MonitorStatusTimelineService, {
+  MONITOR_STATUS_SAME_AS_PREVIOUS_ERROR_MESSAGE,
+  MONITOR_STATUS_TIMELINE_LOCK_ERROR_MESSAGE,
+} from "../../Services/MonitorStatusTimelineService";
+import ServerException from "../../../Types/Exception/ServerException";
 import logger from "../Logger";
 import MonitorCriteriaEvaluator from "./MonitorCriteriaEvaluator";
 import MonitorLogUtil from "./MonitorLogUtil";
@@ -1013,6 +1017,15 @@ export default class MonitorResourceUtil {
           monitorStatusTimeline.rootCause =
             "No monitoring criteria met. Change to default status. ";
 
+          /*
+           * Tracks whether the monitor really is at its default status after the
+           * create call, so the summary event below records only what actually
+           * happened. On the lock-skip path the write was REFUSED - recording a
+           * "reverted" event there would put a false entry in the monitor log and
+           * mask the very lock failure the error log surfaces.
+           */
+          let revertedToDefaultStatus: boolean = true;
+
           try {
             await MonitorStatusTimelineService.create({
               data: monitorStatusTimeline,
@@ -1033,29 +1046,45 @@ export default class MonitorResourceUtil {
              */
             if (
               err instanceof BadDataException &&
-              err.message ===
-                "Monitor Status cannot be same as previous status."
+              err.message === MONITOR_STATUS_SAME_AS_PREVIOUS_ERROR_MESSAGE
             ) {
               logger.debug(
                 `${dataToProcess.monitorId.toString()} - Monitor status already at default; skipping duplicate status timeline (concurrent race).`,
               );
+            } else if (
+              err instanceof ServerException &&
+              err.message === MONITOR_STATUS_TIMELINE_LOCK_ERROR_MESSAGE
+            ) {
+              /*
+               * The per-monitor timeline mutex could not be acquired (fail-closed
+               * create, see MonitorStatusTimelineService). Skipping is recoverable:
+               * the next probe result re-evaluates the same criteria and recreates
+               * the revert-to-default, while failing here would abort the whole
+               * ingest run and lose the monitor log for this probe result.
+               */
+              logger.error(
+                `${dataToProcess.monitorId.toString()} - Could not acquire the monitor status timeline lock; skipping revert to default status. It will be retried on the next probe result.`,
+              );
+              revertedToDefaultStatus = false;
             } else {
               throw err;
             }
           }
 
-          const defaultStatusName: string | null = await getMonitorStatusName(
-            monitorSteps.data.defaultMonitorStatusId,
-          );
+          if (revertedToDefaultStatus) {
+            const defaultStatusName: string | null = await getMonitorStatusName(
+              monitorSteps.data.defaultMonitorStatusId,
+            );
 
-          evaluationSummary.events.push({
-            type: "monitor-status-changed",
-            title: "Monitor status reverted",
-            message: defaultStatusName
-              ? `Monitor status reverted to "${defaultStatusName}" because no monitoring criteria were met.`
-              : "Monitor status reverted to its default state because no monitoring criteria were met.",
-            at: OneUptimeDate.getCurrentDate(),
-          });
+            evaluationSummary.events.push({
+              type: "monitor-status-changed",
+              title: "Monitor status reverted",
+              message: defaultStatusName
+                ? `Monitor status reverted to "${defaultStatusName}" because no monitoring criteria were met.`
+                : "Monitor status reverted to its default state because no monitoring criteria were met.",
+              at: OneUptimeDate.getCurrentDate(),
+            });
+          }
         }
       }
 

package/Server/Utils/Monitor/MonitorStatusTimeline.ts

@@ -5,7 +5,11 @@ import BadDataException from "../../../Types/Exception/BadDataException";
 import MonitorCriteriaInstance from "../../../Types/Monitor/MonitorCriteriaInstance";
 import ObjectID from "../../../Types/ObjectID";
 import { TelemetryQuery } from "../../../Types/Telemetry/TelemetryQuery";
-import MonitorStatusTimelineService from "../../Services/MonitorStatusTimelineService";
+import MonitorStatusTimelineService, {
+  MONITOR_STATUS_SAME_AS_PREVIOUS_ERROR_MESSAGE,
+  MONITOR_STATUS_TIMELINE_LOCK_ERROR_MESSAGE,
+} from "../../Services/MonitorStatusTimelineService";
+import ServerException from "../../../Types/Exception/ServerException";
 import logger, { LogAttributes } from "../Logger";
 import CaptureSpan from "../Telemetry/CaptureSpan";
 import DataToProcess from "./DataToProcess";
@@ -124,19 +128,19 @@ export default class MonitorStatusTimelineUtil {
       } catch (err) {
         /*
          * Concurrency race: two probe/ingest results for the same monitor can be
-         * processed near-simultaneously (the per-monitor mutexes in
-         * MonitorResourceUtil.monitorResource and MonitorStatusTimeline.create can
-         * time out under load and fall through unlocked). Both see the same prior
-         * status and both try to write the same new status row. The
+         * processed near-simultaneously and both see the same prior status, so both
+         * try to write the same new status row. The
          * MonitorStatusTimelineService.onBeforeCreate dedupe check then throws this
          * exact BadDataException for the loser of the race. This is an idempotent
          * no-op (the desired status is already the current status), so swallow it at
-         * debug level instead of failing the job and logging a full ERROR stack.
+         * debug level instead of failing the job and logging a full ERROR stack. The
+         * race itself is now logged at warn by onBeforeCreate, which is the
+         * authoritative telemetry for it - this log only records that we skipped.
          * Match the exact message so unrelated BadDataExceptions still propagate.
          */
         if (
           err instanceof BadDataException &&
-          err.message === "Monitor Status cannot be same as previous status."
+          err.message === MONITOR_STATUS_SAME_AS_PREVIOUS_ERROR_MESSAGE
         ) {
           logger.debug(
             `${input.monitor.id?.toString()} - Monitor status already equals desired status; skipping duplicate status timeline (concurrent race).`,
@@ -144,6 +148,27 @@ export default class MonitorStatusTimelineUtil {
           return null;
         }
 
+        /*
+         * The per-monitor mutex in MonitorStatusTimelineService.create() is
+         * fail-closed: if Redis is unavailable or the lock cannot be acquired within
+         * the acquire timeout, the create is refused rather than performed unlocked.
+         * Writing unlocked is what produced permanently orphaned (endsAt = NULL)
+         * timeline rows, which read back as unbounded downtime on status pages and
+         * uptime reports - far worse than a missed status transition. Skipping is
+         * recoverable: the next probe result for this monitor evaluates the same
+         * criteria and creates the same status change. So log and skip rather than
+         * failing the whole probe ingest run for this monitor.
+         */
+        if (
+          err instanceof ServerException &&
+          err.message === MONITOR_STATUS_TIMELINE_LOCK_ERROR_MESSAGE
+        ) {
+          logger.error(
+            `${input.monitor.id?.toString()} - Could not acquire the monitor status timeline lock; skipping this status change. It will be retried on the next probe result.`,
+          );
+          return null;
+        }
+
         throw err;
       }
     }

package/Server/Utils/Monitor/MonitorStatusTimelineReconciler.ts

@@ -0,0 +1,362 @@
+import PostgresAppInstance, {
+  DatabaseSource,
+} from "../../Infrastructure/PostgresDatabase";
+import DatabaseNotConnectedException from "../../../Types/Exception/DatabaseNotConnectedException";
+import ObjectID from "../../../Types/ObjectID";
+import logger from "../Logger";
+import CaptureSpan from "../Telemetry/CaptureSpan";
+
+/*
+ * A "stale open row" is a MonitorStatusTimeline row with endsAt IS NULL for which a row
+ * with a strictly later startsAt exists on the same monitor.
+ *
+ * These are produced by a write-path race: two probe results for the same monitor can be
+ * processed near-simultaneously, both resolve the same predecessor row, and both INSERT a
+ * new status row milliseconds apart. Only the later one is ever closed, because every
+ * subsequent writer resolves its predecessor with ORDER BY startsAt DESC LIMIT 1 and so
+ * permanently shadows the earlier one. The earlier row keeps endsAt = NULL forever.
+ *
+ * An open row with no successor is the monitor's legitimate current-state row and MUST be
+ * left open. Only rows that have been superseded are repaired here.
+ *
+ * The repaired endsAt is the MIN startsAt among strictly later rows on the same monitor -
+ * i.e. the moment the row was actually superseded. It is deliberately NOT "now" and NOT the
+ * startsAt of the newest row: closing an orphan at the newest row's startsAt would convert a
+ * near-zero-duration orphan into a multi-month closed downtime row, which is unrecoverable
+ * and strictly worse than leaving it open.
+ */
+
+export interface RepairStaleOpenRowsOptions {
+  // Maximum number of open rows examined per monitor per round trip.
+  batchSize?: number | undefined;
+  // When set, only this monitor is reconciled. When unset, every affected monitor is.
+  monitorId?: ObjectID | undefined;
+}
+
+export interface RepairStaleOpenRowsResult {
+  // Open rows examined across every batch of this run.
+  scanned: number;
+  // Open rows that were given an endsAt by this run.
+  repaired: number;
+  // Monitors that had at least one stale open row when the run started.
+  monitorsWithStaleRows: number;
+  // Monitors that had at least one row repaired. Callers may want to refresh their current status.
+  repairedMonitorIds: Array<ObjectID>;
+  // Monitors whose repair threw. They are skipped, not retried, so one failure cannot abort a run.
+  failedMonitorIds: Array<ObjectID>;
+}
+
+interface RepairBatchResult {
+  scanned: number;
+  repaired: number;
+}
+
+/*
+ * Bounded so a single run never loads a pathological monitor's whole backlog into memory.
+ * Production currently has ~67.5k stale rows, ~56k of them on ONE monitor.
+ */
+export const DEFAULT_STALE_OPEN_ROW_BATCH_SIZE: number = 1000;
+
+const MIN_BATCH_SIZE: number = 1;
+const MAX_BATCH_SIZE: number = 10000;
+
+/*
+ * Pure runaway guard. Every non-terminal round repairs exactly batchSize rows, so the loop
+ * is already guaranteed to terminate; this only bounds a run if that invariant is ever broken.
+ */
+const MAX_ROUNDS: number = 100000;
+
+export default class MonitorStatusTimelineReconciler {
+  /*
+   * Finds and repairs stale open rows. Idempotent: a second run over the same data repairs
+   * nothing, because a repaired row no longer matches endsAt IS NULL.
+   *
+   * Monitors are processed round-robin, one batch each per round, so a monitor with tens of
+   * thousands of stale rows cannot starve the rest of the fleet.
+   */
+  @CaptureSpan()
+  public static async repairStaleOpenRows(
+    options: RepairStaleOpenRowsOptions = {},
+  ): Promise<RepairStaleOpenRowsResult> {
+    const batchSize: number = this.getBatchSize(options.batchSize);
+
+    const monitorIds: Array<ObjectID> = options.monitorId
+      ? [options.monitorId]
+      : await this.getMonitorIdsWithStaleOpenRows();
+
+    const result: RepairStaleOpenRowsResult = {
+      scanned: 0,
+      repaired: 0,
+      monitorsWithStaleRows: monitorIds.length,
+      repairedMonitorIds: [],
+      failedMonitorIds: [],
+    };
+
+    if (monitorIds.length === 0) {
+      logger.debug(
+        "MonitorStatusTimelineReconciler: no monitors have stale open status timeline rows.",
+      );
+      return result;
+    }
+
+    logger.debug(
+      `MonitorStatusTimelineReconciler: ${monitorIds.length} monitor(s) have stale open status timeline rows. Batch size ${batchSize}.`,
+    );
+
+    const repairedMonitorIds: Set<string> = new Set<string>();
+    const failedMonitorIds: Set<string> = new Set<string>();
+
+    let pendingMonitorIds: Array<ObjectID> = monitorIds;
+    let round: number = 0;
+
+    while (pendingMonitorIds.length > 0) {
+      round++;
+
+      if (round > MAX_ROUNDS) {
+        logger.error(
+          `MonitorStatusTimelineReconciler: aborting after ${MAX_ROUNDS} rounds with ${pendingMonitorIds.length} monitor(s) still pending. This should be unreachable.`,
+        );
+        break;
+      }
+
+      const stillPendingMonitorIds: Array<ObjectID> = [];
+
+      for (const monitorId of pendingMonitorIds) {
+        /*
+         * Per-monitor try/catch, matching the sibling KeepCurrentStateConsistent jobs: one bad
+         * monitor is skipped for the remainder of the run instead of aborting it. It is not
+         * re-queued, so a monitor that fails deterministically cannot spin forever.
+         */
+        try {
+          const batch: RepairBatchResult = await this.repairStaleOpenRowsBatch({
+            monitorId: monitorId,
+            batchSize: batchSize,
+          });
+
+          result.scanned += batch.scanned;
+          result.repaired += batch.repaired;
+
+          if (batch.repaired > 0) {
+            repairedMonitorIds.add(monitorId.toString());
+          }
+
+          /*
+           * A full batch of repairs means there may be more stale rows on this monitor. Anything
+           * short of a full batch means every open row on this monitor has now been examined -
+           * whatever is still open has no strictly later row and is therefore legitimate.
+           */
+          if (batch.repaired >= batchSize) {
+            stillPendingMonitorIds.push(monitorId);
+          }
+        } catch (err) {
+          failedMonitorIds.add(monitorId.toString());
+          logger.error(
+            `MonitorStatusTimelineReconciler: failed to repair stale open rows for monitor ${monitorId.toString()}.`,
+          );
+          logger.error(err);
+          continue;
+        }
+      }
+
+      pendingMonitorIds = stillPendingMonitorIds;
+    }
+
+    result.repairedMonitorIds = Array.from(repairedMonitorIds).map(
+      (id: string) => {
+        return new ObjectID(id);
+      },
+    );
+
+    result.failedMonitorIds = Array.from(failedMonitorIds).map((id: string) => {
+      return new ObjectID(id);
+    });
+
+    return result;
+  }
+
+  /*
+   * Counts stale open rows without repairing anything. Useful for telemetry and for asserting
+   * that a repair run actually converged.
+   */
+  @CaptureSpan()
+  public static async countStaleOpenRows(
+    options: { monitorId?: ObjectID | undefined } = {},
+  ): Promise<number> {
+    const dataSource: DatabaseSource = this.getDataSource();
+
+    const parameters: Array<string> = [];
+    let monitorFilter: string = "";
+
+    if (options.monitorId) {
+      monitorFilter = `AND t."monitorId" = $1::uuid`;
+      parameters.push(options.monitorId.toString());
+    }
+
+    const sql: string = `
+      SELECT COUNT(*)::int AS "staleCount"
+      FROM "MonitorStatusTimeline" t
+      WHERE t."endsAt" IS NULL
+        AND t."deletedAt" IS NULL
+        AND t."startsAt" IS NOT NULL
+        ${monitorFilter}
+        AND EXISTS (
+          SELECT 1
+          FROM "MonitorStatusTimeline" n
+          WHERE n."monitorId" = t."monitorId"
+            AND n."deletedAt" IS NULL
+            AND n."startsAt" > t."startsAt"
+        )
+    `;
+
+    const rows: Array<{ staleCount: number }> = await dataSource.query(
+      sql,
+      parameters,
+    );
+
+    return rows[0]?.staleCount || 0;
+  }
+
+  /*
+   * The set of monitors that currently have at least one stale open row.
+   *
+   * Note this is deliberately NOT "monitors with more than one open row". A monitor can have
+   * exactly one open row that is still stale, if the newest row on the monitor happens to be
+   * closed. Encoding the definition directly keeps both cases covered.
+   */
+  private static async getMonitorIdsWithStaleOpenRows(): Promise<
+    Array<ObjectID>
+  > {
+    const dataSource: DatabaseSource = this.getDataSource();
+
+    const sql: string = `
+      SELECT DISTINCT t."monitorId" AS "monitorId"
+      FROM "MonitorStatusTimeline" t
+      WHERE t."endsAt" IS NULL
+        AND t."deletedAt" IS NULL
+        AND t."startsAt" IS NOT NULL
+        AND EXISTS (
+          SELECT 1
+          FROM "MonitorStatusTimeline" n
+          WHERE n."monitorId" = t."monitorId"
+            AND n."deletedAt" IS NULL
+            AND n."startsAt" > t."startsAt"
+        )
+      ORDER BY t."monitorId" ASC
+    `;
+
+    const rows: Array<{ monitorId: string }> = await dataSource.query(sql);
+
+    return rows.map((row: { monitorId: string }) => {
+      return new ObjectID(row.monitorId);
+    });
+  }
+
+  /*
+   * Repairs up to batchSize stale open rows on a single monitor, oldest first.
+   *
+   * Ordering is by startsAt, NEVER createdAt. createdAt is assigned DB-side by now() while
+   * startsAt is assigned by the worker pod's clock, so the two orderings genuinely disagree on
+   * real data. Two earlier migrations ordered by createdAt and produced wrong results.
+   */
+  private static async repairStaleOpenRowsBatch(data: {
+    monitorId: ObjectID;
+    batchSize: number;
+  }): Promise<RepairBatchResult> {
+    const dataSource: DatabaseSource = this.getDataSource();
+
+    /*
+     * candidates is materialised once (a data-modifying CTE forces materialisation), so the
+     * counts below and the UPDATE all see the same snapshot and one round trip yields both the
+     * scanned and the repaired count.
+     *
+     * nextStartsAt is NULL for an open row with no strictly later row. Those rows are the
+     * legitimate current-state row (or a startsAt tie at the head of the timeline) and are
+     * excluded from the UPDATE, so they stay open.
+     *
+     * The UPDATE re-checks m."endsAt" IS NULL even though candidates already filtered on it:
+     * the reconciler runs WITHOUT the per-monitor mutex, and under READ COMMITTED a live
+     * writer can close a candidate row between this statement's snapshot and the UPDATE
+     * taking the row lock. Postgres then re-evaluates only the UPDATE's own WHERE against
+     * the new row version (EvalPlanQual), so the openness check must live in the UPDATE
+     * itself - otherwise the reconciler would overwrite the endsAt the writer just committed
+     * with its stale snapshot-time value.
+     */
+    const sql: string = `
+      WITH candidates AS (
+        SELECT
+          t."_id" AS "_id",
+          (
+            SELECT MIN(n."startsAt")
+            FROM "MonitorStatusTimeline" n
+            WHERE n."monitorId" = t."monitorId"
+              AND n."deletedAt" IS NULL
+              AND n."startsAt" > t."startsAt"
+          ) AS "nextStartsAt"
+        FROM "MonitorStatusTimeline" t
+        WHERE t."monitorId" = $1::uuid
+          AND t."endsAt" IS NULL
+          AND t."deletedAt" IS NULL
+          AND t."startsAt" IS NOT NULL
+        ORDER BY t."startsAt" ASC
+        LIMIT $2
+      ),
+      repaired AS (
+        UPDATE "MonitorStatusTimeline" m
+        SET "endsAt" = c."nextStartsAt",
+            "updatedAt" = NOW(),
+            "version" = m."version" + 1
+        FROM candidates c
+        WHERE m."_id" = c."_id"
+          AND m."endsAt" IS NULL
+          AND c."nextStartsAt" IS NOT NULL
+        RETURNING m."_id"
+      )
+      SELECT
+        (SELECT COUNT(*) FROM candidates)::int AS "scanned",
+        (SELECT COUNT(*) FROM repaired)::int AS "repaired"
+    `;
+
+    const rows: Array<{ scanned: number; repaired: number }> =
+      await dataSource.query(sql, [
+        data.monitorId.toString(),
+        data.batchSize.toString(),
+      ]);
+
+    const scanned: number = rows[0]?.scanned || 0;
+    const repaired: number = rows[0]?.repaired || 0;
+
+    if (repaired > 0) {
+      logger.debug(
+        `MonitorStatusTimelineReconciler: repaired ${repaired} of ${scanned} open row(s) examined on monitor ${data.monitorId.toString()}.`,
+      );
+    }
+
+    return {
+      scanned: scanned,
+      repaired: repaired,
+    };
+  }
+
+  private static getBatchSize(batchSize?: number | undefined): number {
+    if (
+      !batchSize ||
+      !Number.isFinite(batchSize) ||
+      batchSize < MIN_BATCH_SIZE
+    ) {
+      return DEFAULT_STALE_OPEN_ROW_BATCH_SIZE;
+    }
+
+    return Math.min(Math.floor(batchSize), MAX_BATCH_SIZE);
+  }
+
+  private static getDataSource(): DatabaseSource {
+    const dataSource: DatabaseSource | null =
+      PostgresAppInstance.getDataSource();
+
+    if (!dataSource) {
+      throw new DatabaseNotConnectedException();
+    }
+
+    return dataSource;
+  }
+}