FOUR-33794 Fix Ellucian clients are reporting slow performance

[caleeli]

Issue & Reproduction Steps

Scheduled metrics:clear ran simultaneously on every pod and tenant, spiking shared Redis.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-33794

[cursor]

PR Summary

Medium Risk
Operational behavior changes (metrics off by default, less frequent clears) affect observability and shared Redis; misconfiguration could hide production metrics until METRICS_ENABLED is set.

Overview
Addresses Redis spikes from metrics:clear running in lockstep across pods/tenants by making Prometheus collection opt-in and softening how clears are scheduled.

METRICS_ENABLED (default false) now controls whether metrics run at all: MetricsService lazy-initializes the registry, no-ops common write paths when disabled, and throws MetricsDisabledException on direct registry access; cache metrics wrapping in AbstractCacheFactory follows the same flag. Scheduled metrics:clear is skipped when metrics are off, moved into scheduleMetricsClear, and uses --stagger (random delay up to METRICS_CLEAR_STAGGER_MAX_SECONDS) with runInBackground / withoutOverlapping. The default clear interval changes from 10 minutes to daily (1440 minutes).

Tests enable metrics explicitly in setup and add coverage for the disabled path.

^{Reviewed by Cursor Bugbot for commit d6fb165. Bugbot is set up for automated code reviews on this repo. Configure here.}

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[caleeli]

Default value changed from 10minutos to 24hours

METRICS_CLEAR_INTERVAL=1440

enables or disables metrics

METRICS_ENABLED=false

Max random delay (seconds) before run clear metrics

METRICS_CLEAR_STAGGER_MAX_SECONDS=60

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit d6fb165. Configure here.}

[cursor]

Stagger overlaps short clear intervals

Low Severity

withoutOverlapping expires after clear_interval minutes while --stagger may sleep for the full interval. With METRICS_CLEAR_INTERVAL=1 (or 2) and the default 60s stagger cap, the mutex can expire while the first metrics:clear is still sleeping or wiping, so the next schedule starts a second clear against the same Redis keys.

Additional Locations (1)

• routes/console.php#L44-L51

 

^{Reviewed by Cursor Bugbot for commit d6fb165. Configure here.}