This is what we do in the Support and Maintenance phase:
the customer about the Managed
|Handle issues in the system.|
|4||Manage deployment artifacts.|
|upgrades and migrations.|
|6||Apply WSO2 security patches.|
Send weekly status updates
WSO2 sends weekly status update emails to you the customer with the following information:
- Summary A summary of the hosting-related JIRAs raised for the Managed CloudService.
- Summary A summary of the maintenance tasks done during the current week.
- Summary A summary of the maintenance work scheduled for the next week, including any scheduled downtimes.
Provide around-the-clock support and maintenance
According to the WSO2 Managed Cloud SLA, WSO2 carries out the following support and maintenance tasks:
|Ensures the availability of the WSO2 servers and services deployed as part of the Managed Cloud.|
|Monitors the Managed Cloud and takes action if any servers become unavailable.|
Configures the hosting setup for optimum resource consumption and scales hardware to meet performance thresholds.
|Updates software that is identified as part of the Managed Cloud to their latest versions.|
|Takes daily scheduled backups of all the servers under the Managed Cloud service.|
Handle issues in the system
If an unplanned interruption that affects the availability, quality, or performance of the services managed by the WSO2 Managed Cloud teamService team occurs, we call it a hosting incident. A hosting incident might occur in deployment, upgrade, maintenance, network configuration, startup, stopping, monitoring, and performance, and it has to be within the scope of the Managed CloudService's deployment architecture.
The diagram below shows how WSO2 handles a hosting incident from its initiation to closure:
Diagram: WSO2 incident-handling process
How to report a hosting incident
Note that you need the customer needs to either raise a support JIRA through the support Website or call the phone support numbers to report a hosting incident. The steps below explain how to use the support Website.
As you need to be a WSO2 production support customer to receive WSO2 Managed
services, we assume you already have a support account in the WSO2 support system. If not, please talk to your
account's manager at WSO2.
The steps below explain how to use the support Website to raise a hosting incident.
Log in to the support system at https://support.wso2.com.
- Click the Create button in the top menu bar of the support Website.
Select your project from the list ofprojects available to you.
Select the issue type. Here's an explanation about when to use what:
- Queries: A question that you have on the WSO2 products deployed by the Managed Cloud team.
- Bug: A defect in the Managed Cloud.
- Improvement: Suggestion you make to improve a WSO2 product or any Managed Cloud service.
- New Feature: A requests you make in a future releases of a WSO2 product.
- Task: Issues that either you or WSO2 needs to look into. Announcements: Notifications issued by WSO2. They can be about a new product, service pack or patch. Announcements should never be used for reporting issues.
Fill in the rest of the issue details. Please include the following contact details in the description field so that WSO2 can contact you if you if required.
- Telephone number (country code, area code, number, and extension)
Once done, click Create to create the support an incident JIRA.
available projects, and s elect the Issue Type as
Tip: For more information about the WSO2 production support guidelines and SLA, see here.
<Coming up soon>
A task is an action item that either the customer or WSO2 needs to perform to ensure that certain objectives are met. For example, the WSO2 Managed Service team may create a task for the customer to provide details on their production environment.
The task-handling process is similar to our incident-handling process as shown in the following diagram:
Diagram: WSO2 task-handling process
Manage deployment artifacts
A deployment artifact is a program, config change, patch etc. that the customer or WSO2 deploys to the Managed Deployment, either manually or via automated scripts. Both the customer and WSO2 need to follow the below best practices to minimize the possibility of new artifact deployments causing issues in the Cloud setup:
- Ensure that all deployment artifacts go through the complete application management lifecycle (ALM) before being deployed in the production servers.
Ensure that all the artifacts are properly tested. If additional testing and development need to be done to an artifact, the customer can request development support from WSO2.
Manage upgrades and migrations
In case of a WSO2 product migration or an upgrade that is either suggested by WSO2 or the customer, WSO2 first carries out an effort estimation. If there are no customizations done to the WSO2 products, then the upgrade or migration can be straightforward. If not, the customer and the WSO2 account manager together are to decide how to handle the upgrade or migration of customer-specific data and any custom codes. Any WSO2 product customization, done by either the customer or WSO2, does not belong to WSO2. The ownership of any custom code is with the customer.
Apply WSO2 security patches
Given below is the WSO2 security patch application process.
Note that the non-production environment where the security patches are first tested on must be shared with WSO2 by the customer beforehand.
Applying monthly security updates is a m andatory operation. WSO2 Operations team takes every possible measure to ensure a smooth update with ideally no downtime. WSO2 expects your cooperation towards this task. If you do not wish to have updates installed or wish delay them, please send an email to firstname.lastname@example.org with the reason.