Continuous Integration Build Artifacts

docs/joularjx/print.html

@@ -296,6 +296,8 @@ <h2 id="license"><a class="header" href="#license">License</a></h2>
 <li><code>save-call-trees-runtime-data</code>: write runtime call trees power consumption in a CSV file. For each monitoring cycle (1 second), a new CSV file will be generated, containing the runtime power consumption of the call trees. The generated files will include timestamps in their names.</li>
 <li><code>overwrite-call-trees-runtime-data</code>: overwrite runtime call trees power data file, or if set to false, it will write new file for each monitoring cycle.</li>
 <li><code>application-server</code>: properly handles application servers and frameworks (Sprig Boot, Tomcat, etc.). Set <code>true</code> when running on application servers. If <code>false</code>, the monitoring loop will check if the JVM is destroyed, hence closing JoularJX when the application ends (in regular Java application). If <code>true</code>, JoularJX will continue to monitor correctly as the JVM isn't destroyed in a application server.</li>
+<li><code>vm-power-path</code>: the path for the power consumption of the virtual machine. Inside a virtual machine, indicate the file containing power consumption of the VM (which is usually a file in the host that is shared with the guest).</li>
+<li><code>vm-power-format</code>: power format of the shared VM power file. We currently support two formats: <code>watts</code> (a file containing one float value which is the power consumption of the VM), and <code>powerjoular</code> (a csv file generated by <a href="https://github.com/joular/powerjoular">PowerJoular</a> in the host, containing 3 columns: timestamp, CPU utilization of the VM and CPU power of the VM).</li>
 </ul>
 <p>You can install the jar package (and the PowerMonitor.exe on Windows) wherever you want, and call it in the <code>javaagent</code> with the full path.
 However, <code>config.properties</code> must be copied to the same folder as where you run the Java command.</p>

docs/joularjx/ref/configuration.html

@@ -187,6 +187,8 @@ <h1 id="configuration-properties"><a class="header" href="#configuration-propert
 <li><code>save-call-trees-runtime-data</code>: write runtime call trees power consumption in a CSV file. For each monitoring cycle (1 second), a new CSV file will be generated, containing the runtime power consumption of the call trees. The generated files will include timestamps in their names.</li>
 <li><code>overwrite-call-trees-runtime-data</code>: overwrite runtime call trees power data file, or if set to false, it will write new file for each monitoring cycle.</li>
 <li><code>application-server</code>: properly handles application servers and frameworks (Sprig Boot, Tomcat, etc.). Set <code>true</code> when running on application servers. If <code>false</code>, the monitoring loop will check if the JVM is destroyed, hence closing JoularJX when the application ends (in regular Java application). If <code>true</code>, JoularJX will continue to monitor correctly as the JVM isn't destroyed in a application server.</li>
+<li><code>vm-power-path</code>: the path for the power consumption of the virtual machine. Inside a virtual machine, indicate the file containing power consumption of the VM (which is usually a file in the host that is shared with the guest).</li>
+<li><code>vm-power-format</code>: power format of the shared VM power file. We currently support two formats: <code>watts</code> (a file containing one float value which is the power consumption of the VM), and <code>powerjoular</code> (a csv file generated by <a href="https://github.com/joular/powerjoular">PowerJoular</a> in the host, containing 3 columns: timestamp, CPU utilization of the VM and CPU power of the VM).</li>
 </ul>
 <p>You can install the jar package (and the PowerMonitor.exe on Windows) wherever you want, and call it in the <code>javaagent</code> with the full path.
 However, <code>config.properties</code> must be copied to the same folder as where you run the Java command.</p>