Home
Changelog

improved

fixed

Ops Manager

Neo4j Ops Manager 1.8 is a maintenance release, and is now available to download for Enterprise Edition self-managed customers from the download page.
Highlights
  • UX improvements across all pages, to improve consistency both within Neo4j Ops Manager and with other Neo4j products.
  • Add more metrics for Databases:
  • -> Checkpoint metrics
  • -> Count store metrics
  • -> Store Size data
  • Handle empty values in Query Logs
  • Reduce size of Ops Manager Server bundles
  • Support Neo4j 4.4.25 and 5.12.0 releases in Upgrade Manager
Fixes
  • Fix format of Teams notification WebHook
  • Fix link from Help -> Community
  • Fix issue with metric threshold alerts where the same threshold would be set for al metrics in the same group (e.g setting a threshold for Disk Used (/Data) would set the same threshold for all Disk Used metrics)
  • Fix bug when granting access using Security Manager
  • Display appropriate message for unaccepted license in 5.9
  • Improve layout of ‘Message’ column in Alerts table
  • Fix issue with fetching an upgrade plan to upgrade to a Neo4j 4.4.x version
  • Show GDS license issues in About page
  • Fix issue with showing Status page for an ungraded DBMS where one or more components are no longer being reported by the agent
  • Fix issue with email notification format. Ensure the SMTP configs username is an email address as some SMTP servers refuse to send emails otherwise
  • Fix issue with apparent discrepancies in disk usage shown in NOM and user observed values

new

AuraDB Professional

AuraDB Free

AuraDS Self-Start

Data Importer

Import

This release of Data Importer brings two new features:
Preview selected
We've made a slight tweak to the Preview feature, allowing you to optionally preview selected parts of your our graph. If you have a particularly complex model, it can sometimes be hard to see how all the different nodes and relationship types being previewed are linking. In these scenarios you can use "Preview selected" to only preview selected parts of the model. This can help you validate specific parts of the model are mapped as expected. In the example below, only the Product, Supplier and SUPPLIES parts of the model will be previewed when using the "Preview selected" option.
CleanShot 2023-09-18 at 15
Generate Cypher script
The Data Importer UI gives you a convenient way to generate your graph model and map data, but what happens if you want to take the import logic and use it somewhere else without the UI? Or what if the Data Importer UI doesn't quite allow the complex transformations that you need?
For these scenarios, we are now providing you the option to view and download a Cypher script representing your model and mapping. You can use these as-is, or adapt for more complex needs.
CleanShot 2023-09-19 at 09
CleanShot 2023-09-18 at 15
CleanShot 2023-09-18 at 15
Examples of where you might use this generated code include:
  • The Workspace Query UI. Note that the files will need to be accessible to the DBMS you are connected to. At present this means Aura customers will need their files accessible on a public URL for the
    LOAD CSV
    command to access them.
  • On the command line via cypher-shell
  • Driver code - De-compose the script to re-use the
    CREATE CONSTRAINT
    and
    MERGE
    statements to implement your loads
The load script itself is commented to help you understand the purpose of the different parts and where you might need to make changes, depending on where you're running it.
You can also choose to download the files with your script, which will give you a handy zip of the script and your files.
We hope you enjoy using these new features and as always please head over to https://feedback.neo4j.com/data-importer with any feedback.

new

AuraDB Enterprise

AuraDB Free

Browser.neo4j.io

This is a minor maintenance release with the following fixes and improvements:
  • Ensure sso access token is always refreshed on expiry
  • Expand editor auto completion detail panel by default
  • Handle more database states
  • Fix plan view for DbHits over 32 bit integer max

new

AuraDB Enterprise

AuraDS Enterprise

Aura API provides Neo4j Aura Enterprise customers with a programmatic way to perform database operations in Neo4j Aura.
The ability to programmatically provision and manage databases is something that Aura Enterprise customers have been asking us for so that they can easily integrate Aura into their end-to-end pipelines, and automate the day-to-day management and running of their Aura estate.
Since Summer 2022, we’ve been on a journey to provide this ability to our customers. After a successful Beta program, we’re pleased to move to v1 (General Availability) of Aura API for our Enterprise customers.
image
Now with Aura API, all Enterprise customers have a secure programmatic way to Create, List, Pause/Resume, Resize, Backup, Restore, Clone, and Delete Neo4j databases as their business requires. Aura API is REST based making it easy to call from scripts or integrate with operational applications so that Aura databases can be managed without the need for any manual actions in the Console.
Please see our API docs for more information on how to get started, and reach out to your Account Manager or the Aura Support Team if you have any questions.
Happy Graphing
Aura Product Team

