Creating Your First Application
Applications help you organize services into logical groups that represent your products or systems.
Step 1: Navigate to Applications
- Sign in to app.alert24.net
- Click Applications in the navigation bar
- Click Create Application
[Screenshot: Applications page]
Step 2: Configure the Application
Fill in the application details:
- Name — A clear, descriptive name (e.g., "Customer Portal", "Payment System")
- Description — Optional context about what this application represents
Click Create to save.
Step 3: Add Services
After creating the application, add the services it depends on:
- Open the application you just created
- Click Add Service
- Choose from two tabs:
- Link Existing — Select services that already exist in your organization
- Create New — Create a new service and optionally set up a monitoring check at the same time
When creating a new service inline, you can also configure an initial monitoring check:
- Status Page — Select a cloud provider (e.g., Cloudflare, AWS) and the specific service you depend on
- HTTP / HTTPS — Enter a URL to monitor
The monitoring check is automatically linked to the new service with status sync enabled.
[Screenshot: Adding services to an application]
Managing Application Services
Adding Services
You can add services to an application at any time:
- From the application detail page, click Add Service
- Choose the Link Existing tab to add existing services, or Create New to create and link a service in one step
Removing Services
To remove a service from an application:
- Open the application
- Find the service you want to remove
- Click the remove or unlink option
Removing a service from an application does not delete the service itself. It only removes the association.
Viewing Application Health
The application detail page shows:
- Overall status — Derived from the status of all services within the application
- Service list — Each service with its current status
- Recent incidents — Any active or recent incidents affecting the application's services
Best Practices
Name applications after products, not infrastructure
Use names like "Customer Portal" or "Billing System" rather than "US-East Cluster" or "Production Servers." Product-oriented names help everyone — including non-technical stakeholders — understand what's affected.
Keep applications focused
An application should represent one coherent product or system. If an application has 20+ services, consider splitting it into smaller, more focused applications.
Include third-party dependencies
If your application depends on Cloudflare CDN, Stripe payments, or AWS S3, include those as services in the application. This gives you a complete picture of dependencies and makes it easier to trace the cause when something goes wrong.
Review regularly
As your infrastructure evolves, review your applications quarterly. Remove services that are no longer relevant and add new ones.