Why are some JMX measures not written to Tsd file, even though they can be monitored with Performance Explorer?
If the JMX measures can be monitored in Performance Explorer during a loadtest; but are completely missing from the generated Tsd files, then the following issue may explain this behaviour.
JMX measure name's consist of the MBean name and the Attribute name, and as such they can end up being very long.
SilkPerformer imposes a limit of 256 characters for measures that can be written to Tsd file. Any measure names that exceed this limit can still be viewed in Performance Explorer, but will not be written to the Tsd file.
A Change Request (41689) has been logged for this issue to be addressed in a future versions of SilkPerformer.
In the meantime to resolve the problem, implement the following workaround:
1. Save and Close your Performance Explorer Workspace (.pew) file.
2. Create a backup copy of the PEW file.
3. Open the .pew file with a text editor such as Notepad.
4. Search for the measure(s) that do not work because the measure names are too long.
5. Edit the "Path" attribute of the affected measures; choosing a shorter name for the middle section. Please note: it is very important that you do not change the folder or attribute name.
6. The shorter name you assign will be displayed in the monitor tree section of Performance Explorer and will allow the JMX measures to be written to TSD file.