Skip to content
Mike Tunnicliffe edited this page Aug 18, 2015 · 10 revisions

Find below some possible problem scenarios and corresponding diagnostic steps.

Checking Node Application Metrics has started

By default, a message similar to the following will be written to console output:

[Fri Aug 14 15:02:39 2015] com.ibm.diagnostics.healthcenter.node INFO: Node Application Metrics 1.0.0.201507150904 (Agent Core 3.0.4.201507150904)

No profiling data present for Node.js applications

Method profiling data is not collected by default.

If collection is enabled, an absence of method profiling data from a Node.js application could be caused by the type of tasks that are being run by your application -- it may be running long, synchronous tasks that prevent collection events from being scheduled on the event loop.

If a task uses the Node.js thread exclusively then shuts down the Node.js runtime environment, the Health Center agent may not get the opportunity to obtain any profiling data. An example of such an application is the Octane JavaScript benchmark suite, which loads the CPU continuously rather than dividing the load across multiple units of work.

Clone this wiki locally