Yesterday, Zoomdata proudly announced Zoomdata v2.6, a major milestone that includes improvements in analytic usability, connectivity, and architecture. With the advent of Zoomdata v2.6, we have adopted a release model that allows customer to choose between:
- A long-term support (LTS) version that receives stability fixes only through bi-weekly patch releases
- A rapid release version that adds stability fixes and new functionality every four weeks
In short, Zoomdata v2.5 and Zoomdata v2.6 will be our current LTS and rapid release version respectively. Please refer to this blog post for more information about Zoomdata’s current release model and for guidance choosing the correct version to use. For those customers who have decided to move to our rapid release “train” in their Development and/or Production environments, I wanted to take the time to capture some advisory notices, general best practices, and personal recommendations for our customers.
Stability fixes will only be implemented in the latest rapid release version
Bugs reported in the rapid release will be fixed but customers will need to upgrade to the newest rapid release version to utilize these fixes. For example, assume the current version is v2.6.4 and an issue has been addressed, the corresponding bug fix will be implemented in the v2.6.5 release. Bug fixes or functionality changes will not be backported to previous v2.6.x releases.
Regularly upgrade your environments to stay on the latest rapid release
Our rapid releases will add both stability fixes and new functionality every four weeks. As Zoomdata will be introducing incremental changes, many of which may build upon previous changes, it is strongly recommended that customers upgrade when a new rapid release is available. Doing so will reduce the risk of introducing stark changes to your user base. As such, we encourage customers to upgrade, at a minimum, on a quarterly basis.
Backup your metadata regularly and prior to any upgrades
We recommend backing up your metadata(s) on a monthly basis and prior to any upgrades that you perform. Thus, in case something goes wrong, customers will be able to roll back to an earlier snapshot of your environment if necessary. Please note that Zoomdata does not support downgrade scenarios and it is impossible to rollback without a metadata backup.
Test customizations and any integrations in a Sandbox environment first
If you have customizations or custom integrations deployed in your environments (e.g. custom connectors, custom charts, scripts, leveraging APIs, embedded solutions, etc.), we recommend customers re-test these customizations and integrations in a Sandbox environment first, before applying these changes to any Development or Production environments.
Verify the upgrade, environmental stability, and dashboard behavior prior to upgrading your Production environment
Prior to upgrading your Production environment, this upgrade should first be verified in a lower environment to ensure that the upgrade will be successful, the environment will be stable, and the behavior of core dashboards or user workflows are as expected. This will help ensure that any unexpected changes or potential issues are identified/addressed early by the customer and in advance of the upgrade to Production environments.
To conclude this blog, I wanted to also add a couple of my own personal recommendations that may prove beneficial to some of our customers.
Use Chrome, Firefox, or Edge if possible
Although Zoomdata supports all standard browsers, I encourage using Chrome, Firefox, or Edge with Zoomdata if you are browser-agnostic in your preferences for the following reasons:
- Safari has different default security settings compared to other browsers, which can lead to some issues with websocket requests and visualizations rendering properly, especially if you do not have a valid signed SSL certificate configured in your environment.
- Edge was introduced by Microsoft to replace Internet Explorer as the default web browser on all device classes and designed to be a lightweight web browser with a layout engine built around web standards. Furthermore, Edge was introduced in mid-2015 while IE 11 has been around for more than 4 years (introduced in mid-early 2013). If you choose to use a Microsoft browser, I suggest following Microsoft’s recommendation of using Edge instead of Internet Explorer.
- Both Chrome and Firefox have more robust Developer Tools capabilities that prove quite helpful in terms of troubleshooting browser, network, or front-end issues with Zoomdata.
Check that ALL necessary Zoomdata services are running properly
With Zoomdata v2.6, we’ve moved more completely to a microservices architecture. In fact, we have introduced more than five new microservices in Zoomdata v2.6. We recommend any customers that leverages monitoring tools to check that the necessary Zoomdata services are all running, which can also serve as a good first troubleshooting step in the event of any issues. For example, this will typically include the following services: zoomdata, zoomdata-consul, zoomdata-scheduler, zoomdata-query-engine, zoomdata-stream-writer, zoomdata-upload-service, and the appropriate connector services for your environment.
We’re Here to Help!
As always, the Zoomdata Application Support team is here to help you be successful with using Zoomdata! The best way to contact us would be to send an email directly to email@example.com. You can also find other useful information and links on our webpage.