Remaining GC capacity chart
Remaining GC capacity is the measurement of Application Component uptime that is not spent on garbage collection (GC).
Turbonomic collects GC data from Application Components discovered by Applications and APM targets, and then uses that data to calculate remaining GC capacity. When you set the scope to one or several Application Components, the capacity that Turbonomic calculated displays in the Remaining GC Capacity chart.
The chart shows average and peak/low values over time. Use the selector on the chart to change the time frame.
An empty chart could be the result of delayed discovery, target validation failure, unavailable data for the given time frame, or an unsupported Application Component (see the next section for a list of supported Application Components).
Supported application components
Data is available in the Remaining GC Capacity chart for Application Components discovered via the following targets:
| Target | Supported application components |
|---|---|
| AppDynamics | Java applications, .NET |
| Dynatrace | Java applications |
| Instana | Java applications |
| JBoss | Java applications |
| JVM | Java applications |
| New Relic | Java applications, Node.js |
| Tomcat | Java applications |
| WebLogic | Java applications |
| WebSphere | Java applications |
Effect on heap resize actions
Turbonomic generates Heap resize actions if an Application Component provides Heap and Remaining GC Capacity, and the underlying VM or container provides VMem. These actions are recommend-only and can only be executed outside Turbonomic.