David Allen

In 4.0 you can selectively get pieces of JMX data on checkpointing like this (needs adjustment) ``` call dbms.queryJmx('neo4j.metrics:name=neo4j.neo4j.check_point.events') yield name, attributes return * UNION call dbms.queryJmx('neo4j.metrics:name=neo4j.florko.check_point.events') yield name, attributes...

@imatwawana could you have a look and see if there are any appropriate backport labels? Reviewed from our team side, just needs final check & merge - this is @tomglenn...

Investigation -- in Neo4j 4.2, most JMX metrics aren't enabled by default, so you already have to set `metrics.jmx.enabled=true` in order for Halin to work. As of Halin 0.15.0, the...

In 4.2 neo4j docs, some of these issues aren't really discussed. The configuration properties are mentioned, but not really what namespacing does, or with any examples (ref here: https://neo4j.com/docs/operations-manual/current/monitoring/metrics/expose/). Additionally,...

Currently mulling whether to try to detect & fix this situation within Halin, or whether the components that require JMX data should simply break with a message saying that the...

Related to #81 because it is a dynamically settable setting

This is an internal Neo4j error that affects halin's ability to get responses back, but it's not really something Halin can cope with. Question is more how the UI should...

I set up the data source this morning, ran into the same thing, but adding this support doesn't seem possible yet. The issue stems from GitHub itself; if the data...

Speculating that this is because one of the JMX metrics being used in mem.js is reporting "size on disk" and the other is reporting total bytes utilized.

@eastlondoner some of these are due to incorrect info coming back from the JMX level from Neo4j directly (Example cypher query used to generate some of this data here: https://github.com/moxious/halin/blob/47ae7fe26b1639bd222b569e2e685d4eb1d0a7ce/src/data/queries/jmx/storeSizes.js#L20)...