RELEASE NOTES
Chief Database release notes provide information on the upgrades, bug fixes and improvements that have been implemented within Chief Database and Chief Software solutions
30 JUNE 2023: v3.1.0
Major release with the following new features:
- Ubuntu 22.04 certification
- point-config GUI to manage points
- Improvements to RESTAPI to manage points, metas and point types
- performance improvements to RESTAPI for syncing with Seeq and other systems
- Tech previews: Visualiser editor and manager & Alarm management window
Point-Config
Point-Config is a GUI to manage points, previously point management had to be done via the command line tools:
- navigate to http://chiefweb/point-config
- From here you can search for points with the standard 4 methods
- Update or change any part of the point
- Delete the point
- Migrate a point to another database within the cluster
- See the coordinate size and descendant size
- Coordinate type and time type changes can only occur on an empty coordinate point
Visualiser Editor and Manager (Tech Preview)
The visualiser can now:
- Manage page files: including creation and upload of new visualiser pages
- Navigate to http://chiefweb/visualiser
- Navigate to http://chiefweb/visualiser/manage
- Edit page files online
- Add new placeholder on the screen live
- Move placeholders around the screen
- Create or save the page
- Navigate to http://chiefweb/visualiser/htmlpage/
- Press CTRL-ALT together to expose the editor panel on the top right of the window
- Edit page files online
- Add new placeholder on the screen live
- Move placeholders around the screen
- Create or save the page
- Navigate to http://chiefweb/visualiser/htmlpage/
- Press CTRL-ALT together to expose the editor panel on the top right of the window
- Pages are arranged in a user defined hierarchy
- Manage symbol files, including creation and upload of new visualiser symbols:
- Navigate to http://chiefweb/visualiser/manage/symbols.html
Visualiser Alarm Window (Tech Preview)
An alarm window is now available that will show a real-time list of alarms, these alarms can be audiable and acknowledgeable:
- Alarms are display for specific point-type named alarm
- Alarms are string coordinate types with specific JSON coordinates in the format: o { “priority”: “high”, “message”: “alarm text message” }
- Only new alarms are shown
- Alarms are displayed in real-time
- All of the database point security is used to limit view and acknowledgement of the alarms
31 MARCH 2023: v3.0.1
Major release with the following new features:
- Coordinate Types
- MQTT Sparkplug-B
- Single sign on (SSO) - OIDC/OAUTH Azure AD integration + JWT support
- More RESTAPI services
- Aged Tiered Storage - online archive onto slow disk (AWS EBS SC1 cold HDD support)
- CDB-849 - Single Sign On
- CDB-850 – Chief Web RESTAPI
Chief now supports the following coordinate types:
- boolean
- int8, uint8, int16, uint16, int32, uint32, int64, uint64
- float, double
- string
- blob
- double array (one or more double)
All coordinate types support start scan coordinate quality (to indicate when a contiguous set of good data has been stored). Each coordinate can now have for following time precision:
- Date time to second precision: 64 bit resolution - practically can store any date and time since the big bang, and 292 billion years into the future
- Date time to nanoseconds precision: 1 at the nanosecond resolution
Fixes in this release:
- CDB-657 - DNP3 test fails intermittently
- CDB-663 - Coord Types - Test/utilities_test/test.sh failed when using ramdisk to test disk full
- CDB-679 - Coord Types cdbbuild upgrade not working
- CDB-728 - Coord Types import/export test failure
- CDB-794 - arm64 test failure [ FAILED ] testCompression.scannedTriangle
- CDB-798 - cdbimport_csv ignores every 2nd row
- CDB-880 - Syslog program name becomes corrupted
- CDB-831 - Chief Trends - Search across "ALL" causes disconnects and fails
4 NOVEMBER 2022: V2.7.10
- Added RESTAPI verbose option - improve Seeq point sync speed
- Improved performance of Binary Interface List Points Slow when concurrently called
8 AUGUST 2022: V2.7.0
- Chief Database now supports full text searching
- Natural language searching as default in Chief Trends (selectable in search window and command line)
- Clustered watches – watch a single DB with Coords persisted in another DB’s in the cluster
- Config now has factory settings in memory, overwrite the defaults in customer editable configuration property files
7 JULY 2022: V2.6.1
- Chief Mixed Integer Programming (MIP) Engine
- Ability to solve complex optimisation problems in real-time
- MIP integration with CBC solver and IBM ILOG CPLEX Optimiser
11 MAY 2022: V2.5.1
- Chief database clustering across different network security zones (i.e. secure and corporate)
- Ability for clustered database nodes to act as read-only copies
16 NOVEMBER 2021: V2.3-90
- Fix of handling of error when creating points such as alias too long - The previous release was closing the Chief Database connection on errors
1 NOVEMBER 2021: V2.3-88
- Removed version from non JSON response to metrics REST call
28 AUGUST 2021: V2.3-87
- Implement Chief MQTT Collector Quality Feature
- Improvements to create and automatically archive JSONL files for Chief MQTT Collector Created Points
- Remove Prometheuos version from the metrics in the REST API
11 JUNE 2021: V2.3.0
Highlights:
- Journalling of Point Store Index File, dramatically improving recovery time on large databases (from many hours down to several minutes)
- In-memory point searching implemented to improve performance of point lockups (seconds down to milliseconds)
- Implemented a more efficient Binary Interface for adding coords to the Chief Database
- New feature to auto expire points, which automatically creates a start scan coordinate if that point becomes stale
- Migration of Chief-Web Visualiser to jquery
Fixes in this Release:
- CDB-452 Chief Trends: Fix display for newer versions of Chrome
- CDB-540 Chief-Database: splitting point store caused duplicate point store
- CDB-515 Chief-Database: fixed intermittent time test failures
- CDB-504 Chief-Database: RESTAPI escaping double white-space instead of tab
- CDB-502 Chief-Database: improve start performance with large point and point type maps
- CDB-500 Chief-Database: RESTAPI rounding coordinate values
- CDB-466 Chief-Database: fixed a bug where points in / but not in /
- CDB-11 Chief-Database: Stop coordinates being added to a symbolic link point
- AC-500 Chief-DNP3-Master: Resolve sending of controls
- AC-498 Chief-Database: Maintenance thread triggered dead-lock
- AC-457 Chief-DNP3-Master: Stopping chief_dnp3_master didn't set dispatch PLC comms to FAILED
- AC-456 Chief-Database: Point changes triggered a dead-lock
Other Improvements and Features in this Release:
- CDB-539 Chief-Database: changing debug_level during run-time – update configuration file and send CDB HUP signal
- CDB-471 Chief-Utils: Add point type search to cdbls
- CDB-430 Chief-Database: Add cdbbuild upgrade to integration tests, and moved to versioned SQLite change process
- AC-494 Chief-DNP3-Master: Added more logging control – see cdbmc
- CDB-507 Chief-Database: Added a test to make sure point store index rebuild is ordered correctly
25 MARCH 2021: V2.0.76-997
A point release containing bug fixes and minor improvements:
- AC-440: add coordinates to now trigger watchers on symlink of symlinks
- CDB-500: fix bug were restapi coordinates were rounded. also replaced tab spacing with white spaces
- AC-438: various bug fixes to network status manager.
- AC-380: added input checking for switch states within network status manager
- AC-439: fixed remove trigger causing chief_database segfault
- AC-380: added logging for device status inputs within network status manager
- AC-436, AC-404, AC-405, AC-437, AC-438, AC-380: fixed design flaw regarding switch changing states
- Fixed RHEL 7 chief-web httpd config issues
- Fixed chief-web slapd config on RHEL 7 (factory install, not docker): cp: cannot stat ‘/usr/share/doc/slapd/examples/DB_CONFIG’: No such file or directory
- AC-397: fixed bug when adding coords out of order to an empty point store causes coordinates to go missing
- CDB-473: enhanced Chief Database binary service get coords - wildcard alias, case-insensitive, max points, on-the-fly compression, overlapping features
- CDB-471: add point type search feature to cdbls
- CDB-470: improved restapi performance when selecting points by alias
- Various other minor bug fixes and spelling mistakes
24 FEBRUARY 2021: V2.0.76.797
- AC-313: added Chief Calculator perl function to download a list of coordinates from CDB
- AC-369: fixed bug where Visualiser displays not always updating
- CDB-464: improve Visualiser performance on clients’ browser
- CDB-456: exposed overlapping restapi get coordinate services
- AC-366: hide Chief Calculator log message re symlinked points
- AC-319: added option for Calculator perl Point->coord to bypass cache and fetch latest data from CDB, moved endpoint to use Calculator config endpoint
- CDB-439: cdbrm recusive deletes (and Soap service) now deletes embedded symlinks
- AC-350: fixed bug where Chief Database segfaults when watching a point which has been deleted
- CDB-453: fixed bug where Chief Web TLS not configured correctly on Ubuntu 18.04
- AC-365: add feature on Chief DNP3 Master to disable event polling when doing integrity scanning only
- CDB-444: fixed bug where cdbbuild corrupts point store index file
- CDB-443: removed requirement to increase stack size on large point Chief Databases
- AC-351: fixed bug where network status manager fails when a switch doesn’t have any devices
- CDB-422: allow cdbc (and associated Chief Database SOAP service) to add ancestor points if they don’t exist
- AC-349: fix bug where network status manager fails to set status on startup
- AC-348: development preview for the Chief Network Status Manager, this daemon will set the state (energised or dead, and which network it is connected to) of connections (cable, busbar or lines), devices (loads, generators) and switches using a mesh-capable tracing algorithm and telemetry/manual switch status
- CDB-438: fixed licence error causing cdbbuild to fail on large point databases
11 JANUARY 2021: V2.0.76.6RT32
Primary changes within this release were to fix MQTT data loss issue, and include:
- Added a max queue size for inbound MQTT messages, this limits the number of in play MQTT payloads. There is also a flush size, which controls when more MQTT payloads are retrieved
- Fixed exception handing in main loop, this fixes some specific failure modes
- Fixed chunking in adding coordinates to Chief Binary Interface
23 NOVEMBER 2020: V2.0.76.518
- CDB-378: fixed retention stats reporting for RESTAPI and cdbstat
- AC-213: dnp3_master errors on points which don’t have dnp3 point types
- CDB-432: MQTT alias changes improvements
The following changes have been since the 23 November 2020 release V2.0.76.518:
- CDB-435: MQTT data loss with large payloads
- CDB-432: bug fix related to alias changes from previous commit
- CDB-424: cdbrm add sym unlink and remove child/ancestor options
- AC-257: new RESTAPI service to get coordinates at a particular time, (at, before or after services)
- CDB-414: cdbcrlf return code always error
- AC-230: added option to RESTAPI add coordinate service to remove any existing coords in timeboxed range – overwrite data
- Fixed cdbgc-u output
- Fixed segmentation failure when deleting coordinates in Chief
- DNP3 Master – only monitor changes to DNP3 points
- Added RESTAPI verbose option - improve Seeq point sync speed
- Improved performance of Binary Interface List Points Slow when concurrently called
- Edit page files online