Deprecation Notice: If you are upgrading from N|Solid 2.x, here are the need-to-know steps for migrating to N|Solid 3.x. * N|Solid Storage has been eliminated, and its functionality is provided by the N|Solid 3.x Console server. Attempting to connect an existing N|Solid Storage instance to a N|Solid 3.x Console will not work unless the storage instance is running in relay mode. * Many of the settings and environment variables from N|Solid Storage are available in the 3.x N|Solid Console; substitute CONSOLE for STORAGE in the variable name. View the Networking documentation for specific settings. * Loading a N|Solid 3.x Console server with the same configuration as a N|Solid Storage instance will load some of your existing assets and metrics history, but Heap Snapshots will need to be accessed directly from your storage device. The default location has changed from ~/.nsolid-storage to ~/.nsolid-console. * The N|Solid 2.x Runtime is compatible with the N|Solid 3.x Console, but not all functionality will be available. * The environment variables used to configure N|Solid Runtime are the same as with N|Solid 2.x, however you must provide a valid license during any operation, either via a connection to an N|Solid Console, or by providing a License Token directly. Read the Configuration guide for more information. * The nsolid-cli syntax and behavior have changed from 2.x, be sure to read the Command Line Interface documentation if you use this functionality.
Clean up resources (Snapshots, Profiles) for N|Solid 2.x
By default, all resources generated by N|Solid are saved to the folder
~/.nsolid-storage/data/assets/ unless you specify the
dir setting in the
[data] section of your N|Solid Storage configuration file. In this folder you will find any CPU profiles and heap dump snapshots taken. Those files and folders can safely be deleted.
But take into account that it will take several minutes for the console to remove the files from the UI. In the current interface, if you try to load a deleted snapshot, it will get stuck on the loading screen.
Automatically clean up and limit assets retention
There is also the option of configuring N|Solid to automatically clean these resources, in order to accomplish this, you can set the following
environment variables or add the corresponding options at the
[assets] section of your N|Solid Storage configuration file to make N|Solid Storage automatically clean up and limit asset retention:
NSOLID_STORAGE_ASSETS_CLEANUP_MINUTESor configuration option
cleanupMinutes: This configures how often the asset files are cleaned up - the oldest asset files are deleted to ensure constraints below are met.
NSOLID_STORAGE_ASSETS_MAX_ASSETSor configuration option
maxAssets: This sets the maximum number of assets to retain at the resources folder.
NSOLID_STORAGE_ASSETS_MAX_ASSETS_MBor configuration option
maxAssetsMb: This limits the maximum size of all assets to keep, that way you can control the maximum amount of disk storage N|Solid will use for those assets.