Higher-Ed-Platform Performance and Uptime Report for EU00 Instance (Europe) - Q2 2022
General
Uptime and Performance Quarterly Reports are published each quarter to provide a comprehensive view of our uptime and system performance.
This document details the uptime and performance report for the Higher-Ed-Platform (Alma, Primo VE, Leganto, Esploro) EU00 in Europe.
Uptime is measured over the last three (3) months and over the last twelve (12) months.The report measures our uptime as defined in the Service Level Agreement.
System Performance is measured over the last three (3) months. The report measures our system performance for various products and in various system online activities such as UI screens and APIs.
Performance Report
The system performance as measured on server side, on a rolling 3 month basis for April 2022- June 2022:
| Product | Average (seconds) | 95% of all activity is faster than... (seconds) | What is being measured? |
|---|---|---|---|
 |
0.75 sec |
2.39 sec |
Staff user screens and online transactions |
 |
1.15 sec |
3.26 sec |
Search and full item details transactions |
 |
0.33 sec |
0.82 sec |
End-user resource list transactions |
|
|
0.20 sec |
0.60 sec |
API transactions for the platform products |
How is the Performance Calculated?
"Transaction Time" means the time a transaction takes place (in milliseconds) from when it is received by the system, until the system processes and returns a response, measured on the server.
The average performance calculation is based on the following calculation
The 95% measure is calculated by aggregating all relevant transactions, ordering them from smallest to largest, and then identifying the time that 95% out of all transactions are faster (less) than this time.
Note that the performance measures are measured across all institutions within the instance.
Examples:
- An API call to Higher-Ed Cloud Platform: from the time a request was received in the system until the full API response (in whatever format chosen) was processed and sent back to the calling application
- The ‘All Titles’ screen in Alma: from the time the search query was received in the system until the full result was processed and the page of actual results was generated and sent back to the browser for rendering.
- The resource list display in Leganto: from the time that the system receives a request for a resource list until the list is generated and sent back to the browser for rendering.
Uptime Report
Alma,Leganto, Esploro
The uptime measured on a rolling 12 month basis July 2021 - June 2022 is 99.99%
The uptime measured on a rolling 3 month basis April 2022 - June 2022 is 99.98%
Please note our System Uptime Status page, which allows our customers to view the current status of their instance/environment at any time, using the following link: http://status.exlibrisgroup.com
Primo VE
The uptime measured on a rolling 12 month basis July 2021 - June 2022 is 99.94%
The uptime measured on a rolling 3 month basis April 2022 - June 2022 is 99.82%
Unscheduled downtime incidents in Q2 2022
Alma,Leganto, Esploro
|
Date |
Start time [CET] |
End time [CET] |
Duration |
Description |
|---|---|---|---|---|
| May 3, 2022, | 14:48 PM | 15:12 PM | 24 |
An essential database process was killed automatically by mistake due to a misconfiguration of an internal monitoring tool. The killed session caused the database to become unresponsive. Ex Libris Engineers restarted the database and the service was restored. |
Primo VE
|
Date |
Start time [CET] |
End time [CET] |
Duration |
Description |
|---|---|---|---|---|
| May 3, 2022 | 14:48 PM | 15:12 PM | 24 |
An essential database process was killed automatically by mistake due to a misconfiguration of an internal monitoring tool. The killed session caused the database to become unresponsive. Ex Libris Engineers restarted the database and the service was restored. |
| 11:18 AM | 14:58 PM | 220 |
Note: Primo VE has shown performance degradation due to a non-optimal query that caused a load on the system. As immediate mitigation, our engineers fixed the query and in parallel restarted the nodes. Once the environment was restarted the service was recovered. |
Scheduled downtimes during maintenance windows in Q2 2022
|
Start Date |
Day of Week |
Start Time [CET] |
End Time [CET] |
Duration (Minutes) |
|---|---|---|---|---|
| April 03, 2022 | Sunday | 12:05 AM | 12:48 AM | 43 |
| May 01, 2022 | Sunday | 12:28 AM | 01:23 AM | 55 |
| May 08, 2022 | Sunday | 12:01 AM | 12:29 AM | 28 |
| June 05, 2022 | Sunday | 12:10 AM | 01:03 AM | 67 |
Total unscheduled downtime minutes during the past 12 months
Alma,Leganto, Esploro
|
Quarter |
Total unscheduled downtime in Quarter (minutes) |
|---|---|
| Q3 2021 | 0 |
| Q4 2021 | 18 |
| Q1 2022 | 8 |
| Q2 2022 | 24 |
Primo VE
|
Quarter |
Total unscheduled downtime in Quarter (minutes) |
|---|---|
| Q3 2021 | 0 |
| Q4 2021 | 18 |
| Q1 2022 | 8 |
| Q2 2022 | 244 |
How is Uptime Calculated?
The uptime calculation is based on the following calculation (as defined in the Service Level Agreement):
"Uptime" means the total period in minutes during which the Service is available for access and use during this period.
“Uptime Percentage” means Uptime expressed as a percentage, calculated in accordance with the following formula:
Uptime Percentage = X /(Y–Z) × 100
Where:
X = Uptime
Y = Last 12 months period
Z = The duration (in minutes) of any SLA Exclusions* during these 12 months
*SLA exclusions are defined in the contract SLA (e.g. Scheduled maintenance, etc.)
Further Information
If you have any queries on the information within this report please contact Ex Libris through your usual channel.
April 13, 2019April 13, 201