title: Google Cloud CPU profiling not showing useful data
body: <p>After my application was running @ 400%+ CPU usage in a dockerised app, I decided to try using <a href="https://www.npmjs.com/package/@google-cloud/profiler" rel="nofollow noreferrer">@google-cloud/profiler</a>. The setup was easy enough but I am disappointed with what I see in the UI:</p>
  <p><a href="https://i.stack.imgur.com/7lxNW.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/7lxNW.png" alt="enter image description here" /></a></p>
  <p>As you can see, what is consuming the most resources, I can't seem to look into as there's no info about it. It's labelled as &quot;(external)&quot; &amp; <em>no file</em>. I am very new to Google Cloud CPU Profiler but it seems quite out of the box. My application is a multi-process one &amp; it is the child process' that are causing the high CPU load so I invoke the CPU profiler on the entry of these child process'</p>
  <p><strong>src/cluster/worker/index.js</strong></p>
  <pre class="lang-js prettyprint-override"><code>module.exports = async function() {
      try {
          await require('@google-cloud/profiler').start({
              projectId: process.env.GOOGLE_PROJECT_ID,
              serviceContext: {
                  service: process.env.GOOGLE_SERVICE || 'app',
                  version: process.env.GOOGLE_VERSION || '1.0.0'
              },
              // want to disable logging to the console
              logLevel: 0
          })
  
          ...
      } catch(err) {
          ...
      }
  }
  </code></pre>
  <p>There are many child process' running <em>(5 ish)</em> so could this be the issue? Also, when I select to view the history of the profile, I get this:</p>
  <p><a href="https://i.stack.imgur.com/etAZC.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/etAZC.png" alt="enter image description here" /></a></p>
  <p>As mentioned, I am new to Google Cloud &amp; CPU profiling in general so any help would be appreciated. Sadly, I cannot find any help in Google forums &amp; no one has raised any similar issues on the NPM package itself.</p>