For redundancy, it is recommended you push data from the Canary Collecter and Sender Service to both a primary and secondary Historian’s Receiver Services.  This means that both the primary and secondary Historian are getting the same constant data feed from any Canary Collector.   

Here was the idea.  Let's show how Axiom would perform if we placed 70 individual trends on a single chart.  Each trend polls at one second intervals and updates 100% of the time.  Then, once we have all 70 trends on a single chart, let's call for 30 days of historical values. 

No, it's not a typo. I didn't mean predictive. This morning I was reading an article from SparkCognition, "Changing the World by Way of Oil and Gas", and I came across the term for the first time. After some research, here is what I learned.

The Industrial Internet of Things is changing the way companies operate. Whether you have already adopted an IIoT strategy or are beginning the planning phases of how/where to begin, there are two key elements that you must first focus on. 

Canary recently hosted it's first Crash Course, a webinar designed to teach you how to functionally use a Canary product in less than 30 minutes.

Could Cassandra be optimized to store time-series data? This is a question that has become a common topic for discussion. I recently came across a great read that compares Cassandra performance to another dedicated time-series database, TimescaleDB.

"40 percent of the workforce at electric and gas utilities will be eligible for retirement in the next five years."

Recently, a system integrator asked us to provide data that would provide both speed and storage requirement comparisons between an out-of-the-box SQL database and Canary.  They wanted to use this data to decide whether it would be best for customer's to deploy a Canary system, or deploy, tune, and maintain an SQL system.