Running Scans

Learn how to scan your GCP resources for optimization opportunities, performance issues, and security gaps.

Scan Types

SmartSRE supports two types of scans:

Type	Trigger	Use Case
Manual	On-demand via UI	Ad-hoc analysis, troubleshooting
Scheduled	Automatic per scope	Continuous monitoring, compliance

Running a Manual Scan

From the Dashboard

1. Click Run Scan in the top navigation
2. Select the Service (e.g., BigQuery, Cloud Run)
3. Choose the Project to scan
4. Optionally select a Scope to limit resources
5. Click Start Scan

From the Service Console

1. Navigate to Operations → Service Console
2. Select a service tab (e.g., Cloud Run)
3. Click Scan on a specific project card

Scan Progress & Status

During a scan, you'll see:

• Progress indicator — Percentage complete
• Resource count — Number of resources discovered
• Status — running, completed, failed

Scans typically complete in 30-120 seconds depending on resource count.

Viewing Scan Results

After completion, navigate to the Run Details page to see:

Findings Tab

Lists all detected issues with:

• Severity — Color-coded badges (Critical, High, Medium, Low, Info)
• Issue Type — e.g., high_memory_usage, public_bucket
• Resource — Affected resource identifier
• Actions — Fix, Ignore, View Details

Artifacts Tab

Shows raw scan data including:

• Console output logs
• Metrics snapshots
• Resource configurations

Scheduled Scans

Enable Scheduled Scanning

1. Navigate to Settings → Scopes
2. Select or create a scope
3. Configure Scheduler Settings:
   • Interval — How often to scan (e.g., every 6 hours)
   • Time Window — When scans can run (e.g., business hours only)
4. Save the scope

Scheduler Behavior

• Scans run automatically at the configured interval
• Findings generate notifications based on tenant settings
• Historical scan results are retained for trend analysis

Scope Filtering

Scopes let you filter which resources are scanned. Configure scopes in Settings → Scopes to target:

• Specific projects — Only scan production, not development
• Specific regions — Only scan us-central1 resources
• Specific labels — Only scan resources with env=production label

See Scope Management for details.

Velocity Limits

To control costs and prevent runaway scans, SmartSRE enforces velocity limits:

Tier	Scans per Hour	Scans per Month
Free	2	20
Team	5	100
Pro	50	1,000
Enterprise	Unlimited	Unlimited

Troubleshooting

"Scan Failed" Error

1. Check that your GCP project is still connected
2. Verify the service account has required permissions
3. Review the error message in the Run Details → Artifacts tab

No Resources Found

1. Confirm resources exist in the selected project/region
2. Check scope filters aren't too restrictive
3. Verify API is enabled for the service in your GCP project

Scan Takes Too Long

Large projects (100+ resources) may take longer. Consider:

• Creating scopes to limit resource count
• Scheduling scans during off-peak hours

Next Steps

• Understanding Findings — Interpret scan results
• Applying Fixes — Execute remediation
• Scope Management — Configure scan targeting