Skip to main content

Alerts, Jobs, and Updates

Alerts, Jobs, and Updates

Overview

Alerts, scheduled jobs, and container updates arehelp platform operations features. They help operators detect issues, run recurring work, and safely updatekeep CMS containerservices services.current.

Alerts

CMSAlerts alertsappear includein alertthe type,notification status, area, closed state, title, message, related type,area and relatedAlerts ID.

page.

CurrentThey system-generatedhelp alertusers sourcesidentify includeissues that need attention, such as missing usage, missing subscriptions, region health, identity health, missing billing information, cost alerts,issues, or license validity.

Each alert includes a title, message, area, severity or type, status, and licenserelated validityrecord alerts.

where

License validity alerts are platform-only operational alerts. They are created by the scheduled license validity job inside the 90-day expiration window, escalate after expiration, and close automatically after renewal.available.

Alert Visibility

AlertsUsers mustsee respectalerts CMSaccording ownershipto hierarchy.their role and organisation access.

Role VisibilityTypical visibility
PlatformAdministrator AllPlatform alerts,alerts includingand licenseall validityscoped alerts.
DistributorAdministrator Distributor, partner, tenant, and subscription alerts inside distributor scope.
PartnerAdministrator Partner, tenant, and subscription alerts inside partner scope.
TenantAdministrator Tenant and subscription alerts inside tenant scope.
TenantUser Tenant-level alerts where appropriate.enabled.

License validity alerts are stricter:intended onlyfor PlatformAdministratorplatform can see or manage them.administrators.

Manual Review Required: The alerts featureworkspace documentshould saysbe thereviewed alertas engine,new UI filtering, closing, custom alerts, and all system-generated alert sources needare broaderadded. healthOperators review.should Doconfirm not assume every futurethe alert sourcemessage isexplains complete.the required action before relying on it for a process.

Scheduled Jobs

Administration > Jobs provideshows scheduled jobs and recent run history for long-running platform work. Scheduled jobs store recurring platform schedules.

The hosted scheduled jobs service wakes every 10 minutes and runs due enabled jobs. Manual runs and background runs share ScheduledJobRunnerService.roles.

Supported scheduled job types include:

Job type Purpose
DatabaseBackupDatabase backup Run theRuns configured CMS database backup tier and apply cleanup.tiers.
UsageCollectionUsage collection CollectCollects current-month usage, generate billing,usage and generateprepares commissions.billing-related data.
UsageDataCleanupUsage data cleanup DeleteRemoves expired usage rows onlydata when cleanup settings allow it.
RegionHealthRegion health RefreshRefreshes region and identity health for configured regions.health.
DelinquentPaymentNotificationsDelinquent payment notifications UpdateSends overdue invoice statuses and send one overdue reminder per invoicereminders when enabled.
BudgetAlertsBudget alerts Evaluate tenant and subscriptionSends budget warning or breach notifications.notifications when enabled.
LicenseValidityLicense validity CreateRaises or close platformclears license validity alerts.

The Scheduled jobs stuck in Running for more than 24 hours are treated as stale and can be recovered.

Jobs Page

Administration > Jobs istab availableshows at /administration/jobs for platform roles.

The page includes:

  • Scheduled Jobs.
  • Run History.
  • Type,type, enabled state, current status, last run, last status, next run, and descriptiondescription. columns.
    • Platform
  • Manualadministrators Runcan Nowrun actionssupported forjobs platform administrators.
manually.

Implementation Gap: TheRegion-specific Jobsjob featurehistory backlogis sayslisted as an area for improvement. Use the jobsmain Run History tab forwhen a specificregion regiondetail view does not currently show the jobsexpected forjob that region.entries.

Updates

CMSAdministration supports> platform-adminUpdates containerlets updateplatform workflowsadministrators throughreview aavailable separateversions, CMS.Updaterread sidecar.release Thenotes, APIinspect image tags, check service health, and Portalstart doCMS notapplication mount Docker directly.updates.

The Updatesupdate pageworkflow includes:uses the Patch Manager service. The portal shows update progress and service health from CMS.

Update pages can show:

  • Available versionversions selection fromfor the configured release manifest.channel.
  • Release readme display.notes.
  • ImageService tagimage display.tags.
  • Backup-required warnings.
  • Install action.
  • Container health widget.health.
  • UpdatesUpdate settings.

Access

TheAlerts updaterare sidecarvisible appliesaccording releaseto imageorganisation overridesscope. only for CMS application services: API, Portal,Jobs and Updater.Updates Proxyare platform operations areas. Manual scheduled job runs and databaseupdate imageinstalls referencesrequire areplatform treatedadministrator asaccess.

manifest

If metadataa user cannot see a job, update action, or alert, check their role, organisation scope, and healthwhether entriesthe only.

related

Update Security

All update API routes require PlatformAdministrator.

UpdaterApiKeyfeature is a secret database setting and must match the updater sidecar environment variable. The Portal polls CMS API status routes and never talks directly to the updater sidecar.enabled.

Operational Notes

TakeBefore arunning MySQLupdate or backup-related maintenance, confirm the current backup beforerequirements applyingand scriptsthe that seed scheduled jobs, notification state,selected update settings,version's or backup settings.warnings.

Planned Behaviour: Signed manifest verification, rollback UI, and combined multi-service release manifests are listed as future update backlog items.improvements.

Back to top