Skip to main content
The Settings > General page controls how Upmetr monitors your infrastructure. These are organization-level settings — each organization has its own independent configuration. Navigate to Settings > General to access all options below.
You need Admin or Superadmin role to change settings.

​
Discovery Settings

Controls automatic scanning of your connected cloud accounts for new or changed resources.
SettingDescriptionDefaultOptions
Automatic DiscoveryToggle scheduled resource scanning on or offOffOn / Off
Discovery IntervalHow often Upmetr re-scans your cloud accountsEvery hourEvery hour, Every 6 hours, Every 12 hours, Daily
When discovery is disabled, you can still trigger a manual scan from the Cloud Accounts page at any time.
For accounts with frequently changing resources (auto-scaling groups, spot instances), use a shorter interval like Every hour. For stable environments, Daily reduces API calls.

​
Uptime Monitoring

Configures HTTP endpoint and website monitoring. Uptime monitoring is always active — it cannot be disabled.
SettingDescriptionDefault
Check IntervalHow often each monitor is checked60 seconds
Each check performs up to 3 HTTP attempts (1 initial + 2 retries with 1-second delay) to avoid false positives from transient network issues. A monitor must pass a configurable recovery threshold (default: 2 consecutive successes) before auto-resolving an incident.

​
CloudWatch Metrics

Controls polling of AWS CloudWatch for managed service metrics (RDS, ALB, CloudFront, etc.).
SettingDescriptionDefaultOptions
CloudWatch PollingGlobal toggle for CloudWatch metrics collectionOffOn / Off
Polling IntervalHow often metrics are fetched from CloudWatch5 minutes5, 10, 15, or 30 minutes
CloudWatch polling has two layers of control:
  1. Global toggle — this setting page (applies to the entire organization)
  2. Per-account opt-in — each cloud account must also have CloudWatch enabled on the Cloud Accounts page
Both must be enabled for metrics to flow.
CloudWatch API calls incur AWS costs (~0.01per1,000metricdatapoints).Estimatedcost: 0.01 per 1,000 metric data points). Estimated cost: ~1–4/month per account depending on resource count. The IAM policy must include cloudwatch:GetMetricData and cloudwatch:ListMetrics.
GCP Monitoring and Azure Monitor polling can also be enabled per-account. These follow the same pattern as CloudWatch — a global toggle plus per-account opt-in.

​
Session & Security

Authentication and access control policies for your organization.
SettingDescriptionDefault
Session TimeoutMinutes of inactivity before a user is logged out30 minutes
MFA EnforcementRequire multi-factor authentication for all usersOff
Max Login AttemptsFailed login attempts before account lockout5
Lockout DurationMinutes an account stays locked after exceeding max attempts15 minutes
Enabling MFA Enforcement is strongly recommended for production environments. Users will be prompted to set up TOTP on their next login.

​
Data Retention

SettingDescriptionDefault
Data RetentionNumber of days to keep metric and log data90 days
Data older than the retention period is automatically purged. Adjust this based on your compliance requirements and storage needs.

​
Settings vs Organization

Upmetr separates monitoring behavior from organization identity:
  • Settings (this page) — controls how monitoring works: discovery intervals, polling, security policies, data retention.
  • Organization (separate page at Settings > Organization) — controls branding and identity: organization name, custom logo, accent colors, and whitelabeling options.
See the Organization guide for branding configuration.