We launched xMatters On-Demand way back in 2010, which in high-tech time is roughly when the Flintstones were cohabitating with dinosaurs. Back then, many of our customers were in their own early stages of cloud adoption with requirements still best suited to xMatters data centers at colocation facilities. Seven years later, software services have changed drastically, with even the most security-focused banking, healthcare, and government agencies adopting some form of approved cloud computing.
To meet this dynamically shifting landscape, we've constantly evolved our solution to drive out complexity, provide new features, and offer ever-increasing levels of performance. Here are just a few examples of those efforts:
- The creation of new cloud-friendly features such as the Communication Plan Builder, which allows our customers to easily design their communication processes and the integrations that drive them.
- Architecture changes to accommodate new design patterns like a micro-services orientation to optimize performance, and to provide new features such as in-country SMS codes (introduced in September 2014 when we launched our first micro-service for SMS delivery).
- Deployment process updates that allow us to deliver fixes and features faster and more efficiently - and then even faster and even more efficiently again.
These changes have allowed our service to grow and change in concert with our customers' shifting needs. Now, to best support current and future needs, our services are evolving again and our underlying infrastructure will be undergoing important upgrades and enhancements.
In short, we're upgrading our private infrastructure as a service provider to make sure we can support all of our customers, no matter their size or requirements. Consider the following:
- Scale - We have hundreds of customers, each with their own unique needs for toolchain integration, data synchronization, notification, and other resource-intensive operations.
- Elasticity - Need for scale is unpredictable and may require our services to dynamically expand and contract as our customers deal with event floods from monitoring systems, updates from the HR system, large notification requests for major incidents, and similar usage spikes.
- Availability - Communications are a critical component of IT process and cannot afford downtime.
- Analytics - Vast amounts of performance and behavioral data pour into and through the xMatters system, allowing our customers to gain important insights into their processes.
And, of course, the biggest point of all:
- Security - Security is a concern for everybody, in the cloud or otherwise. We're building out an ISO 27001-compliant system, and supporting multiple hosting regions to help meet data localization requirements. We'll be able to offer new or improved versions of our data-at-rest cryptographic and physical protection, secure browser communications, and privacy and security program.
What's the process?
The process of migrating to our new services will be similar to our existing processes for failover. In advance of the migration, services and data will be created and replicated as necessary. The old and new environments will be kept up to date through our continuous delivery processes.
Customers will be provided with their migration date 90 days in advance. Prior to the migration date a confirmation will be sent with a specific one-hour maintenance window for the migration.
During migration, xMatters services will be unavailable for a period of time. The process is similar to our existing datacenter failover so customers can expect a similar duration for the operation. xMatters is currently testing and refining the migration process and more detailed information will be available based on our testing.
Non-production environments will be migrated in advance of production migrations. The non-production migrations will allow for customers to perform any testing or validation required in advance of the production migration.
When is this happening?
The timing of each migration will be dictated by your hosting region with the following date windows:
Europe, Middle East and Africa
We'll update production environments two to four weeks after their related non-production environments.
Check back here for the official dates here once we've finalized them.
How do you get ready?
We understand that change can be a pain - we're big consumers of evolving technologies ourselves. The good news for migration is that there's a lot of long-term gain for a bit of up-front pain. If you'll allow us to get a bit geeky for a moment, consider that Lehman's laws of software evolution are just as valid today as they were when they were first written decades ago.
And, in our case Lehman's Law of Increasing Complexity applies to this improvement: as a system evolves, its complexity increases unless work is done to maintain or reduce it. Migrating our service allows us to replace older components with modern technologies - and we believe now's the time to reduce the complexity of our system while offering customers the latest capabilities.
The following sections outline the changes that will require customer action.
Networking and Email
Any optimizations you have created in your own networking, email routing or other systems that use hardcoded addressing techniques will need to be evaluated and potentially modified to point to the new xMatters environments.
xMatters strongly discourages the use of IP whitelisting. Our experience with providing emergency communications for incidents of all types, including disaster recovery and business continuity situations, has taught us that any mechanism that restricts the immediate and critical flow of communications can be a hindrance - especially in a crisis. Although IP whitelisting is often seen as part of a "Defense-in-Depth" strategy for traffic shaping, the dynamic services offered by cloud providers - including xMatters - may not perform optimally with these strategies. In fact, the high-availability protocols used by cloud services, such geographic and high-IP-range load balancing, can produce a denial-of-service (DOS) issue if the load balancing systems require an IP change.
To help provide the best security possible without impacting the free flow of events and notifications, we provide a full range of application-level access management and control, including native and federated secure login, and data-in-transit protection via HTTPS/TLS.
Customers with stringent security policies that are using IP whitelisting or other filtering will require customer side changes in advance of the migration to ensure they don't experience a service interruption. We will work toward a solution for customers who absolutely must have specific IP ranges, however we cannot identify when or if our customers are using this type of customization. You will need to proactively identify if you need to modify your network settings.
End of Life for Advanced Messaging (legacy scenarios)
Advanced Messaging is - or, rather, was - a module for saving and recalling message content, recipients, and responses so communication processes could be predefined for important incident response activities. The feature was a precursor to our Communication Plan Builder and lacks many of the abilities that our newer communication plan forms and their scenarios support, including:
- Purpose-built forms with input validation to gather the exact information you need to drive your incident response
- Drag-and-drop design tools for building message templates for text (SMS), voice, email, and mobile app push content
- Mobile app initiation and status reporting
- Map-based recipient targeting
- Message scheduling
- And much more...
Customers will need to re-implement any advanced messaging content to form-based scenarios - the benefits in usability and functionality are already reason enough to make the switch! As an added benefit, this consolidation of our feature set into the newer technology means we can focus on refining enhancements, performance tuning, and bug squashing to constantly improve your xMatters experience.
End of Life for Action Scripting
Action Scripts and the event domains they live in were our mechanism for defining business logic, message formats, responses, and integration behaviors. This proprietary language has been replaced with our drag-and-drop communication plan design tools, and the Integration Builder offers a much better method for building custom integrations. And, you'll recall that our Integration Directory offers over 60 pre-built, easily-configured integrations to common IT systems - with more being added all the time.
Customers will need to re-implement any integration that uses Action Script to either an integration from our Integration Directory, or an integration built using our communication plan design tools. Consolidating your event traffic to flow only through our newer technologies allows us to provide an event pipeline with enhanced capabilities for filtering, suppression, correlation, and prioritization so that each communication process can reliably find the right recipients.
Changes to Customer Hostnames and URLs
We're simplifying the URL used to access xMatters by removing extraneous hosting information. In addition to improved usability, this change allows us to make important improvements to our infrastructure, including enhancements to performance, security, reliability, and data retention.
For most of our customers, there's nothing you need to worry about right away - though we do encourage you to start using your new and improved hostname. For a few of our customers, this change might cause a conflict if they have similar hostnames for different locations, such as "example.hosted.xmatters.com" and "example.na1.xmatters.com".
We have already identified the clients that will be impacted by this change, and we'll be working closely with them to select a new hostname, and to devise a project plan specific to their individual inventory of affected components.
In addition to these changes we strongly recommend the following when building new integrations:
- Integrate events using our Integration Builder. The REST API's POST trigger end point will eventually be deprecated with the expectation that all integration traffic will use the Integration Builder. We've made this very simple with the addition of our "Create a new xMatters event" action in inbound integrations - it understands exactly the same JSON payload as the REST call.
- Use xM API calls for web services work. Our SOAP API and older REST API will eventually be deprecated. While we haven't yet provided deprecation dates, using these older technologies will mean more work later on to move to the equivalent xM API calls.
How do you get help?
We are ready, willing, and eager to help you however we can!
We've already engaged with a number of customers that are preparing for the migration and we're finding that they frequently want to re-evaluate their integration points to best support their IT processes and to use our latest integrations. Your Client Success Manager is a great resource for walking through your current processes and integrations.
If you already know what you'd like to do but need technical assistance with our supported integrations or changes to your deployment, contact xMatters Support by submitting a request.