Next steps

Congratulations - you’ve completed the Your first 10 minutes with xrelia guide. Your first service is now being monitored, health checks are running, and incident notifications are configured.

The next step is to build a more complete monitoring setup and understand how xrelia models your systems.

Understand the core concepts

Before adding more services, take a few minutes to learn the concepts that power xrelia.

Start with:

Platforms - production, staging, preview, and development environments.
Services and service instances - how applications are organized and monitored.
Health checks and synthetic requests - the difference between availability checks and user journey monitoring.
Dependencies - how xrelia maps relationships between services.
Incidents and confidence - how monitoring results are combined into a single operational view.

These concepts will help you design a monitoring structure that scales as your infrastructure grows.

Expand your monitoring

Once you’re comfortable with the basics, add more monitoring coverage.

Recommended next steps:

Configure additional health checks for critical endpoints.
Add synthetic requests to monitor login flows, checkout flows, APIs, or other user-critical journeys.
Map service dependencies so incidents can be correlated across your architecture.
Configure notification channels for your team and define severity thresholds.

Explore analytics

xrelia provides analytics at the service, instance, and platform levels.

Review:

Availability trends
Response time percentiles
Confidence history
Incident timelines
Platform health

These views help you understand not just whether a service is down, but how reliability changes over time.

Manage changes

Monitoring is most useful when it is connected to deployments and configuration changes.

Learn how to:

Record deployments
Track configuration changes
Correlate incidents with recent changes
Identify regressions after releases

Build a production setup

For a production environment, we recommend monitoring every critical service with multiple health checks, synthetic requests for key user journeys, dependency mapping, and notifications routed to the appropriate teams.

A typical setup includes:

One service for each application or infrastructure component
Multiple instances across regions or availability zones
HTTP health checks for availability
Synthetic requests for user-facing functionality
Email and push notifications with severity-based routing

Continue with the documentation

A good path through the documentation is:

By the end of these sections, you’ll have a monitoring setup that not only detects outages, but helps you understand impact, identify root causes, and track reliability over time.