This session will provide an overview of the recently released Neo4j Ops Manager product for enterprise customers. We'll explore its use cases and features, as well as watch a demo and look at a product roadmap.
5. 5
Neo4j Ops Manager Categories
Architecture:
Provide a secure platform for administrative users to manage their Neo4j
installations, regardless of deployment modality, using a web interface.
Administration:
Make it simpler to perform administrative tasks in Neo4j.
Observability:
Provide an instant view of the status of managed Neo4j installations, a dashboard for
metrics, easy access to logs and audits with extensible alerting for offline monitoring.
Operability:
Schedule, monitor and review database operations.
Architecture
Operability
Observability
Administration
Neo4j pillar: Operational Trust
6. 6
Neo4j Ops Manager Architecture
Architecture
Operability
Observability
Administration
Neo4j installation host (1:n)
Admin User
Neo4j
NOM Server (single JAR)
Front end
NOM Agent
NOM persistence
Neo4j
Client API Agent API
Single JAR. Java 17.
Version 4.4.x or higher
14. Roadmap Summary - defining features
Q4 2022
(Planned)
Query Performance
H1 2023
Multi-user and SSO
Actionable Insight
Object Manager
Configuration Manager
H2 2023+
History and Audit
Activity Manager
Topology Management
Recommendations
15. Neo4j, Inc. All rights reserved 2021
What it is
● Capture the query execution information from
managed instances and store relevant canonical
data in NOM
● Allow drill through from metrics to a focussed
view of queries
● Provide summary view query execution to
quickly identify problem candidates
● Provide a list of all query executions with filter,
sort and search capability
● Data prepared to remove customer data
(canonical form) and only include relevant query
executions as defined by the administrator
What it is for
● To allow administrators to review
query execution data with sort,
search and filter in the NOM UI to
quickly find the queries of interest
● To provide a performance summary
of query execution to allow quick
identification of problem queries for
a given period
Query Performance (1.3, December 2022)
16. Neo4j, Inc. All rights reserved 2021
What it is
● Support users in Ops Manager Security
Manager who are externally authenticated
(SSO) for the managed DBMSs
● Allow administrators to connect to Ops Manager
using SSO credentials
● Allow multiple users to connect to Ops Manager,
each having their own defined authorisations
● Allow users to be grouped by tenant in Ops
Manager (company, department, project) to
allow Ops Manager to manage multiple DBMSs
where isolation is required
What it is for
● Most Enterprise customers will have SSO
for their Neo4j DBMS installations. Provide
the ability in NOM to manage SSO users in
the managed DBMSs
● Extend NOM to support both multiple NOM
users and tenants with a NOM installation
(projects/departments) to allow a single
NOM to manage multiple DBMSs and
provide Administrative isolation
● Allow NOM users to connect using SSO
Multi-user and SSO (H1 2023)
17. Neo4j, Inc. All rights reserved 2021
What it is
● Provide a framework which allows the
definition and monitoring of measures,
thresholds, conditions, status and alerts
● Allow this framework to support actionable
insight on topology, metrics and logs for the
managed DBMSs
● Provide a set of default monitors as well as
allowing user-defined monitors
● Allow an action on an alert being triggered
to notify a remote management system via
one or more protocols
What it is for
● Allow the administrator to
define thresholds and alert
conditions on metrics, logs
and other parts of the
managed DBMSs
● Allow a triggered alert to be
sent as a notification event via
one or more protocols for
offline alerting
Actionable Insight (H1 2023)
18. Neo4j, Inc. All rights reserved 2021
What it is
● Provide a view of the schema of each
database with the managed DBMSs
● To include labels, relationship types,
property names, constraints and
indexes for each database
● Run scheduled jobs to gather statistics
on these objects to augment the data
provided by the DBMS
● Other than schema definitions, Ops
Manager will never store any user data
What it is for
● Allow the Administrator to view
the schema elements within the
managed databases, including
labels, relationship types,
property names, constraints and
indexes
● Periodically capture and store
statistics on these elements for
information
Object Manager (H1 2023)
19. Neo4j, Inc. All rights reserved 2021
What it is
● Provide graphical view of current
configuration of an instance
● When managing a cluster, allow
side-by-side instance view with the option
to highlight differences
● Allow changing of dynamic settings
through the UI, with option to apply to all
cluster instances concurrently
● [Future] allow setting of static settings in
neo4j.conf with agent controlled restart
What it is for
● Allow an Administrator to quickly view
the configuration of an instance
● Allow the Administrator to set dynamic
(and, in the future, static) configuration
values through a simple user interface
● Support clusters, allowing cross-server
comparison and setting configuration
values on the cluster in one action
● Guided configuration advisories, i.e.
setting up SSL connections
Configuration Manager (H1 2023)
20. Neo4j, Inc. All rights reserved 2021
What it is
● As well as providing a current view of the
DBMS, also record a history of changes to the
managed DBMS
● This should be a record of changes made
through NOM, or of detected changes in the
managed DBMS
● History will be provided for topology (DBMS,
instance, database), security, configuration and
schema as these features become available
● History will be viewable, and can be filtered,
sorted and searched, with an ability to export the
data
What it is for
● Administrators may wish to
see a record of what changes
were made to a DBMS, when
and by whom
● Provide a history of detected
changes, or a record of
changes in NOM, to allow an
audit to be run by an
Administrator
History and Audit (H1 2023)
21. Neo4j, Inc. All rights reserved 2021
What it is
● Provide a view of the currently
connected users on a managed DBMS
● Provide a view of the currently
executing queries on a managed
DBMS
● Provide a cluster view where the
managed DBMS is clustered
● Allow the administrator to be able to
cancel running queries and disconnect
users
What it is for
● Provide visibility on currently
connected user transactions
and query activity
● Allow a view across all
servers in a cluster
● Allow queries to be cancelled
and transactions to be
terminated
Activity Manager (H2 2023+)
22. Neo4j, Inc. All rights reserved 2021
What it is
● Provide better visualisation and
management of the topology of the
managed DBMSs
● Support newer features such as composite
databases and autonomous cluster
● Support various topology elements
including
○ Host/Agent
○ Instance (or cluster server)
○ Database (including composite)
○ Cluster (Causal & Autonomous)
configuration
What it is for
● Allow easier management of
topology though the NOM
user interface for the
Administrator
● Includes management of
clusters, databases and
composite databases (Fabric)
Topology Management (H2 2023+)
23. Neo4j, Inc. All rights reserved 2021
What it is
● Provide a framework to allow recommendations
to be defined using metadata
● Provide a standard set of recommendations and
allow user-defined recommendations
● Recommendations based on actionable insight
(metrics and logs) as well as detected topology,
schema and security
● Ensure each recommendation is explainable,
detailing the reasons for the recommendation
What it is for
● Provide the Administrator with
recommendation for improving the
performance or setup of the managed
DBMSs
● An extensible framework where
additional advice can be loaded as it
becomes available
● To include recommendations on
configuration, object (schema), query
performance and potentially modelling
Recommendations (H2 2023+)