Skip to content
This repository has been archived by the owner on Feb 19, 2020. It is now read-only.

Logisland Data Historian 1.0.1 - Oct 2018

Latest
Latest
Compare
Choose a tag to compare
@amarziali amarziali released this 02 Nov 12:56
· 11 commits to master since this release
1.0.1
efe237e

Release notes 1.0.1

New features

  • CSV import of tags datasources (configuration).
  • Set up Grafana Dashboard. Authentication SSO with keycloak.
  • Dynamic gauges in 'gauges' page.

Known issues that will be fixed in another release

  • no link back to historian in grafana

    • in grafana there is no link to go back to the data historian application

  • Tags on/off

    • when user turns off a tag that has previously been turned on the tag is still green
    • behavior expected: when user turns off a tag that has previously been turned on the tag should turn black (inactive)

  • 404 Not Found when user clicks on browser back button

    • from any application page (Datasources & Tags, Csv Tag Import, Tags, Gauges) user clicks on Dashboard on the left vertical menu
    • user clicks back button on browser
    • user gets 404 Not Found
    • user gets a 404 Not Found also when Keycloak session is over and user logins again

  • Csv Tag Import

    • there should be a information message on the Csv Tag Import page that says that it is mandatory to create first a data source before importing Csv Tag

  • Missing page titles

    • Datasources & Tags http://historian.hurence.com:10080/sources-and-tags on the left menu there is Datasources but the title is Datasources & Tags
    • Page title in page should be Datasources or menu should be Datasources & Tags
    • Visualization > Tags there is no title on the page
    • Visualization > Gauges there is no title on the page

  • Help menu icon link is dead

  • Server connection Status always red even if server is connected and gathers data

    • add new automatic data source opc.tcp://opcua.demo-this.com:51210/UA/SampleServer
    • Server connection Status is red
    • tags are shown in tags panel

  • Server names with more than 19 characters

    • in the tags panel in visualization > tags & visualization page
    • tags names don't fit on tags panel when tag name is more than 19 characters
    • 8 characters when tag name is WWWWWWWW

  • Configure your new gauge

    • Monitored tags have parent node id
    • monitored tags should have actual tag name

  • Can not resize or move the gauges.

  • If we refresh a page of the application that is different from the root '/', we have a 404 Not Found error, we must navigate using the application's navigation menu.

  • Uncorrected tabular view. Metrics on a single point.

  • The values ​​of aggregations in grafana are done at the level of grafana, that is after sampling points by bucket in chronix. This means that aggregations are approximations unless the query's time-range is sufficiently weak. For example, if you want to have the value 'current' of a tag you have to use the shortest possible time interval.

  • In the form of the gauge the fields 'Tag' contain all the tags of the historian which could pose problems with a number of very high tags (no tests performed to date but the problem should not happen before to wait for ten thousand tags?).

  • The choice of the time range custom is in a sub-menu of the menu time range, the two sub-menu will be merged in a future version.

Bug Fixed Before Release

  • Problem for saving dashboard gauges:
    • No popup when the user changes pages with unsaved changes.
    • The popup appears after clearing the dashboard (not consistent), the dashboard should just be erased.
    • If we modify the dashboard gauges without saving, that we change the name of the dashboard in the dashboard management menu, that we then save the gauges, it will erase the modification of the previously done name. Therefore, after changing the name or description of a dashboard, refresh the page before changing the gauges or save the gauges before changing the name of the dashboard.
  • When creating a new dashboard the default values ​​of auto-refresh and time range are not ideal:
    • 'None' for auto-refresh => Done put to '10 seconds'.
    • '1970-01-01T12: 00: 00 + 00: 00 to 1970-01-01T12: 00: 00 + 00: 00' for time range. => Done put to 'last 15 minutes'.
  • Saving a dashboard does not work if auto-refresh is 'None'.
  • When update of a dashboard fail the user can not know it, no message is showed.
  • When id in cookie not found infinite pending in dashboard page.
  • The form of creating / editing a gauge lacks aesthetics, especially with regard to color areas.
Assets 2
Loading