Migrate from Gatus

In your dashboard, open Import from another service and upload your config.yaml under Import from Gatus. The importer reads the endpoints and external-endpoints lists and nothing else, so alerting settings, webhook URLs and push tokens in the file are ignored and never kept. If your configuration is split across several files, upload each one.

The preview lists every endpoint with what it becomes. HTTP endpoints become HTTP checks at their own interval (Gatus's default is 60 seconds), tcp:// endpoints become TCP checks, and DNS endpoints become DNS checks for A, AAAA, CNAME, MX, TXT and NS records. A [BODY] == pat(*text*) condition becomes a body assertion. Other conditions, such as JSONPath or response time, are counted in the preview so you can rebuild them. The group name is kept at the front of each check's name. Imports count against your plan's monitors, 10 on Free.

An external endpoint with a heartbeat.interval becomes a heartbeat monitor here. Its Gatus token is a credential and is never read, so each heartbeat gets a new ping URL, shown once on the result screen. Change the job that pushed to Gatus to request that URL, and add /fail to report a failed run at once. External endpoints with no heartbeat interval have nothing to alert on, so they are listed for you to set up with the interval you want.

Checks run from four regions on Free, eight on Pro, all ten on Business, all on the same run, so a failure in one place shows as one region rather than as your whole service being down. That also means an endpoint on a private or LAN address cannot be reached, and the importer refuses it and names it. Keep Gatus for the inside of your network, or install the server agent, which reports outward and needs no open port.