Perhaps you already know this, but... You can monitor free space in cont-repo through the UI.
If you have a cluster go to the global menu -> Cluster -> Content Storage Stand-alone go to global menu -> Summary -> system diagnostics -> System I suppose if you wanted to you could Pull the nifi.properties file periodically w/ a getFile (set "keep source file" to "true"), and you could evaluate the nifi.properties that way? Although a little odd... but it could be done nonetheless :) On Aug 14, 2024 at 11:26 AM -0400, Mike Thomsen <[email protected]>, wrote: I can open the nifi.properties file manually. I was just wondering if there was a singleton object or something that held its values somewhere. On Wed, Aug 14, 2024 at 11:25 AM Mike Thomsen <[email protected]> wrote: The location info for the content repositories so I can monitor the free space. Our use case is a bit of a weird one driven by us having to hack around budget issues that aren't aligned with the expectations on the raw volume and size of the data these nodes will handle. On Tue, Aug 13, 2024 at 8:20 AM Bryan Bende <[email protected]> wrote: Processors should not know about nifi.properties. What information are you trying to get? On Tue, Aug 13, 2024 at 7:52 AM Mike Thomsen <[email protected]> wrote: Is there a 1.X and 2.X safe way to get the configuration data from nifi.properties? Thanks, Mike
