Support is provided 24x7x365 worldwide for subscribers. You can contact Percona engineers via telephone, instant messaging, email, and our Customer Portal depending on your support tier. See contacting support for ways to open a support incident.
Percona prioritizes support requests based on incident priority to ensure that customers experiencing severe production outages are restored to service as soon as possible. Real-time contact methods such as telephone and instant messaging should be reserved for critical situations that demand and directly benefit from immediate feedback.
At Percona, we understand that one size does not fit all. You may request changes to how or what we support to meet your unique needs. While we cannot accommodate every request, we will engage in an exploratory process with you to identify and document any such requests, and agree on the specific changes and any corresponding change in cost. This ensures that customization is well-documented both for you and for our delivery teams so nothing is lost in translation.
Customers with Managed Services are provided proactive, around-the-clock management of their database(s) that includes deep enterprise-grade expertise across a variety of database environments.
For each Environment for which you intend to receive support, Percona requires that you include all production database servers that store data related to this application (Percona XtraDB Clusters and MongoDB clusters that use an arbiter node that doesn’t hold data do not need to be included for pricing considerations, but will be supported). This allows us to assist you with covered support requests before those issues cause production outages, and protects you by ensuring every server related to your business-critical applications receives timely responses to support requests.
If the application you wish to cover makes use of a complex configuration, such as multiple region Disaster Recovery (DR) or database clustering, we require that all servers that underpin that application be included in your support subscription. As an example, if you had a source-source cluster with a replica for performing backups and an identical environment in another region for DR, you would need to include all six servers in your support subscription to guarantee that Percona can provide support for any database issues that could arise. For customers with complex configurations or a large or dynamic overall server count, there are options that will meet your needs.
In addition to the above, Percona recommends that any servers that are used to provide testing, development, or staging environments for your organization related to the covered applications also be included. Covering these non-production servers allows us to help you stage and test database software upgrades or hot fixes, replicate issues outside of your production environment and gather and analyze query metrics before potentially problematic changes go into your production environment. These servers are typically priced at a lower cost than production servers. Please be aware that Percona can only provide assistance with servers that are covered as part of your subscription agreement. Percona may request a server inventory list be completed during the initial contracting phase, at renewal of the contract, and anytime throughout the support term to ensure compliance.
“Environment” means the Supported Software configured in a consistent manner across servers when running on the O.S. and Covered Servers in support of one or more applications. Customer shall ensure that the Environment meets Percona’s minimum requirements. Partitioned Environments or complex replication architectures in which databases serve distinct roles require that all servers be covered for any of the servers to be covered under contract. To be considered a single Environment, at minimum a collection of servers must be running a supported version or versions of software, on a supported platform, and leveraging supported software for its given level of Subscription.
In practice, what this means is that a collection of servers must be similar enough to be considered fundamentally the same. If a collection of servers are all running in production, have similar architectures, run the same major versions of software, etc., then we can consider them all fundamentally the same. Minor differences in configuration will not necessitate splitting these out into separate environments. However, if you have some servers that support an application that is higher priority and requires more stringent SLAs, leverages different technologies to perform given functions than others in your environment (like replication technologies), or that is on a completely different version than the rest, then this environment would be considered separate from the others. Any pricing differences would be limited to this specific environment, while you still benefit from volume discounts based on the entirety of your subscription.
In a nutshell, we will fix covered software that is not working correctly, and coach you in specific tasks with which you require help. More specifically, we provide:
Further information about Percona spheres of support and Percona services lifecycle policy is here.
Some common topics for which customers use Percona Support include:
The following types of incidents are excluded for Support customers:
Percona Managed Services covers many of the same needs as Percona Support. However, since Managed Services are hands-on and much more tightly integrated as a part of your operational team, there are additional options available as a result. The key is how your organization plans to leverage Managed Services to support your team, whether primarily to support the day-to-day operations, to augment your capacity and capabilities to handle just your biggest problems or your most complex database projects (upgrades, migrations, etc.), or to be your database team handling everything while working with your application team(s). More specifically, we provide:
Query optimization and tuning is a key part of the healthy operation of any database solution. As a Managed Services customer, you will get a minimum of one Top Query review each year to assess your most commonly used queries and key suggestions for optimizing them. Premium Managed Services customers receive a quarterly Top Query Review in addition to an allotment of hours to tune your queries on a monthly basis.
The following types of incidents are excluded for Managed Services customers:
PRIORITY 1 (URGENT)
A problem that severely impacts your use of the software in a production environment (such as loss of production data or in which your production systems are not functioning). The situation halts your business operations and no procedural workaround exists.
PRIORITY 2 (HIGH)
A problem where the software is functioning, but your use in a production environment is severely reduced. The situation is causing a high impact to portions of your business operations and no procedural workaround exists.
PRIORITY 3 (MEDIUM)
A problem that involves partial, non-critical loss of use of the software in a production environment or development environment. For production environments, there is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround. For development environments, where the situation is causing your project to no longer continue or migrate into production.
PRIORITY 4 (LOW)
A general usage question, reporting of a documentation error, or recommendation for a future product enhancement or modification. For production environments, there is low-to-no impact on your business or the performance or functionality of your system. The potential for future issues cannot be used to justify an increase in priority unless there is proof from prior incidents and the request is clearly backed with supporting data. For development environments, there is a medium-to-low impact on your business, but your business continues to function, including by using a procedural workaround.
Response time commitments for each priority differ based on your subscription level.
[1]Proactive deliverables apply only to Managed Services subscriptions. Proactive Deliverables are a series of reports intended to assess the healthy operation of the database environment in order to make recommendations for improvement. These include a Performance Review, Business Continuity Review, and Top Query Review. They are yearly for Advanced Subscribers, or quarterly for Premium Subscribers.Phone support does not apply to Managed Services subscriptionsOptional Technical Account Manager applies only to Support subscriptions
| Advanced | Premium | |
|---|---|---|
| Initial P1 | 30 Minutes | 15 Minutes |
| Initial P2 | 90 Minutes | 60 Minutes |
| Initial P3 | 8 Business Hours | 4 Hours |
| Initial P4 | 16 Business Hours | 24 Hours |
| Ongoing P1 | 1 Hour | |
| Ongoing P2 | 4 Hours |
| Priority Level | Priority Level Description | Resolution Time Goal* |
|---|---|---|
| Priority Level 1 (Urgent) | An incident that severely impacts or halts customer’s use of the Supported Software in a production environment (such as loss of production data or in which customer’s production systems are not functioning) and no procedural workaround exists. | <= 24 hours |
| Priority Level 2 (High) | An incident where the Supported Software is functioning, but customer’s use in a production environment is severely reduced. The situation is causing a high impact to portions of customer’s business operations and no procedural workaround exists | <= 48 hours |
| Priority Level 3 (Medium) | An incident that involves partial, non-critical loss of use of the Supported Software in a production environment or development environment. For production environments, there is a medium-to-low impact on customer’s business, but customer’s business continues to function, including by using a procedural workaround. For development environments, where the situation is causing the customer’s project to no longer continue or migrate into production. | N/A |
| Priority Level 4 (Low) | A general usage question, reporting of a documentation error, or recommendation for a future product enhancement or modification. For production environments, there is low-to-no impact on the customer’s business or the performance or functionality of the customer’s system. For development environments, there is a medium-to-low impact on customer’s business, but customer’s business continues to function, including by using a procedural workaround | N/A |
Resolution is defined as restoration of service**. Root cause analysis and any resulting bug fixes or hotfixes will be a secondary item and are not governed by the same resolution goal. Resolution times are only included for Premium subscribers.
Unless otherwise agreed to in an executed Statement of Work, the following exceptions apply to Resolution time calculations:
*To the extent the information herein is inconsistent with an applicable statement of work, the terms and conditions of the statement of work shall control.
**For Managed Services customers only. For the Percona Support service, it is at the point that recommendations to restore service are provided, based on our analysis of all required logs and information. As Support does not have access to your environment and therefore cannot apply fixes themselves, it will be up to the customer to actually restore services based on our recommended steps.
Percona will fix bugs within Percona software subject to the Percona Software and Platform Lifecycle.
When requested, Percona will investigate possible bugs, for example ones that cause crashing, freezing, incorrect results, data corruption, performance problems, or security breaches. Bugs must be verified via repeatable test cases.
Percona engineers can work together with you to create test cases. Collaboration with you is key for us to be able to verify and fix any bug that we are working on. We will work with you to collect analytics data and test potential workarounds.
With any issue reported to us, our number one goal is to restore service. When it comes to handling bugs, the quickest way to restore service and prevent downtime is often to provide a workaround (for example changing settings, changing sql, starting with special flags, etc.).
Fixing a bug is a complex and often time-consuming process. Sometimes it is not possible or feasible to fix a particular bug, but we will apply our best effort in good faith. If no fix is possible, we will seek a workaround instead.
Percona may merge bug fixes from newer versions to older versions of the software, or undo fixes that were added in newer versions if appropriate and technically feasible.
For Percona software, once we are able to repeat a bug and the development work is completed, a bug fix will be included in the next released version of the software and you will need to upgrade after the release to receive the fix.
Customers with a Premium level subscription who request a hot-fix are entitled to a hot-fix build of the current version of Percona software with the fix applied as soon as development has completed the fix. This gives you access to critical bugs as soon as possible. Note, you will not need to upgrade server versions to receive the fix.
We are unable to guarantee that bug fixes will be incorporated into other flavors of the software, but bug fixes will always be contributed upstream to Oracle®, MongoDB, and the PostgreSQL community to adopt freely if they so choose.
Bug fixes will be included in the next scheduled release that is open for code changes. This may not be the immediate next release because it may already be frozen or being built.
Premium level subscriptions include hot fixes. Hot-fixes are available more quickly, as they are created specifically to address the identified issue(s), and are based on the version you are currently running. This lets you keep using exactly the same version plus fixes to customer-reported bugs. Hot-fixes are created to get you a resolution as quickly as possible, and therefore go through an accelerated release process.
We report bugs upstream wherever possible and work to leverage our relationship with the open source community, partners, and other vendors to find solutions for our customers. All bug fixes created by Percona are made available at no charge to the open source community and upstream vendors such as Oracle, MariaDB, MongoDB, and PostgreSQL so that the fixes may be incorporated into their versions of the software. However, the decision when or whether to incorporate those fixes is beyond Percona’s control.
