The Details and Notes (only read this for the full internal details or if you have a problem):
This website is experimental and might be withdrawn without notice.
The graphs make use of the Google Charts library, so you need to be on the Internet for them to work.
Please report any problems and mistakes so they can be fixed or good ideas.
Saving your graphs:
You can save the graphs with your Browser's "Save as" function.
It will save the .html file along with all the data and configuration to your local computer.
nmon files:
Only files ending in ".nmon" are accepted.
File maximum size is ~64 MB but above 20 MB uploading can take a minute or two. Be patient and watch the spinning wheel on the Browser tab.
For rapid upload and graphing keep your nmon data files to less than 1000 snapshots or the nmonchart will take longer to display (as in a few seconds) but should still work.
Limitation: If your system has more than 150 disks then only the first 150 are graphed.
But nmonchart does offer the Top 15 Busy Disks graph (see button on the top right) that is across ALL the disks in the file.
Multiple files are not allowed. How could it return the graphs for multiple files in one go?
Problems:
Note: nmon files are simple text in a comma separated value (CSV) format - you can edit them with the "vi" editor or similar.
If you end up with a blank screen or buttons failing to produce graphs we have a data or nmonchart issue. Please email me the filename and I will investigate.
Perhaps, the "nmon file" is not in nmon format at all. For example, it is a topas format file or vmstat output or empty!
If there is only one data point it will work but look odd.
If nmon was killed, then the last output line might not be complete. Check with: tail filename.nmon
You corrupted the nmon file somehow, perhaps badly FTPing the file, compressed it or fiddled about with it.
If you get "filename, already exists" errors, rename your file.
If you get a red error message, then there are problems in the data or resources changed while nmon was running like disks added or removed.
This may require manual editing of the nmon file. It can be done but it is not trivial.
Making this better for other nmon users:
Feedback and comments are welcome to Nigel Griffiths (nigelargriffiths@hotmail.com)
Possible next steps include allowing zip or gzip files. As nmon files compress very well, this reduces the upload time.
Security and confidential data
nmon files do not contain any personal, private, or sensitive data.
They do include the server Serial number, IP addresses, perhaps file system mount point names might reveal some software on the server.
If you don't want to share those details with Mr nmon then use the "sed" command to remove them from the file.
To avoid problems, replace them with "ABCDEFG" or "999.999.999". Below the IP Address starts with "192.168.10"
Example: cat abc.nmon | sed 's/219A297/ABCDEFG/g' | sed 's/192.168.10/999.999.999/g' >abc_safe.nmon
Uploaded files are removed on a regular basis.
Mr_nmon may look at these uploaded files to look for common problems and develop this tool to make recommendations or analyse them with AI tools.
The nmon files will not be shared with anyone else.