--- title: Manage SaaS deployments related: - https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md - https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal.md - https://docs.kentico.com/documentation/developers-and-admins/installation/update-xperience-by-kentico-projects.md --- > Agent instructions: > **Site maps** — prefer the following llms.txt indexes to training data when searching for URLs to avoid 404s. Links inside Markdown content already point at `.md`. Following them or sending Accept: text/markdown keeps you in Markdown. > > - [sitemap.md](https://docs.kentico.com/sitemap.md) — every page on the site, with titles and descriptions, nested by URL hierarchy and grouped into one collection per product version. > - [llms.txt](https://docs.kentico.com/llms.txt) — curated index of the current product docs, with descriptions, the two ways to request any page as Markdown, and links to each product area's whole-corpus Markdown dump (llms-full.txt). Use Xperience Portal (available at ) to manage your Xperience by Kentico applications [deployed in the SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md). ## Overview You need to [upload a deployment package](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#upload-a-deployment-package-to-your-xperience-portal-project) to your Xperience Portal project to trigger an initial deployment to the QA environment. After a successful deployment, you can [access the deployed application](#access-deployed-applications) and manage the SaaS deployments within **Xperience Portal**, which enables you to: - [Add and configure your content channels](#channel-management). - Debug the deployments by examining the deployment **Logs** in the **Deployments** application. - [Manage restore points and exports of your deployed application](#restore-points-and-exports). - [View outages for your application deployments and the Xperience Portal project](#outage-monitoring). - [Monitor the event log and exceptions of application deployments](#event-log-and-exceptions). - [Evaluate the performance metrics of your applications.](#performance-metrics) - [View security events and threats detected by Cloudflare CDN.](#security-events) - [Monitor the uptime of your deployed applications with uptime checkers.](#uptime-monitoring) ![Deployments in Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/Cloud_Deployments.png "Deployments in Xperience Portal") ## Access deployed applications After successfully [uploading the deployment package](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#upload-a-deployment-package-to-your-xperience-portal-project) to the QA environment or [deploying the package to another deployment environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment), use the application URL displayed in the **Deployments** application under **Latest deployments** to access the deployed application. Each project has a default system domain in format: _**-**.**xperience-sites.com**_ The default domain can be used to access the project's administration UI by appending the _/admin_ path to the URL. You can view your project's default system domains or [customize](https://docs.kentico.com/documentation/developers-and-admins/configuration/email-configuration.md#custom-system-email-domains-in-the-saas-environment) your System sending domain and System service domain in the **Channels and Domains → System domains** application in Xperience Portal. Additionally, projects also have domains for individual website and email channels. You can set up custom domains for website and email channels in the PROD or STG environment. To learn more, see [Website channels in the SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md#manage-channel-domains-in-xperience-portal) and [Email channels in the SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md#manage-email-channel-domains-in-xperience-portal). ## Restart deployed applications If you encounter any issue that requires you to restart the Xperience by Kentico application, you can [restart the application](https://docs.kentico.com/documentation/developers-and-admins/configuration/system-overview.md#restart-the-application) in the administration interface. However, when you cannot access the administration interface, you can restart the application from Xperience Portal. 1. [Access your Xperience Portal project](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal.md#xperienceportal-accessportal). 2. Navigate to the **Deployments** application. 3. **Restart** the desired environment. - For non-production environments (**QA**, **UAT**), the _Restart_ button is available to all portal users. However, only users in **Tenant Administrator** or **DevOps Engineer** [roles](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal/reference-xperience-portal-user-roles.md) can restart production environments (**PROD**, **STG**). 4. Wait until the restart is finished. ![Restart button in the Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/XP_restart_app.png "Restart button in the Xperience Portal") ## Channel management Content in Xperience by Kentico is encapsulated within channels, which are bound to specific domains. To allow the content to be presented by deployments in the SaaS environment, you need to add and configure all website and email channels within Xperience Portal in the **Channels and Domains** application. For detailed information, see: - [Website channels in the SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/configuration/website-channel-management.md#website-channels-in-the-saas-environment) - [Email channels in the SaaS environment](https://docs.kentico.com/documentation/developers-and-admins/digital-marketing-setup/email-channel-management.md#email-channels-in-the-saas-environment) - [GraphQL API endpoints](https://docs.kentico.com/documentation/developers-and-admins/configuration/headless-channel-management.md#graphql-api-endpoints) ## Restore points and exports The SaaS environment uses a two-tier system consisting of **restore points** and **exports** to ensure data protection and disaster recovery. This system allows you to restore previous versions of your project for a particular environment. Xperience Portal creates [automatic restore points and exports](#automatic-restore-points-and-exports), and you can also create [manual restore points](#create-a-manual-restore-point) and [manual exports](#create-a-manual-export) for production and non-production environments. Restore points and exports are managed in separate applications: - **Restore points** can be viewed, managed and [restored](#restore-from-a-restore-point) under **Data Management** → **Restore points** - **Exports** can be created and downloaded under **Data Management** → **Exports** The separate Restore points and Exports applications are available for projects with version **30.1.0 or higher** deployed across all environments. Projects with earlier versions continue to use the combined **Backups** application. > **Info:** Applications deployed in the SaaS environment consist of the following services: > > - **Application service** – application binaries and runtime files > - **Database** – reflects the current state of the environment's database > - **Storage** – reflects the current state of files in the environment's Azure Blob storage ### Restore points vs. exports Understanding the difference between restore points and exports is crucial for effective data management: **Restore points:** - A timestamp referencing the application state at a given time, allowing you to restore the application to that previous state - Fast to create as no physical data copying occurs - Always include restore points for all three services (application, database, and storage) - An Application service restore point is a snapshot of the deployment package. If nothing has been deployed yet, you can download the intial Application service files - Created automatically before deployments, manually on demand, or on a regular schedule - Cannot be used to download data (with the exception of _Weekly restore points_). To download data, you must create an export. **Exports:** - Physical copies of data that can be downloaded for inspection, debugging, or long-term storage - Slower to create (depends on the amount of data) as files are physically copied - Can be full (all components) or partial (selected components only) - Cannot be used to restore the application - Service components included in exports: - **Application service** – copy of all files from the application service file system - **Database** – exported as a `bacpac` file - **Storage** – copy of files from Azure Blob storage - Limited to **30 exports per component** per environment per month (may be adjusted with custom plans) - Exports that include the **Database** component can appear in the **Exports** application before the database export is fully finalized. In this state, database download remains unavailable until processing is complete. - Exported files are retained for **60 hours** after creation and must be downloaded before automatic removal ### Automatic restore points and exports Kentico automatically creates the following **restore points and exports**: - For all environments: - _Pre-deployment restore points_ which expire in 30 days. The system creates a restore point for each service to make deployments faster: - **Application service** – if nothing has been deployed yet, an export of the current application service file system is created instead - **Storage** – restore points are always created - **Database** – restore points are created only when all project environments have Xperience by Kentico version 30.1.0 or higher deployed and all existing backups are from 30.1.0 or higher - For the _Staging_ or _Production_ environment: - _Daily restore points_ with a retention policy based on your service plan: - _Level 1_ – 3 days - _Level 2_ – 3 days - _Custom_ – 7 days or more - Daily backups always use restore points only - Application service restore points are snapshots of the deployment package. If no deployment package has been deployed yet, the daily backup may contain a downloadable application service [export](#restore-points-vs.-exports) instead. > **Note:** **QA environment daily backups** > > All standard service plans (_Level 1_, _Level 2_) have QA daily backup retention set to 0 days, so the QA environment does not have any daily backups. Only _Custom_ service plans can configure QA daily backup retention. - _Weekly restore points_ (created on Sundays) with a retention policy of 30 days - Downloadable export data is included for all components, which allows you to download the data for long-term storage purposes while also providing fast restore point functionality - Weekly restore points are displayed only after related database export finalization is complete > **Info:** See [SaaS service plans](https://docs.kentico.com/documentation/developers-and-admins/saas/saas-service-plans.md) for information about service plans and [Licensing Xperience by Kentico SaaS](https://docs.kentico.com/documentation/developers-and-admins/installation/licenses.md#licensing-xperience-by-kentico-saas) for information how to change to a different service plan. ### Create a manual restore point You can create manual restore points for both production and non-production environments. The retention policy for manual restore points is: - _Restore points_: - _Level 1_ service plan – 3 days - _Level 2_ service plan – 3 days - _Custom_ service plan – 7 days or more To create a manual restore point: 1. Navigate to **Data Management** → **Restore points**. 2. Select **Create restore point** in the upper-right corner. 3. Select the environment for which you want to create a restore point. > **Info:** Only **Tenant administrator** and **DevOps** roles can access and create restore points for **Production** or **Staging** environments. See [Reference - Xperience Portal user roles](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal/reference-xperience-portal-user-roles.md). 4. Select **Create** and wait for the restore point to be created. > **Info:** SaaS processes (e.g., restore points, [deployments](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment)) are queued, and you can have only one process running at a time. Your restore point is now available in the **Restore points** application under **Data Management**. ### Create a manual export The export process creates physical copies of the data, which can then be downloaded. Exports are limited to 30 exports per component per environment per month (may be adjusted with custom plans). To create a manual export: 1. Navigate to **Data Management** → **Exports**. 2. Select **Create export** in the upper-right corner. 3. Select the environment for which you want to create an export. > **Info:** Only **Tenant administrator** and **DevOps** roles can access and create exports for **Production** or **Staging** environments. See [Reference - Xperience Portal user roles](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal/reference-xperience-portal-user-roles.md). 4. Select what components should be included in the export. 5. Select **Create** and wait for the export to be created. > **Info:** SaaS processes (e.g., restore points, [deployments](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment)) are queued, and you can have only one process running at a time. Downloading exports allows you to inspect the state of the application, debug the database or check the integrity, versions, and number of files in the deployment environment. > **Note:** **Contained users authentication** > > Enable [contained users authentication](https://learn.microsoft.com/en-us/sql/relational-databases/security/contained-database-users-making-your-database-portable?view=sql-server-ver17) on your local SQL Server to be able to use the exported database backups. ### Restore from a restore point You can restore your application to a previous state using restore points. This is useful if you need to revert changes or recover from an issue. > **Warning:** **Downtime during the restore** > > Restoring from a restore point causes **downtime** for the target environment. The application will be unavailable until the restore is complete. You can display a custom HTML page to inform visitors about the site's status during the restore. 1. Navigate to **Data Management** → **Restore points**. 2. Select an environment and select **Apply**. A list of restore points for the environment is displayed. 3. Restore from a restore point by selecting **Restore** () next to a restore point. 4. On the **Restore a restore point** page: - Select the exact restore point you wish to restore from. - Choose an HTML page displayed on the live site during the downtime caused by the restore. - You need to choose the HTML page each time you run a restore. The selected page is used only for that restore. - The [app offline page](https://docs.kentico.com/documentation/developers-and-admins/configuration/saas-configuration.md#define-a-custom-app-offline-file) configured for downtime during deployment is not used for restores. - If you do not select a page here, the system displays a default page with a generic offline message. - Select whether to restore immediately or schedule the restore for a later date. 5. Select **Restore** and wait for the restore process to complete. ## Application monitoring The **Monitoring** set of applications in the Xperience Portal are designed to keep your application running smoothly and provide full visibility into your application's performance, enabling you to quickly detect and resolve issues, optimize performance, and ensure the best possible user experience. - [Outage monitoring](#outage-monitoring) - [Event log and exceptions](#event-log-and-exceptions) - [Performance metrics](#performance-metrics) - [Security events](#security-events) - [Alerts and email notifications](#alerts) - [Uptime monitoring](#uptime-monitoring) ### Outage monitoring Use the **Outages** application under **Monitoring** in Xperience Portal to see a list of outages for your Xperience Portal project and deployed applications. Records include the time when the outage occurred and the cause of the outage. You can filter the outages by the month when they occurred. Use **Outage monitoring** to track platform or project outage incidents. For endpoint-level availability checks of your application URLs, see [Uptime monitoring](#uptime-monitoring). Go to [status.xperience-portal.com](https://status.xperience-portal.com/) to see the uptime statistics for Xperience Portal. See [Xperience Portal uptime statistics](#xperience-portal-uptime-statistics). ![Outages](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/Cloud_Outages.png "Outages") > **Info:** Your Xperience Portal project occasionally undergoes [scheduled maintenance](https://docs.kentico.com/documentation/developers-and-admins/saas/xperience-portal.md#schedule-maintenance-of-xperience-portal-projects), during which certain Xperience Portal features may become unavailable. #### Xperience Portal uptime statistics Go to [status.xperience-portal.com](https://status.xperience-portal.com/) to see the statistics about the availability of: - Xperience Portal - Deployment API - Production sites by region You can also see the list of **Past incidents** below the statistics. > **Info:** You can subscribe to the incident reporting to receive a message whenever Kentico creates, updates, or resolves an incident. Select **Subscribe to** **updates** at the top of the Xperience by Kentico status page. ### Event log and exceptions Xperience by Kentico integrates [Application Insights for ASP.NET Core applications](https://learn.microsoft.com/en-us/azure/azure-monitor/app/asp-net-core) to enable monitoring and aggregation of metrics for your website. For detailed information about enabling the Application Insights integration for your projects, see [Microsoft Application Insights integration](https://docs.kentico.com/documentation/developers-and-admins/configuration/saas-configuration.md#microsoft-application-insights-integration). To view the Application Insights logs for your deployments, use the following applications under **Monitoring** in Xperience Portal: - **Event log** – displays entries from the [Xperience event log](https://docs.kentico.com/documentation/developers-and-admins/configuration/event-log.md) and any custom messages sent via the Application Insights SDK. - **Exceptions** – displays all .NET exceptions (errors) from Application Insights. Includes exceptions that can occur before the Xperience application is fully running, in addition to errors in the Xperience event log. You can filter the logs for individual deployment environments, and based on the time when the event occurred. ![Exception data from Application Insights](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/XP_Monitoring_Exceptions.png "Exception data from Application Insights") > **Info:** **Log size limits** > > There is a **daily limit** on the size of the Application Insights logs. After the daily limit is reached, further logs are discarded. > > The following table lists the daily limits for all deployment environment types and service plans. > > | **Environment** | **Service plan** | **GB/Day** | > | --------------- | ----------------- | ---------- | > | QA | All | 1 | > | UAT | Custom | 2 | > | PROD and STG | Level 1 & Level 2 | 3 | > | PROD and STG | Custom | 6 | > > 1 GB can store approximately 125 000 average-sized exceptions or event log records. ### Performance metrics Use the **Project metrics** application under **Monitoring** to see various performance metrics related to applications deployed to the SaaS environment. The available metrics include server errors, response time, CPU usage and memory usage. By tracking these metrics, potential issues can be detected and addressed before they impact users, bottlenecks and areas for optimization can be identified, resource utilization can be better understood, and insights can be gained to make data-driven decisions to improve and optimize the application. To view performance metrics for various SaaS environments: 1. In [Xperience Portal](https://xperience-portal.com), navigate to **Monitoring → Project metrics**. 2. Select an **Environment** and a **Time period**, for which you want to display metrics. 3. **Apply** the changes. ### Email metrics Use the **Email metrics** application under **Monitoring** to see email sending statistics from the [SendGrid platform](https://docs.kentico.com/documentation/developers-and-admins/configuration/email-configuration.md#sendgrid-integration). The available statistics include total numbers of delivered, bounced, and deferred emails. You can also track the number of [unique clicks](https://www.twilio.com/docs/sendgrid/glossary/clicks) in emails. These metrics help identify deliverability issues, optimize campaigns, and improve user engagement to drive better marketing performance. To view email metrics for various email channels and [deployment environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment): 1. In [Xperience Portal](https://xperience-portal.com), navigate to **Monitoring → Email metrics**. 2. Select a **Channel**, **Environment** and a **Time period**, for which you want to display metrics. 3. **Apply** the changes. ![Email metrics in Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/XP_Monitoring_Emails.png "Email metrics in Xperience Portal") ### Security events Use the **Security events** application under **Monitoring** to view security events detected and handled by [Cloudflare CDN](https://docs.kentico.com/documentation/developers-and-admins/configuration/saas-configuration.md#cloudflare-cdn). The application provides an overview of security threats, including [DDoS attacks](https://en.wikipedia.org/wiki/Denial-of-service_attack), malicious requests, and other suspicious activities that Cloudflare automatically detects and mitigates. > **Info:** Security event data is available for the **last 28 days** only. Events older than 28 days are automatically removed and cannot be retrieved. Security events are categorized into the following action types: - **Block** – Requests blocked by Cloudflare's security rules - **Skip** – Requests that bypassed certain security checks - **Log** – Security events that were logged for monitoring purposes - **Managed challenge** – Requests that received an automated challenge to verify legitimacy To view security events for your project: 1. In [Xperience Portal](https://xperience-portal.com), navigate to **Monitoring → Security events**. 2. Use the available filters to narrow down the security events: - **Channel** – Filter by website channel - **Environment** – Select a [deployment environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment) (QA, UAT, PROD, STG) - **Actions** – Filter by action type (Block, Skip, Log, Managed challenge) - **From (UTC)** and **To (UTC)** – Specify the time range for events - **Limit** – Set the number of most recent events to retrieve from Cloudflare 3. **Apply filters** to view the filtered results. The **Security events overview** section displays the total count of security events in the selected time period, a breakdown by action type with color-coded indicators showing the number of events for each category, and a timeline chart visualizing security event trends over time, helping you identify patterns and potential attack periods. The **Security events** table displays filtered events based on your selected parameters. To view detailed information about a specific event, including Cloudflare's [Ray ID](https://developers.cloudflare.com/fundamentals/reference/cloudflare-ray-id/), description, HTTP request details, and response information, select the Information () icon in the **Details** column. ![Security events in Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/security-events.png "Security events in Xperience Portal") ### Alerts Alerts notify about potential problems with applications deployed to the SaaS environment. Most of the available alerts are based on [performance metrics,](#performance-metrics) such as application responses, server errors or CPU/memory/DTU utilization. The system currently provides the following types of alerts: | Alert type | Severity | Alert conditions | | ----------------------------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Application response | Error | An [uptime checker's](#uptime-monitoring) endpoint availability dropped below **50%** over the past **15 minutes**. Uptime checkers send requests every 5 minutes. | | CPU utilization greater than 80% | Error | The application's average CPU utilization over the past **30 minutes** was above 80%. | | Memory utilization greater than 90% | Error | The application's average memory utilization over the past **30 minutes** was above 90%. | | DTU utilization greater than 90% | Error | The application's average Database Transaction Unit (DTU) utilization over the past **30 minutes** was above 90%.
The DTU utilization metric is calculated as the ratio of used DTUs to the total DTUs available for your project's plan. | | DTU utilization greater than 70% | Warning | The application's average DTU utilization over the past **30 minutes** was above 70%.
The DTU utilization metric is calculated as the ratio of used DTUs to the total DTUs available for your project's plan. | | Failed requests (Server errors) | Error | More than 5% of web requests sent to the application over a **30 minute** interval resulted in a failed status, i.e. returned a 5xx [HTTP status code](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes). | | Failed deployment | Error | [Deployment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-with-a-deployment-package) of a package failed. | | Service scaling | Warning | A production environment was scaled out to the maximum number of allowed instances over the past **360 minutes**. Typically occurs due to auto-scaling under heavy load.
Only applies to projects with a custom service plan, which can allow scaling to 3 or more service instances. | | Cloudflare DDoS attack | Warning | An HTTP [DDoS](https://en.wikipedia.org/wiki/Denial-of-service_attack) attack has been detected on one of your domains. These attacks are automatically detected and mitigated by the [Cloudflare CDN](https://docs.kentico.com/documentation/developers-and-admins/configuration/saas-configuration.md#cloudflare-cdn). View detailed security event data in the [Security events](#security-events) application. | To view alerts for your project's deployments, navigate to **Monitoring → Alerts** in [Xperience Portal](https://xperience-portal.com). You can filter the alerts for individual deployment environments, based on the time when the alert was fired, and the alert severity. Alerts are displayed with the **Resolved** flag if the conditions that caused the alert to fire no longer apply. For example, a _CPU utilization_ alert will be resolved after the average utilization drops under the 80% threshold over 30 minutes. Select **Show active alerts only** in the filter if you wish to see only unresolved alerts. ![Alerts in Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/XP_Monitoring_Alerts.png "Alerts in Xperience Portal") #### Alert email notifications Whenever an [alert](#alerts) is fired, the system sends a notification email to all Xperience Portal users assigned to the related project. Individual users can adjust their preferences for receiving alert email notifications: 1. In [Xperience Portal](https://xperience-portal.com), expand the top-right user menu. 2. Select **Notifications**. 3. Customize for which alert types and severities you want to receive email notifications from each [deployment environment](https://docs.kentico.com/documentation/developers-and-admins/deployment/deploy-to-the-saas-environment.md#deploy-the-package-to-another-deployment-environment). - **Note**: The selected alert severity and alert type conditions are combined using an _AND_ statement. If you select _Critical_ alert severity and _CPU_ alert type, you will not receive any alerts of alert types other than _CPU_. For **Production** and **Staging** environments, it is recommended to enable all alert types and at least _Critical_ and _Error_ alert severity. 4. Select **Save changes**. ![Alert notification settings in Xperience Portal](https://docs.kentico.com/docsassets/documentation/manage-saas-deployments/XP_Alert_Notifications.png "Alert notification settings in Xperience Portal") ### Uptime monitoring Uptime monitoring enables you to proactively monitor the uptime of your deployed applications. Each uptime checker periodically sends a request to its configured endpoint. When availability drops below the expected threshold, the system fires an [alert](#alerts) and sends a notification email to all Xperience Portal users assigned to the project. Use **Uptime monitoring** to track endpoint availability using custom uptime checkers. For platform or project outage incidents, see [Outage monitoring](#outage-monitoring). #### Create an uptime checker 1. In [Xperience Portal](https://xperience-portal.com), navigate to **Monitoring → Uptime monitoring**. 2. Select **Add uptime checker**. 3. Configure the following settings: - **Name** – Enter a name (3–50 characters) for the uptime checker using lowercase letters, digits, and hyphens. Hyphens can be used as word separators but cannot be the leading or trailing character. Uptime checker names appear in alert notification emails, so use a descriptive name that helps your team identify which endpoint has failed. - **Environment** – Select the deployment environment to monitor (QA, UAT, PROD, STG). - **Domain** – Select the domain of your deployed application to monitor. - **Checked path** – Enter the path to monitor (for example, `/admin/logon`). The path starts with `/` and can be up to 100 characters. Each domain and path combination must be unique; you cannot create multiple uptime checkers for the same domain and path. - **HTTP method** – Select the HTTP method for the uptime check request. - **Expected status code** – Enter the HTTP status code that indicates a successful response (for example, _200_). - **Timeout** – Set the maximum time (in seconds) to wait for a response. If the endpoint does not respond within this time, the uptime check is considered failed. 4. Select **Test connection** to send a test request and verify that the uptime checker can reach the endpoint with the current configuration. This helps you identify configuration issues before saving. 5. Select **Create** to save the uptime checker. #### Manage uptime checkers Navigate to **Monitoring → Uptime monitoring** to view existing uptime checkers. Use the **Environment** filter to display checkers for a specific deployment environment. To remove an uptime checker, select **Delete** () in the **Actions** column.