Greg here from the video 
Do i need to configure the APM to send Database statements?
In case you turn on the agent with the UseAllElasticApm method from Elastic.Apm.NetCoreAll you don’t need to configure database monitoring, we turn on everything for you. Now 1 reason you don’t see database calls can be related to this. Back in the alpha and pre-release days (that’s when the video you referenced was created) we had the UseElasticApm both in the Elastic.Apm.AspNetCore and also in the Elastic.Apm.All namespace. The 1. only turned on ASP.NET Core monitoring, the 2. turned on everything (ASP.NET Core, outgoing HTTP tracing, and database tracing, etc.) It turned out that having the same method name is very confusing so we made a change: Now there is the Elastic.Apm.NetCoreAll package with the Elastic.Apm.NetCoreAll (previously Elastic.Apm.All) namespace and it has a UseAllElasticApm method - an example usage can be seen here. Hopefully this naming is more clear: this is the one that turns on everything (including db monitoring). So my 1. idea: Do you use this method - (so UseAllElasticApm from Elastic.Apm.NetCoreAll)? If not please make sure you switch to this.
Does the APM not work with other connectors besides microsofts entity framework core?
We target EF Core and we listen to events that are sent by EF Core itself, the connector should not matter. On the other hand we only tested with SQLite and MS SQL. In theory all connectors should work, because the events we use are not related to the connectors. If this is not the case I’m happy to look into a specific setup and figure out why it does not work.
If so, are there plans to expand the APM to work with other connectors?
In case it does not work, I’d take a look at it - In case you have a reproducer that I can just start that would be super helpful.
But first let’s see if it really does not work.
Hope this helps,
Greg