APM Server transport error (400): Unexpected APM Server response APM Server accepted 0 events in the last request Error: Problem validating JSON document against schema: I[#] S[#] doesn't validate with "metricset#" I[#] S[#/allOf/0] allOf failed

Describe the bug APM works well when running my app without docker but once i start the app in docker I get an error:

APM Server transport error (400): Unexpected APM Server response
APM Server accepted 0 events in the last request
Error: Problem validating JSON document against schema: I[#] S[#] doesn't validate with "metricset#"
  I[#] S[#/allOf/0] allOf failed
    I[#/samples/system.process.cpu.total.norm.pct/value] S[#/allOf/0/properties/samples/patternProperties/%5E%5B%5E%2A%22%5D%2A$/properties/value/type] expected number, but got null
  Document: {"metricset":{"timestamp":1548853260277000,"tags":{"hostname":"96d3f45afe38","env":"development"},"samples":{"system.cpu.total.norm.pct":{"value":null},"system.memory.total":{"value":2096164864},"system.memory.actual.free":{"value":1151217664},"system.process.cpu.total.norm.pct":{"value":null},"system.process.memory.size":{"value":1100959744},"system.process.memory.rss.bytes":{"value":190550016}}}}

To Reproduce Steps to reproduce the behavior:

1. Use this config ’ const apmConfig = { serviceName: process.env.APP_NAME, serverUrl: process.env.APM_SERVER, secretToken: process.env.APM_TOKEN, logLevel: ‘info’, } ’
2. Then call ’ const apmObject = require(‘elastic-apm-node’).start(apmConfig); ’
3. Then do ‘’
4. See error

APM Server transport error (400): Unexpected APM Server response APM Server accepted 0 events in the last request Error: Problem validating JSON document against schema: I[#] S[#] doesn’t validate with “metricset#” I[#] S[#/allOf/0] allOf failed I[#/samples/system.process.cpu.total.norm.pct/value] S[#/allOf/0/properties/samples/patternProperties/%5E%5B%5E%2A%22%5D%2A$/properties/value/type] expected number, but got null Document: {“metricset”:{“timestamp”:1548853260277000,“tags”:{“hostname”:“96d3f45afe38”,“env”:“development”},“samples”:{“system.cpu.total.norm.pct”:{“value”:null},“system.memory.total”:{“value”:2096164864},“system.memory.actual.free”:{“value”:1151217664},“system.process.cpu.total.norm.pct”:{“value”:null},“system.process.memory.size”:{“value”:1100959744},“system.process.memory.rss.bytes”:{“value”:190550016}}}}

Expected behavior Expect the apm to work well with docker as it works without me using it

Environment (please complete the following information)

• OS: Mac Osx
• Node.js version: v10.11.0
• APM Server version:
• Agent version: 2.5.0

How are you starting the agent? (please tick one of the boxes)

• Calling agent.start() directly (e.g. require('elastic-apm-node').start(...))
• Requiring elastic-apm-node/start from within the source code
• Starting node with -r elastic-apm-node/start

Additional context Add any other context about the problem here.

• Agent config options

  Click to expand

  replace this line with your agent config options
  

• package.json dependencies:

  Click to expand

  replace this line with your dependencies section from package.json
  

[Qard]

On further investigation, I found there was a bug. I’ve published 2.5.1, which should fix this.

[Guik]

Same issue for me.

I’m using up to date alpha version official image: docker.elastic.co/apm/apm-server:7.0.0-alpha2 docker.elastic.co/elasticsearch/elasticsearch:7.0.0-alpha2

Is apm-agent-nodejs compatible with alpha2 ?

Edit: I downgraded to 6.6.0 I have the same behavior.