News and Announcements
Kaizen Database Upgrades
As part of our continued effort to bring to provide a stable and secure fault detection and diagnostics platform to everyone, we will be migrating our databases to Atlas starting on November 25th 2021.
During the upgrades, the Kaizen UI will be available and up-to-date TL data can be viewed, however, Insights, CTL updates, Reports, and other calculations will not be generated until upgrades are completed. It is best to treat Kaizen as “read-only” for this time to ensure continuity as the upgrades complete.
Additionally during this period, your data collection devices may appear as “offline”, though, this is not a true indication of its connectivity. To verify its connection, check the Vault for updated TLs.
What will this be affecting?
By migrating to MongoDB Atlas we will be able improving our support of the following features:
- High performance: The MongoDB WiredTiger storage engine with compression and fine-grained concurrency control ensures that we can meet your most demanding storage requirements.
- Scalability: One-click, automated-sharding for scale out, and zero-downtime scale up to larger instance types. Ability to provision TBs of database storage, all on high performance SSDs with dedicated I/O bandwidth.
- Monitoring & alerts: Instant visibility into the database and hardware metrics that matter, so we can stay ahead of any issues that could impact performance and user experience.
- Strong security: Out-of-the-box protection of your most valuable data assets. Security features include TLS/SSL encryption, authentication, and authorization via SCRAM; network isolation and VPC Peering on AWS; IP access lists; encrypted storage volumes; and the MongoDB Atlas console to manage databases.
- Highly available: A minimum of three data nodes per replica set are automatically deployed across availability zones (AWS), fault domains (Azure), or zones (GCP) for continuous application uptime in the event of outages and routine maintenance.
- Workload Isolation: With MongoDB Atlas maintaining up to seven replicas of your data, we can concurrently run operational and analytical workloads across the same databases, without resource contention.
- Disaster recovery: Fully managed backup service with continuous, consistent backups and point-in-time recovery, backed by custom retention policies.
How is this going to impact you?
At CopperTree Analytics, we have been privileged to collect data from over 2500 client buildings, and as a result of that we have generated a ton of meta data. So much so that in order to guarantee a successful transfer we will need to remove calculated trend logs older than 3 years, before we start the transfer. We will also need to turn off the reporting engines during the transfer period, to keep the DB as static and predictable as possible. Don’t worry if you have CTLs older than 3 years, they can be regenerated from your Time-Series Trend Log Data that will be moving over to Atlas. Also, once the transfer is complete, the Reporting engines will be turned back on and they will start to backfill information for the period they were turned off. Additionally, APIs will upgraded and therefore some of the old endpoints will be replaced by new ones.
Timeline:
- Tuesday November 23rd, we will start preparing the DB for migration, by backing up the DB, removing all CTLs older than 3 years, and making another backup.
- Thursday November 25th, we will turn off the reporting engines and begin the migration. You will still be able to use Kaizen during this time, but rules and reports will not be active. We expect the Migration to complete on Sunday November 28th.
- Monday November 29th, assuming the transfer is completed and data has been verified, Kaizen will be upgraded to the latest version compatible with Mongo Atlas. The Reporting and Rules engines will be turned back on. We expect it to take up to 3 days from this point, for the engines to get caught up with the backlog of work.
API Upgrades:
If you are using the Kaizen API to retrieve data, the DRF endpoints are being upgraded to work with Atlas. The functionality will remain the same, however, the routes have changed slightly as the microservice’s that host the endpoints have been upgraded.
Kaizen Central Deprecated Endpoints:
Kaizen Central Current and Replacement Yana Endpoints:
https://kaizen.coppertreeanalytics.com/yana/mongo/heartbeat – ‘GET’, ‘POST’
https://kaizen.coppertreeanalytics.com/yana/mongo/geocoded_weather/<int:building_id>/ – ‘GET’, ‘POST’, DELETE’, ‘PATCH’
Kaizen East Deprecated Endpoints:
https://kaizen-east.coppertreeanalytics.com/api/v3/objects/
https://kaizen-east.coppertreeanalytics.com/api/v3/object/<string:pk>/
https://kaizen-east.coppertreeanalytics.com/api/v3/kaizen_variables/templates/<string:pk>
https://kaizen-east.coppertreeanalytics.com/api/v3/kaizen_variables/templates/
https://kaizen-east.coppertreeanalytics.com/api/v3/trend_log_summary/
https://kaizen-east.coppertreeanalytics.com/api/v3/trend_log_summary/<int:building_id>
https://kaizen-east.coppertreeanalytics.com/api/v3/geocoded_weather/<int:building_id>/
https://kaizen-east.coppertreeanalytics.com/api/v3/systems/
https://kaizen-east.coppertreeanalytics.com/api/v3/inventory_with_last_heartbeat/<int:inventory_id>/
https://kaizen-east.coppertreeanalytics.com/api/v3/inventory_with_last_heartbeat/
https://kaizen-east.coppertreeanalytics.com/api/v3/trend_log_objects/<string:pk>/
https://kaizen-east.coppertreeanalytics.com/api/v3/kaizen_variables/<int:building_id>/
Kaizen East Current and Replacement Yana Endpoints:
https://kaizen-east.coppertreeanalytics.com/yana/mongo/heartbeat – ‘GET’, ‘POST’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/objects/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/object/<string:pk>/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/kaizen_variables/templates/<string:pk> – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/kaizen_variables/templates/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/trend_log_summary/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/trend_log_summary/<int:building_id> – ‘POST’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/geocoded_weather/<int:building_id>/ – ‘GET’, ‘POST’, DELETE’, ‘PATCH’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/systems/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/inventory_with_last_heartbeat/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/trend_log_objects/<string:pk>/ – ‘GET’
https://kaizen-east.coppertreeanalytics.com/yana/mongo/kaizen_variables/<int:building_id>/ – ‘POST’, ‘DELETE’
These upgrades are mandatory and required for the long-term support and stability of Kaizen. For continuity, please update any self-hosted/maintained code that pulls from any of the deprecated endpoints on or before Monday November 29th.
Contact Us
Thank you for your understanding during the transition and cut over, if you have any questions, please do not hesitate to contact our Customer Solutions team, or your account rep.
Customer Solutions
Hours: 7:30am-4:30pm (PST/PDT)
Monday to Friday
Phone: +1 (778) 726-0524
Email: customersolutions@coppertreeanalytics.com