I have a NodeJS stack pushing logs and APM info to Logstash and then to elasticsearch/kibana hosted on Elastic Cloud. For some reason, the APM trace is missing the full trace. At the very least, I'd like to see MongoDB instrumentation (in the below example screenshot, that request is making multiple requests to MongoDB that should be visible). I'll post as much context as I think is relevant, but please let me know if there is any config/setup that would be helpful to see. I have a hunch that the issue is related to using Parse Server which isn't natively supported by Elastic APM but it's just a layer over Express and I've seen other APM (including DataDog and New Relic) instrument the requests in their entirety out of the box.
If you are using mongodb@5, please let me know. That'll help me prioritize, so I can see about getting a fix out for this this week.
If that isn't the issue, then the next step would be to get a full trace-level log: configure the elastic-apm-node agent with logLevel: 'trace'), run your app, send us/me the full output to look for issues. A common issue is if elasticApm.start(...) is called too late -- after a DB client driver module has already been require()d.