New feature requirement: actual file sizes of indexes in jmx status report

[ghost]

@pwin commented on Oct 2, 2018, 12:30 PM UTC:

What is the problem

I had a paradoxical extremely large index file (ngram.dbx) occur in exist-db v2.1 but did not "see" this developing from the data in e.g. monex

What is the suggestion

proposal for jmx information to be extended to include actual size of the index files (in addition to the memory footprint of the index caches)

This issue was moved by duncdrum from eXist-db/exist#2184.

[duncdrum]

Hi Peter, we ll have to touch upon the jmx parser code that ships with monex for the release of 5.0.0 so there is a good chance that this might make it into an update of monex soon.

I think the feature request makes sense and would be a good addition to the information currently displayed by monex.