Docs supported a workspace-based resource fed by the ASP.NET Core exporter connection string, with application logs expected in the classic trace and exception tables. The docs did not settle whether this exporter version writes those tables or a separate OpenTelemetry logs table. The resource was templated and never created.
- What worked
- Workspace-based linking and the connection-string model were clear enough to keep one regional store for the app.
- What got in the way
- Table mapping for structured-log export stayed ambiguous, which left the error-spike query's target table uncertain until further source checks.