New Survey: Leveraging real-time data delivers higher revenue growth and increased developer productivity. Learn more.
DataStax Managed Cloud Support Policy
Last Updated Date:
- Supported Software
- Technical Contacts
- Informational Support
- Technical Currency
- Issue Resolution
- Service Levels
- Customer Responsibilities
- How to Escalate a Support Issue
- End of Life Policy
- Support of Customers of Resellers
DataStax provides Support on DataStax Managed Cloud subscriptions under the terms of this DataStax Managed Cloud Support Policy as long as Customer maintains a current subscription to DataStax Managed Cloud, which includes the services described in this DataStax Managed Cloud Support Policy and does not include one-time services or other services not specified in this DataStax Managed Cloud Support Policy, such as training, consulting or custom development. This DataStax Managed Cloud Support Policy is part of and subject to an agreement with DataStax (the “Agreement”) that includes (unless Customer has executed a separate agreement with DataStax) the DataStax Managed Cloud Terms (at www.datastax.com/dmc-terms) and the Order Schedule under which Customer purchased its Subscription to DataStax Managed Cloud.
1. Supported Software
Support covers only the software and services delivered to Customer through the DataStax Managed Cloud under the Agreement (the “Supported Software”). The Supported Software includes the open source software and other third party components delivered to Customer by DataStax. Similar third party components might be available from other sources, but Support covers only the software delivered to Customer by DataStax.
2. Technical Contacts
Support may be initiated and managed only by Customer’s Technical Contacts. “Technical Contacts” are named individuals who are responsible for technical engagement with the DMC operational team within Customer’s organization. Customer may designate the number of Technical Contacts that corresponds with its licensed volume in Table 1 below. Additional Technical Contacts may be available for an additional fee.
|# Nodes||# Technical Contacts|
3. Informational Support
DataStax will provide reasonable product and technical support to address questions concerning use of the Supported Software. In addition to providing access to software, DataStax Managed Cloud is also a managed service that is governed by the terms of a Service Level Agreement. Technical Contacts may initiate Support by submitting a ticket through our 24-hour web ticketing system in the management console at https://cloud.datastax.comor at the DataStax Managed Cloud Support site at https://dmc.datastax.com. Support is provided in the English language only.
4. Technical Currency
As part of Support, and at no additional license fee, DataStax will provide Customer with all new versions of the Supported Software that it generally releases, including all improvements, enhancements and bug fixes. All such new versions are provided subject to the terms of the Agreement. The DataStax Managed Cloud team will upgrade Customer clusters to provide access to new versions of Supported Software. Support does not include any item that DataStax licenses separately from the Software or that DataStax makes available for an additional fee.
5. Issue Resolution
DataStax will make commercially reasonable efforts to resolve any Issues submitted by Customer’s Technical Contacts. Such efforts may include helping with diagnosis, suggesting workarounds, providing patches, or making a change to the Supported Software in a new release. An “Issue” is a material and verifiable failure of the Supported Software to conform to its Documentation. Support will not be provided for the following: (1) use of the Supported Software in a manner inconsistent with the applicable Documentation, (2) modifications to the Supported Software not provided by or approved in writing by DataStax, (3) modifications to the cloud environment provided by DataStax, or (4) use of the Supported Software with products or software not provided or approved in writing by DataStax. Customer shall not submit Issues arising from any software other than the Supported Software or otherwise use Support for unsupported software.
6. Service Levels
When a Technical Contact submits an Issue, DataStax will reasonably assess its priority according to the appropriate priority levels defined below. DataStax will confirm the priority level with Customer and will resolve any disagreement regarding the priority as soon as is reasonably practical. Urgent and High priority levels are not available for non-production systems.
|Normal/Low||24 hours M-F, excluding holidays|
“Urgent” means a catastrophic problem in Customer’s production systems. Examples include a complete loss of service, production systems that are crashed, or a production system that hangs indefinitely. Customer cannot continue essential operations.
“High” means a high-impact problem in Customer’s production systems. Essential operations are seriously disrupted, but a workaround exists which allows for continued essential operations.
“Normal” means a lower impact problem on a production or non-production system that involves a partial or limited loss of non-critical functionality, or some other problem involving no loss in functionality. Customer can continue essential operations. Normal problems also include all problems on non-production systems, such as test and development systems.
“Low” means a general usage question. It also includes recommendations for requests for new products or features, and requests for enhancements or modifications. There is no impact on the quality, performance, or functionality of the product in a production or non-production system.
7. Customer Responsibilities
Customer shall provide DataStax with credentials to access the cloud environment where the deployment will reside. Customer will provide access to Customer’s Technical Contacts as reasonably required to allow DataStax to resolve reported Issues. Customer is responsible for the adequate duplication and documentation of all of its files and data for backup purposes. Backups are an included function of the DataStax Managed Cloud service.
8. How to Escalate a Support Issue
DataStax Managed Cloud is committed to providing accurate and timely solutions to technical support needs. Customer may use the following escalation path to have your concerns addressed:
- Verify that the support ticket is up-to-date and all requested information and files have been provided.
- Contact Support via the hotline number, which can be found on the ‘Contact Us -> Hotline Number ’ linkonce logged into the Datastax Managed Cloud Support Portal. (You will receive access to the Support portal upon processing of your contract.) Caller will be asked for your name, company name, ticket number, contact number, and reason for the call. If a DataStax Managed Cloud engineer is not available, an operator will take the information and generate an urgent support request and issue an alert
9. End of Life Policy
Support covers the following Software: (1) the current Major Release and one prior Major Releases; and (2) each Major Release for at least 18 months after its general release; and (3) all Minor Releases under a supported Major Release. If none of the conditions in the preceding sentence are met, then the Supported Software has reached its End of Life (“EOL”). “Major Release” means a new version of the Supported Software made generally available by DataStax with substantial improvements, enhancements and bug fixes, represented by a change in the number to the left or right of the first decimal point (such as a version change from 1.1.0 to 2.1.0 or from 1.1.0 to 1.2.0). “Minor Release” means a version change represented by a change in the number to the right of the last decimal point. For example, if a Major Release were made available on January 1, 2000, then it would be supported until June 30, 2001, even if 7 Major Releases are made available in that period. Similarly, if only two Major Releases are made available over a three-year period, then both will be supported throughout that period.
The Supported Software will reach its End of Service Life (“EOSL”) 6 months after the EOL. Until the EOSL (and provided Customer has a current Subscription to Support), if Customer has identified a defect in a Major Release that has reached EOL, DataStax will evaluate fixing the defect in a release that has not reached EOL. After the EOSL, DataStax will not support, in any way, a Major Release and/or any Minor Releases of that Major Release. DataStax will make every effort to ensure that managed clusters are upgraded prior to EOSL, but in the unlikely event that a Customer cluster remains on a version that has reached EOSL, the cluster will no longer be bound by the DataStax Managed Cloud SLA or be managed by DataStax staff.
Support for other versions of the Supported Software is not provided under this DataStax Managed Cloud Support Policy. Support does not cover use of the Supported Software on platforms or operating systems that are no longer supported by the original vendor. A list of current versions of the Supported Software is available at: www.datastax.com/support-policy/supported-software.
10. Support of Customers of Resellers
If Customer purchased its Subscription through a reseller, then please see the applicable agreement with that reseller for any applicable additional or different terms (for example, Customer’s first contact for support may be the reseller, rather than DataStax).
Except as expressly provided herein, no modification of this DataStax Managed Cloud Support Policy will be effective unless contained in writing and signed by an authorized representative of each party. From time to time, DataStax may amend this DataStax Managed Cloud Support Policy in its sole discretion. DataStax will post the amended terms on the DataStax website at www.datastax.com/dmc-support-policy. DataStax will also update the “Last Updated Date” at the top of this DataStax Managed Cloud Support Policy. By continuing to access or use Support after DataStax has provided Customer with such notice of a change, Customer is indicating that it agrees to be bound by the modified DataStax Managed Cloud Support Policy. If the changes have a material adverse impact on and are not acceptable to Customer, then Customer must notify DataStax within 30 days of the applicable Last Updated Date. If DataStax cannot accommodate Customer’s objection, then the prior DataStax Managed Cloud Support Policy shall govern until the expiration of the then-current subscription period. Any renewed subscription will be governed by the then-current DataStax Managed Cloud Support Policy. No term or condition contained in Customer’s purchase order or similar document will apply unless specifically agreed to by DataStax in writing, even if DataStax has accepted the order set forth in such purchase order, and all such terms or conditions are otherwise hereby expressly rejected by DataStax.