Progress is progress ![]()
Im most excited about Power Historian. Don't use perspective, and the gateway status/config kind of grows on you like your dumb sibling...you learn the quirks and how to navigate/manipulate.
With that said, will there be a path to merge existing historian data into the new power historian? The conference video mentions it's integrated within Ignition and sort of skirted the question about hosting on a remote server. Most of us have SQL boxes...sure hope there is a transition path to turn those into power historian.
My newer understanding of the power historian is that it's not intended for larger installation bases and is intended to be a more performant historian for smaller standalone systems and edge systems.
I could be completely wrong, but considering best practices are to keep the historian separate from the Ignition servers, this breaks that "rule".
2 million tags per second in historian is pretty huge, most ive seen is 40k spread over several servers (and a cost of 3 euro/tag)
2 mil/second was my understanding too...and the size is only limited by the storage space on the ignition box from what i read. If thats changed significantly, thatd be a disappointment.
2 million in the best case scenario probably, assuming earth has no air
QuestDB (which the Power Historian is built upon) boasts 4+ million rows/s for ingestion on a beefy machine. 2 million/s might not be an outrageous number on a powerful server.
I'm excited to start using that. Should be able to build some very performant data dashboards.
So, is today the day ?
Supposed to be, but I would expect it to happen on California time.
I'd guess some time this afternoon if nothing goes wrong or delays the release process...
![]()
When this rolls out will it be available as a docker image?
When this rolls out will it be available as a docker image?
I don't decide these things, but I'm expecting it to be.
Yes, inductiveautomation/ignition:8.3.0-beta1
The Encryption Key Set is stored securely as a kek.json file
I see what you did there ![]()
