[META 806] Create dashboard for runtime metrics

[elastic-apm-tech]

See meta issue for the description and details:

• Meta issue: Create dashboard for runtime metrics apm#806

[trentm]

@AlexanderWert Does https://github.com/elastic/kibana/pull/157724/files#diff-b0f9281b29e17f3aa9406728abcfb41a649247dcf8ea1fb0dc801ad4439cd783 already provide a dashboard for Node.js runtime metrics? That "nodejs.json" file includes \"sourceField\":\"nodejs.memory.heap.used.bytes\", for example.

Granted this doesn't handle any OTel SDK possible metrics.

[trentm]

Does https://github.com/elastic/kibana/pull/157724/files#diff-b0f9281b29e17f3aa9406728abcfb41a649247dcf8ea1fb0dc801ad4439cd783 already provide a dashboard for Node.js runtime metrics?

Answering my own question: Yes, it does. That dashboard is clearly there in my local-dev 8.10 kibana.

Alex, please correct me if I'm wrong.
Our goal for this issue for Node.js then is to:

1. add a dashboard for agentName === 'opentelemetry/nodejs' for default (or common) Node.js runtime metrics provided by the OTel JS SDK; and
2. possibly review what you have added with the nodejs.json dashboard.

(/cc @david-luna)

[david-luna]

Found the host-metrics Otel package is sending bad measurements for CPU utilization. Filed an issue
open-telemetry/opentelemetry-js-contrib#1718

[david-luna]

PR on apm-contrib repo to add memory metrics which could be reused in other languages

elastic/apm-contrib#84

[david-luna]

Alignment in process.cpu and system.cpu metrics at semconv level has been suggested
open-telemetry/semantic-conventions#563

[david-luna]

PR to fix process.cpu.time & process.cpu.utilization
open-telemetry/opentelemetry-js-contrib#1785

There is a PR to update process semconv which may change the attribute names. The PR above is prepared to receive the necessary changes