Back in v8.1 we opened Historian up to AI: ask your data a question in plain language, through whichever model your team already uses. Historian v8.2 keeps opening the platform up; this time to the systems and workloads industrial teams already run.
Historian now speaks Ignition natively
.png)
The Factry Historian Ignition module is a native, open-source connector that registers Factry as a historian provider inside Ignition. Mark a tag for historization in Ignition Designer, the way you always have, and Factry picks it up automatically. No second configuration step, no separate mapping to maintain. New tags and lines added later are picked up the same way.
It works in both directions: because Factry registers as a standard Ignition historian provider, you can also query Factry data directly from an Ignition Power Chart, including measurements collected from sources other than Ignition.
Source and issue tracker are public: github.com/factrylabs/factry-historian-ignition-module.
A fully-documented, fully-validated API
Historian's API has moved from Swagger 2.0 to OpenAPI 3.0. That means that the API's validation logic now ties directly into the published spec, so the API behaves exactly as documented. If you build against Historian's API (custom scripts, the Excel Add-in, Seek, or your own tooling) upgrades and new endpoints are now easier to trust and easier to build against. Error responses are clearer too: standard status codes and messages instead of guessing what went wrong.
Built to stay fast as you grow
.png)
Two changes protect performance as installs get bigger:
- Query rate limiting. A new admission control system rate-limits time-series queries, so one heavy dashboard or one bad query can no longer degrade Historian for everyone else on the instance.
- Faster asset trees. Asset hierarchy performance work speeds up large installs. It's also what powers the new lazy-loaded asset picker in the Grafana datasource plugin. So assets, event-asset properties and event filters now load roots first and children on expand, instead of the full tree at once.
Small things that add up
A new issues panel on the homepage surfaces problems with your installation at a glance, alongside live CPU and memory usage per process means you won't have to digging through logs to find out if something's wrong.
Still the same Historian, still moving forward
This release centers on a complete rebuild of the REST API with lots of stability optimizations to improve and performance under load. There are also refinements to event and calculation workflows under the hood. All this results in noticeably faster asset trees, richer event detail and a more informative homepage.
See full release notes here: docs.factry.io.
.png)
