APM dotnet 1.1.2 error validating JSON document against schema: I[#] S[#] doesn't validate with \"metricset#\

Kibana version:
7.4.0 [Cloud]

Elasticsearch version:
7.4.0 [Cloud]

APM Server version:

APM Agent language and version:
dotnet 1.1.2

Browser version:

Original install method (e.g. download page, yum, deb, from source, etc.) and version:
7.0.0 -> 7.2.0 -> 7.4.0 through deb

Fresh install or upgraded from other version?
7.0.0 -> 7.2.0 -> 7.4.0 through deb

Is there anything special in your setup? For example, are you using the Logstash or Kafka outputs? Are you using a load balancer in front of the APM Servers? Have you changed index pattern, generated custom templates, changed agent configuration etc.
NGINX reverse proxy in front of APM Server and between APM Server and Logstash server

Description of the problem including expected versus actual behavior. Please include screenshots (if relevant):

We have an issue with our APM dotnet agents (1.1.2) hosted on AWS Lambda which do not seem to collect the system.cpu.total.norm.pct information in a proper format. This is causing a lot of errors in the application and also in the APM-server (7.4.0) logs.

Provide logs and/or server output (if relevant):
2019-11-06T11:30:46.789+0100 ERROR [request] middleware/log_middleware.go:74 data validation error {"request_id": "93fe9539-7408-4f55-be5a-f988482ee59b", "method": "POST", "URL": "/intake/v2/events", "content_length": 2249, "remote_address": "", "user-agent": "elasticapm-dotnet/1.1.2 System.Net.Http/4.6.27909.0 .NET_Core/2.1.12", "response_code": 400, "error": "error validating JSON document against schema: I[#] S[#] doesn't validate with "metricset#"
I[#] S[#/allOf/5] allOf failed
I[#/samples/system.cpu.total.norm.pct/value] S[#/allOf/5/properties/samples/patternProperties/%5E%5B%5E%2A%22%5D%2A$/properties/value/type] expected number, but got string [{"metricset": {"samples":{"system.memory.total":{"value":649019392.0},"system.memory.actual.free":{"value":440369152.0},"system.process.memory.size":{"value":12418158592.0},"system.process.memory.rss.bytes":{"value":137818112.0},"system.cpu.total.norm.pct":{"value":"NaN"},"system.process.cpu.total.norm.pct":{"value":0.56391401439108568}},"timestamp":1573036126515048}}]"}

Thanks for reporting, this seems like a bug to me - opened an issue to confirm. In the meantime, you could consider disabling metrics using one of these approaches.