Bump elastic-apm-node from v3.10.0 to v3.14.0

[trentm]

Summary

Bumps the version of the elastic-apm-node dep used for self-APM of Kibana.

Changelog: https://www.elastic.co/guide/en/apm/agent/nodejs/current/release-notes-3.x.html
Notably:

• Adds apm.addMetadataFilter(fn) that can be used for PII filtering
• Improves communication with APM server to not be pathological if APM
  server is down for extended period of time and load is high.
• Fixes bugs in data for the Dependencies and Service Map in the APM
  app.
• The APM agent now collects cloud metadata.

For maintainers

• This was checked for breaking API changes and was labeled appropriately

/cc @joshdover @tylersmalley This adds the feature requested in elastic/apm-agent-nodejs#1916 so that metadata could now be filtered for PII there. I don't know if there is any urgency there (e.g. to try to get it in before 7.13 FF).

[trentm]

@elasticmachine merge upstream

[trentm]

@elasticmachine merge upstream

[trentm]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: c97a0c2
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💚 Build #122165 succeeded e1055f5
• 💚 Build #121556 succeeded a96980a
• 💚 Build #120708 succeeded 2ecc3f8

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @trentm

[mshustov]

Adds apm.addMetadataFilter(fn) that can be used for PII filtering

According to https://www.elastic.co/guide/en/apm/server/current/metadata-api.html#metadata-schema
Metadata includes user and account data from now on. Are they always collected? If so, the Kibana Core team has to address it in a follow-up PR.

[elasticmachine]

Pinging @elastic/kibana-core (Team:Core)

[joshdover]

@kobelb Do you think we could consider backporting this to the 7.13 branch as a bug fix? It addresses some performance issues that we'd like to see fixed for rolling this instrumentation out more widely.

[kobelb]

@kobelb Do you think we could consider backporting this to the 7.13 branch as a bug fix? It addresses some performance issues that we'd like to see fixed for rolling this instrumentation out more widely.

If it's a safe bugfix, backport away :)

[kibanamachine]

💔 Backport failed

Status	Branch	Result
❌	7.13	Commit could not be cherrypicked due to conflicts
❌	7.x	Commit could not be cherrypicked due to conflicts

To backport manually run:
node scripts/backport --pr 97509

[trentm]

Metadata includes user and account data from now on. Are they always collected? If so, the Kibana Core team has to address it in a follow-up PR.

Currently the Node.js APM agent:

• does NOT collect and set metadata.user (https://github.com/elastic/apm-nodejs-http-client/blob/master/index.js#L1007-L1081)
• does by default collect metadata.cloud.account (https://github.com/elastic/apm-agent-nodejs/tree/master/lib/cloud-metadata/). All metadata.cloud.* collection can be turned off with a cloudProvider: 'none' config if wanted.

This version of the agent added addMetadataFilter() because of @dover's request at elastic/apm-agent-nodejs#1916

So, yes, there should be a PR to filter:

• metadata.cloud.account (or turn off metadata.cloud.* collection entirely)
• metadata.user (in case a future node.js apm agent version adds collection of that)
• metadata.process.{args,title}