Data available on connection to a running application
When connecting the Health Center to a running application, the data available for the client to display can vary for a number of reasons.
The data available to the Health Center client on connection to a live source varies depending on the following conditions:
- If this is the first Health Center client that has connected to a particular live source since it was started.
- The type of runtime environment, for example Java™ or Node.js.
- The version of the Java Virtual Machine (JVM) or Node.js runtime engine that is being monitored.
- The version of the monitoring agent used (see the section on platform requirements for the agent in: Platform requirements).
For example:
- Health Center client A connects to live source L.
- Health Center client A uses some data from live source L and then disconnects.
- Health Center client B connects to live source L.
Data available on first Health Center client connections to a live source
Runtime environment version | Available data |
---|---|
|
As much historical data as fits in the monitoring agent's buffer, up to the current time. |
|
Data from the time when the live source was started until the current time. |
Data available on subsequent Health Center client connection to a live source
Runtime environment version | Available data |
---|---|
|
As much historical data as fits in the monitoring agent's buffer, up to the current time, which has not already been used by a Health Center client.
Note: In the profiling perspective, some method names might not display immediately.
|
|
All data from the time when the live source was started until the current time, which has not already been used by a Health Center client.
Restriction: Method names are available only for classes loaded since the previous Health Center client was disconnected.
|