azuredatastudio: Profiler extension missing parameterized queries from ASP.NET Core + EF Core application

Hello, and thx for a wonderful new tool. I’m trying out the Profiler extension for SQL Operations Studio because some of my colleagues use Linux for .NET Core development, and this tool could be very helpful.

I outlined in an answer on Stack Overflow a way to use the Profiler for a very basic ASP.NET Core 2.1 + EF Core + Sql Server (docker or localdb), and got it to work nicely.

Now I’m trying to hook up to my actual ASP.NET Core 2.1.0 (with EF Core 2.1.0) application, but the important statements aren’t showing. I’m using Postman to hit my API with a simple GET of one value, but my profiler window only shows EventClass

• lougout
• rpc_completed twice
• login

all from the “Core .Net SqlClient Data Provider”. However, I was also expecting sql_batch_starting and sql_batch_completed or similar, with some SELECT queries. In fact, that’s the only events I’m after at the moment.

Some additional info:

• If (on my Windows machine) I use SQL Server 2016 Profiler to do the same trace, then I do see RPC:Completed events with exec sp_executesql N'SELECT TOP(1)... events containing my query.
• If (on my Windows machine) I use SSMS 2016 to drill into Management > Extended Events > Sessions > Profiler > package0.ring_buffer (which I guess is related?), then click to the XML, I do see a <data name="statement"> element with that same SELECT. It is contained in a rpc_completed event with a timestamp similar to the events that the Profiler in OpsStudio showed.

Surely the missing events are particular to my ASP.NET Core Web API application, but I can’t seem to find any relevant setting for this. I also am at a loss how to debug this further to provide you with a concise repro.

I would love to provide such a concise repro, but perhaps someone can point me in a good research direction?

Edit: see repro below.