Release Date: 16 August 2023

Patch Details (1.7.3)

  • Upgrade Go version to 1.20
  • Add upgrade support for Neo4j 5.11.0 and 4.4.24
  • Only attempt auto-update of agent if the current version has auto-update capability

Patch Details (1.7.2)

  • Fix issue where instance status events for unknown instances lead to duplicate EventSpecs resulting in errors in the persistence DBMS
  • Fix issue where alert ‘Failed to get neo4j config for max heap size’ was being shown when metrics namespaces are enabled
  • Handle the fact that composite databases return a null value for role in `SHOW DATABASES` 
  • Fix issue where NOM server being unavailable resulted in a monitored Neo4j instance becoming unavailable. (Due to the custom query log appender in log4j blocking on writing to the socket)
  • Stop sending query parameters from Neo4j instance to NOM agent
  • Helm Chart no longer requires secret in values.yaml – can now be referenced

Highlights (1.7.1)

Overview

This is a minor release with a selection of bug fixes and small improvements.

Highlights

  • Query optimization
    • Use Neo4j client instead of driver for persistence queries
    • Reduce number of queries run on persistence DBMS when an instance status message is received from an agent
    • Decrease the number `CALL db.info` queries run by agent against monitored instances
    • Agent config for NOM operational queries
  • Uptime/Downtime and NOM summary
    • Show uptime for NOM, DBMSs, instances and Database instances
    • Show summary for NOM installation including: 
      • Version information
      • Information about the persistence being used
      • Information about monitored topology components
      • Information about NOM users
  • Metrics dashboard improvements
    • Added ‘Expand’ option for charts which opens a single chart in a modal allowing for a more focussed analysis of a single metric series. 
  • Improved release testing 
    • Upgrade smoke test
    • Full end to end testing with playwright
  • Read available Neo4j versions from a file instead of requiring a migration
  • Place a red border around charts for metrics that have an active alert
  • Clean up obsolete alert conditions as part of topology clean-up job
  • Provide warnings in the server logs when provided configuration contains invalid characters or is in the wrong format
 

Fixes

  • Generate jwt token if none is provided (instead of using a default)
  • Remove orphan query log nodes
  • Fix an issue where query logs fail to stream after an upgrade
  • Provide a script to enable Ops Manager persistence DBMS to be upgraded from 4.4.x to 5.x
  • Fix issue with alert banner so that it now disappears as expected when all alerts listed are cleared
  • Fix issue with sorting in the Conditions table
  • Fix auto-refresh on Agents view
  • Fix issue where space usage is incorrectly reported when directories are sub-directories of home directory
  • Add exec permissions to agent in Agent docker image
  • Provide better messaging about offline database instances when creating an upgrade plan
  • Fix date formatting error which was causing certain  times to be incorrectly displayed as ‘24:xx:xx’
  • Show log summary instead of log detail view when coming from Metrics dashboard with a time period that does not contain any log details
  • Fix issue where lines between data points were not being correctly drawn for metrics charts at certain zoom levels
  • Make DBMS switcher menu scrollable so that it is usable with a large number of DBMSs
  • Fixed issue where threshold for page cache percentage was displayed incorrectly