Shipper output producing events that get rejected with illegal_argument_exception

[fearful-symmetry]

File this under "issues I run into while hacking on elastic/elastic-agent-shipper#185"

metricbeat events sent to elasticsearch by the shipper are getting rejected with this error:

{"log.level":"debug","@timestamp":"2023-01-27T23:29:00.174Z","message":"Failed to add items: struct { Type string \"json:\\\"type\\\"\"; Reason string \"json:\\\"reason\\\"\"; Cause struct { Type string \"json:\\\"type\\\"\"; Reason string \"json:\\\"reason\\\"\" } \"json:\\\"caused_by\\\"\" }{Type:\"mapper_parsing_exception\", Reason:\"failed to parse\", Cause:struct { Type string \"json:\\\"type\\\"\"; Reason string \"json:\\\"reason\\\"\" }{Type:\"illegal_argument_exception\", Reason:\"Limit of mapping depth [20] has been exceeded due to object field [fields.data.system.Kind.StructValue.data.cpu.Kind.StructValue.data.idle.Kind.StructValue.data.norm.Kind.StructValue.data.pct.Kind]\"}}","component":{"binary":"shipper","dataset":"elastic_agent.shipper","id":"shipper-default","type":"shipper"},"service.name":"shipper","ecs.version":"1.6.0","log.logger":"elasticsearch-output","log.origin":{"file.line":108,"file.name":"elasticsearch/output.go"},"ecs.version":"1.6.0"}

I suspect this is an issue with the beats shipper out, as right now the shipper itself isn't doing much to actually modify events.

[botelastic]

This issue doesn't have a Team:<team> label.

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!