Overview
The Overview page is your app's main dashboard. It's where you get a quick health check without digging through settings. One glance tells you everything that matters right now.
Quick Status Check
At the top of the page, you'll see your app's name and its current status at a glance. The info card below shows six fields in a grid:
| Field | Description |
|---|---|
| Status | The current app state. See the full list of statuses below |
| App Type | The runtime your app uses |
| Plan | Your current plan tier |
| Region | Where your app is deployed |
| High-availability | On or Off, depending on whether your containers qualify |
| Containers | How many containers are running and their size |
Here's what each app status means:
| Status | Description |
|---|---|
| Pending Deployment | App created, no deployment yet |
| Queued | Job queued, waiting for worker |
| Building | Worker building Docker image |
| Deploying | Deploying to Kubernetes |
| Running | Successfully running |
| Unhealthy | Health checks failing |
| Crashed | Container crashed |
| Restarting | Attempting restart |
| Stopped | User stopped |
| Suspended | Admin suspended |
| Failed | Deployment failed |
| Deleted | Soft deleted |
Common Actions
At the top right of the page, you'll find action buttons for the most common operations. Which buttons appear depends on your app type and its current state.
Open App: Opens your live application in a new tab.
Settings: Jumps to your app's Settings page. Change Git config, domains, health checks, and more.
Upgrade App: Takes you to the Plans section to change your container size or plan tier.
Restart: Forces a clean restart without redeploying. Good for clearing transient issues when your app is stuck.
Stop / Start: Pauses your app without deleting it (Stop), or brings it back up (Start). The button toggles based on whether your app is currently running. Stopped apps don't incur container charges.
APM (Meteor apps only): Opens Monti APM for performance monitoring. Only available on apps with a Professional plan.
SEO (Meteor apps only): Opens the SEO configuration for your Meteor app.
Bookmark your app's Overview page. You'll be checking it constantly, and it's the fastest way to see what's happening.
Performance
Below the info card, you'll find the Performance section. This shows real-time charts for your app's resource usage. Two badges at the top show your container's configured limits: CPU LIMIT and MEMORY LIMIT.
Use the Filter by Time dropdown (top right of the section) to change the time window. The default is 1 hour.
Three charts are available:
CPU Usage: Tracks how much processing power your app is consuming over time, measured in millicores (m). Watch for spikes that correlate with traffic or deployments.
Memory Usage: Shows RAM consumption in MB. A steadily climbing line can indicate a memory leak. If it's consistently near your memory limit, consider upgrading to a larger container.
Requests: Shows incoming request rate in requests per minute (req/min). Useful for correlating traffic patterns with CPU and memory usage.
No Data Showing?
If your app is stopped or hasn't received traffic recently, the charts will be empty. Start your app and send some requests to see data populate.
Activity Feed
On the right side of the page, the Activity Feed shows a chronological log of everything that's happened to your app. Each entry shows an icon, a description, and a timestamp.
Events you'll see here include:
- App created: When the app was first provisioned
- Domain added: When a custom domain was configured
- Deployment started / completed / failed: Each stage of a deployment cycle, with version number
- Build started / completed: Build phase events, with duration
- App started / stopped: Manual start and stop actions, showing who triggered them
The feed gives you a quick audit trail without needing to dig into Deployments or Logs. If something changed unexpectedly, check here first.
High-Availability
High-availability makes your app more resilient. When enabled, Galaxy distributes your containers across different availability zones in the same region. If one zone goes down, your app keeps running on the others.
This is crucial for production apps. Your users won't notice an outage when you have high-availability enabled.
How High-Availability Works
Galaxy supports high-availability automatically, but you need to meet two requirements:
- Container size: Standard (1GB) or larger
- Container count: Three or more containers
That's it. Once both conditions are met, Galaxy automatically enables HA and spreads your containers across different availability zones. You'll see a green "On" indicator next to High-Availability in your app's overview.
Checking Your HA Status
Look at the High-Availability field in your overview. You'll see one of two states:
On (green): Your app is fault-tolerant across availability zones. You're protected if a zone goes down.
Off (red): Your app doesn't meet the requirements yet. Either your containers are too small, or you don't have enough of them.
Click the status to see exactly what you need to do.
Enabling High-Availability
Getting HA up and running takes just a few steps:
- Go to your app's Plans section
- Change the container size to Standard (1GB) or larger
- Add containers until you have three or more running
- Check back at Overview: HA should now show as "On"
Minimum Container Size Required
Smaller containers don't qualify for high-availability, even if you run three or more of them. You need 1GB containers at minimum.
What's Next?
Apps Menu
The Apps section is your command center for managing all your deployed applications. Whether you're running one app or dozens, everything you need to monitor, scale, and troubleshoot is right here.
Containers
Understand container status, monitor resources, and scale your app to handle growth.