Monitoring your app
Monitoring means keeping an eye on your live app — is it up, how hard are the servers working, and is anything slowing down? The good news: The Deployer sets all of this up for you automatically. You don't have to install, configure, or connect anything. This page shows you what you get and where to find it.
Set up for you, with zero effort
The moment your app deploys, The Deployer also wires in a small monitoring stack:
- Grafana — a dashboards tool that turns raw numbers into easy-to-read charts.
- Prometheus — the piece that collects and stores those numbers (called "metrics") over time.
- Two behind-the-scenes collectors that feed Prometheus real data about your servers and your app's containers, so the charts are populated for any app on any cloud — no code changes required from you.
On top of that, The Deployer finds a health endpoint on your app (a URL it can quietly ping to confirm your app is alive) and sets up a probe that watches it. If your app doesn't have one, the Code Doctor can add it during setup.
Switching tools on and off after launch
The extras (uptime check, crash reports, charts, logs, alerts, database backups) are not fixed at launch. On an app that runs on one server, open the Extras panel, switch what you want, and read the review before you confirm: what is installed or removed, what it does to your bill (these run on the server you already pay for, so nothing is added), whether it fits the server, and what you lose by switching something off. The change runs as a short job you can follow in Launch. Your app keeps running and nothing is rebuilt. If the tools would not fit the server's memory, the panel says so and points you to the Scaling card to resize it first.
Where to find it on the Dashboard
Everything lives on your project's Dashboard:
- Live services card — this is where the Grafana web address (URL) appears, with a health badge and a clickable link. Click it to open your dashboards. Prometheus has no address of its own: it has no sign-in screen, so it is never put on the internet. You read its numbers inside Grafana (open Explore, then pick Prometheus).
- Service logins card — this is where you'll find the username and password to sign in to Grafana (and any other tool). Passwords are hidden until you click the show/hide toggle. See service logins.
So the usual flow is: open Grafana from Live services, then sign in with the details from Service logins.
Who can open your dashboards
Your dashboards hold information about your app, so they are not open to the whole internet.
- With a domain, Grafana (and your other tools) are served at their own address on your domain, such as
grafana.yourdomain.com, over HTTPS. Nothing else about your server is open for them. - Without a domain, your tools are shut to everyone except the addresses you allow. When you launch, we allow the address you launched from. To change that, open the Addresses card and use the Tool access tab: add the IP addresses you work from, or remove one. This kind of address is plain HTTP, so the sign-in travels unencrypted. Connect a domain to get HTTPS and drop the list.
- A server made before these rules may still have its tool ports open to the internet. We allow the address you last signed in or deployed from, and the Tool access tab says that is where it came from. If we cannot find an address of yours, we add an item to your project's to-do list and email you once, so you can add one before anything is closed.
To limit who can open your app itself, see who can open your app.
If your internet address changes (a new network, a different office), the dashboards will stop opening until you add the new address in that tab. The tab has an Add my current address button for exactly this.
What you can see
Once you're in Grafana, the starter dashboard shows the essentials for any app:
- CPU usage — how busy your server's processor is (the CPU is the part that does the computing).
- Memory (RAM) usage — how much of your server's short-term working memory is in use.
- Disk and network activity.
- Per-container breakdowns, so you can see which part of your app is using what.
- Request health — whether your app is responding, based on that health probe.
You'll also spot quick CPU, RAM, and disk meters right on the Dashboard's Servers card for an at-a-glance read without even opening Grafana — see connecting to your servers.
Tip
Remember to change Grafana's default password after your first sign-in — see the reminder in service logins.