Dualog Fetch - Changelog

INTRODUCTION

This page lists every addition/modification to Dualog Fetch since its first release.

SHORE UPDATE - 05 MARCH 2024

IMPROVEMENTS:

  • Fixed number mismatch for High Severity log lines (overview and details showed different numbers)
  • Modified the high severity log lines details page to only show one line per device
  • In the devices list we have now filtered out installations without configuration and without any devices reporting

SHORE UPDATE - 15 FEBRUARY 2024

IMPROVEMENTS:

  • Add modal for "log lines" for the pie chart on Fetch start page
  • Added datepicker for "Devices reporting"
  • Modify last 24 hours to be last two days for the pie chart
  • Show all vessels, not only those reporting data the last 7 days

VERSION 2.1 - 04 DECEMBER 2023

IMPROVEMENTS:

  • Additional small improvement in RFC 3164 timestamp parsing
  • Include the structured data in the message filter. Format: <structured data <message>

BUG FIXES:

  • Fixed parsing of structured data in syslog messages of type RFC 5424

SHORE UPDATE - 07 NOVEMBER 2023

IMPROVEMENTS:

  • Loading indicators all-around

SHORE UPDATE - 23 OCTOBER 2023

IMPROVEMENTS:

  • Devices list. Now showing all devices, also those without any data last 7 days
  • Devices list: default sorting set to time for "Last sent data "
  • Devices reporting card now shows both number of ships and devices
  • All numbers now with 1 000 separator for readability

BUG FIXES:

  • Fixed issue when moving between Config and Status
  • High severity log lines: Fixed number mismatch between card and list

SHORE UPDATE - 12 OCTOBER 2023

IMPROVEMENTS:

  • Fetch status page: Added online/offline traffic light for devices list
  • Fetch status card: Non-clickable card does not longer look like it is clickable

SHORE UPDATE - 19 SEPTEMBER 2023

IMPROVEMENTS:

  • Now released with .NET 6 dependencies.

SHORE UPDATE - 19 SEPTEMBER 2023

NEW FEATURE:

  • Fetch alert is now available

VERSION 1.10 - 09 MAY 2023

IMPROVEMENTS:

  • Replacing the use of Webrequest with the System.Net.Http.HttpClient class.

VERSION 1.09 - 14 MARCH 2023

BUG FIXES:

  • Fixed issue not listening on port 514 if it fails during startup. Now it tries forever trying to listen on port
  • Fixed issue where it crashes when Metadata.json is corrupt

SHORE UPDATE - 09 FEBRUARY 2023

NEW FEATURE:

  • New status page

BUG FIXES:

  • Fixed issues where reader access was not implemented

SHORE UPDATE - O5 OCTOBER 2022

IMPROVEMENTS:

  • Retrieve logs from clients: Missing serviecs added (Fetch, LinkTransfer, Endpoint)
  • Cosmetic fixes

VERSION 1.7 - 16 SEPTEMBER 2022

BUG FIXES:

  • Link Platform not reporting Fatal error
  • Config file (appsettings.json) is recovered correctly (actually hardcoded the cloud URL

VERSION 1.5 - 06 SEPTEMBER 2022

IMPROVEMENTS:

  • Reporting status data to ship status UI

VERSION 1.4 - 17 March 2022

IMPROVEMENTS:

  • Several performance improvements

 

VERSION 1.3 - 17 March 2022

IMPROVEMENTS:

  • Improved crash recovery
    Added timeouts7delay on startup.

BUG FIXES:

  • Fetch Client Recovery
    Fixed an issue where the fetch client crashes and fails to start when unable to receive the token.
  • Reset of daily counter
    Fixed an issue where the counter for bytes/lines does not reset if the PC is hibernated around midnight.

 

1.2 (17 February 2022)

NEW FEATURES:

IMPROVEMENTS:

  • Improved logging
    Added minor adjustments to the logging, such as time formats and exception dumps.
  • Adjustments to aggregated traffic data
    Added adjustments such as splitting of agg.data on day, on sent/detected and using the hostname as key.

1.1 (01 February 2022)

NEW FEATURES:

  • Now available as a service under Installations.

IMPROVEMENTS:

  • Improved performance
  • RFC 3164 is now supported
    RFC 3164 is now detected and accepted to support firewalls and etc that use this RFC standard.

1.0 (24 January 2022)

  • Fetch is now available!
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Article is closed for comments.