Reltio Platform Status Page

The Reltio Platform Status page is a publically-available page. You can access the page without being logged in to the Reltio platform or without having a Reltio account.

Overview of Reltio Platform Status Page

The Reltio Platform Status page is owned and handled by the Reltio Site Reliability Engineer (SRE) and Network Operations Center (NOC) teams. Each service in each cloud of the platform has several levels of monitoring, such as cloud level, infrastructure components, platform service components, performance check, and health check. Each layer of each service has a set of automated alerts. The SRE and NOC teams monitor these alerts 24/7 and respond via an on-call process established in a follow-the-sun manner.

If there is an incident, an alert or notification is published and triaged. If the incident cannot be resolved in an automated manner, it is investigated and resolved by the appropriate team.

The NOC will regularly and frequently update the incident report log of an ongoing incident until it is resolved. After the incident is detected, a Root Cause Analysis (RCA) is published to drive the uncovered root cause as well as the related issues to completion.

Using the Reltio Platform Status page, you can view:
  • The overall current status of all Reltio environments in all clouds. Some examples are mentioned in the Monitor Clouds section.
  • A history of the daily status of each environment.
  • A history of the daily status of global services such as an authentication server.
  • A historical daily log of all past incidents.
  • A detailed current and daily status of various services inside each cloud. For example: UI, API.
  • The details of each incident, including the current status and timeline provided for remediating and resolving the incident.
  • The uptime percentage of each cloud for the last 90 days.
  • The monthly uptime details.
You can also subscribe to the status and incident updates using:
  • Email: Provide an email address and click SUBSCRIBE VIA EMAIL to receive the updates.
  • Phone: Provide a country code and telephone number and click SUBSCRIBE VIA TEXT MESSAGE to receive the updates.
  • Slack: Click SUBSCRIBE VIA SLACK to receive the updates.
  • Webhook URL: Provide the webhook URL and email address to receive notifications if the API fails, and click SUBSCRIBE.
  • Atom or Really Simple Syndication (RSS) web feeds: Click the required link depending on the XML format you want to view.
Note: The Reltio Platform Status page is based on the Atlassian statuspage.io service and is therefore completely decoupled from Reltio’s infrastructure. For more information, see Statuspage resources.

Status Alert Subscription

The Reltio Platform Status page provides you with the overall current operational status of all systems in all clouds. A green bar along with the text - All System Operational indicates that there are no ongoing incidents in any of the clouds.

Notification Subscription

You can use the Subscribe To Updates button to subscribe to automated alerts. When you click the button, different icons appear. You can click the icon to see the type of notification it provides. You can also click on the support site link in the support icon to view the Reltio support site and create a support ticket, if required.

After you complete your subscription, a notification is sent if there is an incident in any of the clouds. You will continue to receive further notifications about the open incident until it is resolved.

A sample subscription confirmation email is displayed:

The email indicates that you can manage notifications for various component using the email subscription for alerts or updates. The Subscription Management View is displayed after clicking the Manage your subscription button.

Manage Subscriptions

Using the Components list, you can select the cloud name and related service for which you want to monitor and receive alerts.
Note: Make sure that you click Save after selecting the required items.

You can always change the configuration of your subscription using the same button available in the email. Make sure that you save your changes after changing the configuration.

Cloud Services

You can monitor the health of the following cloud services. The criticality of all services are critical or high except the Activity Log and Matching Service, for which the criticality is medium. When the core functionality of a critical service is down, we must take corrective actions immediately. If the criticality of a service is medium, the core functionality of the service still works, but we must take corrective actions as soon as possible.
  • UI: This service monitors the health status of the Console and Hub, and affects all cloud customers. The platform services that can lead to failure are:
    • Cloud Infrastructure
    • UI-dedicated Infrastructure
    • Authentication service
  • API: This service monitors the health status of the Reltio platform APIs, and affects all customers in all clouds or in certain clouds. The platform services that can lead to failure are:
    • Cloud Infrastructure dedicated to APIs
    • Authentication service
  • Data load: This service monitors the health status of the Data Loader overview, and affects specific customers. The platform service that can lead to failure is the cloud infrastructure.
  • Data Storage: This service monitors the health status of the primary and secondary data storage for all tenants. The platform services that can lead to failure are:
    • Primary data storage
    • Secondary data storages
  • Export: This service monitors the health status of the data export service. The platform services that can lead to failure are:
    • Elastic Search for Search/Export
    • Jobs Cluster
    • CRUD Queue
    • Primary data storage
    Note: This service is critical only to specific customers.
  • Search: This service monitors the health status of Elasticsearch. If this feature does not work, it could impact the smooth functioning of the UI. The platform services that can lead to failure are:
    • Elastic Search for Search/Export
    • CRUD Queue
    • Primary Storage
  • Queues: This service monitors the health status of the streaming queues. The platform services that can lead to failure are:
    • CRUD Queue
    • Match Queue
  • Activity Log: This service monitors the health status of the Activity Log. The platform services that can lead to failure are:
    • Elastic Search for Activity Log
    • CRUD Queue
    • Activity Log storage
    Note: This service is critical only to specific customers.
  • Matching Service: This service monitors the health status of the match service. The platform services that can lead to failure are:
    • Primary data storage
    • Secondary data storages
    • Authentication service

Monitor Clouds

After you select the clouds that you want to monitor, you must monitor their status regularly. One way is to find the cloud on the Status Monitoring page. When you log in to your tenant using a web browser, the URL you see will be in the following format:
environmentName.reltio.com/ui/tenantName

For example: 361.reltio.com/ui/mytenantID.

The About This Site section of the Status Monitoring page contains mappings of the environment to the cloud name. Using the mappings, you can find the cloud that you need to monitor. Once you do this, you can select a specific set of services in this cloud to receive alerts.
Note: While selecting the services to monitor:
  • Make sure that the URL always starts with your environment name.
  • Reltio recommends that you keep all services selected.

The status of the followings items are displayed on the Reltio Platform Status page:
  1. The bar at the top shows the overall operational status of the platform for all clouds and services. If the bar is green and the All Systems Operational text is displayed, then there are no issues in any of the services of the clouds.
  2. The current status of a specific cloud.

    If you see a green bar, then all services or components are functional. If you see an orange bar, hover over the bar to see how many services or components are affected:

    If you want to see the specific components that are affected, click the banner next to the cloud name:

    You can now hover over the orange bar to see the details of the issue:

  3. The overall cloud status on any particular day in the timeline. A yellow or red color (any color except green) implies that there was at least one service issue that day, and the specific color (red, yellow, or green) shows the severity of the service degradation.
  4. The View historical uptime link button opens the historical uptime view, which shows a monthly view of a full history of incidents in the Incidents tab, and the uptime status in the Uptime tab.

You can also look for the cloud using cloud name tips. The overall uptime for each cloud is displayed as a percentage value.

Historical Uptime View

This view shows the daily uptime status with the same severity color coding as mentioned earlier. You can view the status for a specified 3-month time period.

You can see the details for a specific day by hovering over the day.

The Incidents tab shows a monthly timeline with details of each incident that happened in a particular month. You can filter this view for each component using the Filter Components drop-down menu. For example, you can select the Global Cleanse check box to view all incidents related to cleanse.

You can view the details of an incident using the Incident Detail View by drilling down to a specific day to view the incident details for that day, like the resolution status, technical details of the investigation details, timeline of the incident, and list of impacted clouds.

The Current Status link takes you back to the Reltio Platform Status page.

An example of the Incident Detail View is displayed: