Hello Angelo,
Per the documentation, seems that you can:
https://jazz.net/wiki/bin/view/Deployment/CLMServerMonitoring

Hi Angelo,
I guess I found what you had mentioned:
Following the page https://jazz.net/wiki/bin/view/Deployment/CLMServerMonitoringAgentTechPreview, when you reach the item "for CLM 4.0.6x Server Monitoring Agent Tech Preview from here. to be updated"  it is pointing to a page with "Access Denied".
Seems that as version CLM 4.0.6 does not have official support, they denied the access.

Anyway, I would try to do a fresh install of CLM Monitoring using the CLM 5.0.1 and start it. Then, I would try to access the CLM 4.0.6 server to be monitored, however starting it using the options to enable the plugin :

https://jazz.net/wiki/bin/view/Deployment/JazzMonitoringThroughJMX#Option_1_JMX_not_secured

Microsoft Windows:
   rem for JMX monitoring
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote=true
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.port=1099
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.ssl=false
   set JAVA_OPTS=%JAVA_OPTS% -Dcom.sun.management.jmxremote.authenticate=false

If CLM 4.0.6 already has the code embedded on it, when starting the server with these attributes it may be able to communicate with the CLM Monitoring.
But again, just an idea. I have not tried it by myself yet.
And it may produce unpredictable results, as for version 4.0.6 it is not officially supported.

Cheers,
Isabel