fixed

new

Ops Manager

Patch 1.7.3 for Neo4j Ops Manager is now available to download.
  • [Fixed] Upgrade Go version to 1.20 to address security issues
  • [New] Add upgrade support for Neo4j 5.11.0 and 4.4.24
  • [Fixed] Only attempt auto-update of agent if the current version has auto-update capability

new

AuraDB Enterprise

AuraDB Professional

AuraDB Free

AuraDS Self-Start

AuraDS Enterprise

Prototype with / Create a GraphQL API with your Aura instance in a few seconds with the GraphQL Toolbox
Screen Shot 2023-08-15 at 16
For further information please see our docs.
Please give it a try and share your feedback!
Thanks
The GraphQL Product Team

new

AuraDB Enterprise

AuraDS Enterprise

Bloom.neo4j.io

Neo4j Bloom Enterprise offers additional features including storage of multiple Scenes, and sharing Scenes & Perspectives with other users based on database role.
image
We are now expanding our Early Access program, which offers Bloom Enterprise to interested organizations at no additional charge for one year.
image
For more information, please get in touch with your Customer Success Manager, or raise a support ticket to express your interest!
Thanks
The Aura & Bloom Product Teams

improved

AuraDB Enterprise

AuraDS Enterprise

We are excited to announce that we have released V1Beta4 of our API. This new version brings some significant improvements and enhancements to our service and we want to ensure you are aware of the changes.
Please read the following carefully as there are a number of changes encompassing new endpoints, modifications to existing ones and a few breaking changes with V1Beta4
New functionality
This is new functionality that we’re bringing to V1Beta4. It’s not expected that these will cause issues and can be introduced at your convenience. We do , as always, recommend testing.
GET /instances/<instanceId>/snapshots/<snapshotId>
We have introduced this new endpoint to retrieve details of a specific snapshot associated with an instance.
Use selected snapshot of the source instance used when using overwrite endpoint
It is now possible to choose which snapshot of the source instance that will be used when overwriting an existing instance. To do this, include
source_snapshot_id
in the request body with
source_instance_id
when performing a
POST /instances/<instanceId>/overwrite
request.
Modified endpoints
We consider these changes to be those that you can adapt to at your discretion and timeline without disruption to existing functionality. Nevertheless, we recommend that you test your application to confirm your integration is working as expected.
Creating instances requires ‘cloud_provider’ to be supplied with
POST /instance
When making creating an instance the cloud provider must be specified as part of the request body. For example, to use GCP , add
cloud_provider:gcp
to the request body.
GET /instance/<instanceId>
Additional fields
memory
and
cloud_provider
are returned as part of the response.
Full instance details are returned in the request response when using the following endpoints and operations:
POST /instances/<instanceId>/pause
POST /instances/<instanceId>/overwrite
POST /instances/<instanceId>/restore
POST /instances/<instanceId>/resume
DELETE /instances/<instanceId>
POST /instances/<instanceId>/snapshots
When creating a snapshot, this endpoint now returns
snapshot_id
in the request response.
GET /instances
This endpoint now includes cloud provider information as part of the information in each instance.
Breaking changes
A breaking change is a change that may require you to make changes to your application in order to avoid disruption to your integration with the Aura API. The following are changes we consider breaking.
Content-Type header must be specified for all POST / PATCH requests
All POST/PATCH requests require the
Content-Type
header to be specified with the value
application/json
for example:
Content-Type:application/json
‘cloud_provider’ field moved in the JSON body response
When using GET /tenants the
cloud_provider
field has been relocated to each entry in the
instance_configurations
list.
We understand that these changes may require some modifications to your existing integration. To ensure a smooth transition to V1Beta4, we recommend reviewing your codebase and updating it accordingly to accommodate these changes. For more information please see Aura API Docs or go direct to our latest V1Beta4 swagger spec.
If you have any questions or need assistance with the migration, please don’t hesitate to reach out to our support team. We are here to help you throughout the process.
Thanks
The Aura Product Team

fixed

Browser.neo4j.io

This is a minor maintenance update with a number of small fixes.

fixed

Ops Manager

Patch 1.7.2 for Neo4j Ops Manager is now available to download.
This contains a small number of fixes which were not ready in time for the 1.7 release:
  • 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
We recommend that you apply this patch version to your implementation.
Load More