Application Insight Dashboard for tracking per production project errors.

Thank you Bharath for the new resources; I will explore them. While I do that, could you recommend a top-tier AI assistant I can use in parallel?

Hello Deepika, you can absolutely build a single dashboard that shows error-breakdowns for multiple “production” projects. You really have two flavors of approach:

1. Multi-resource (one App Insights resource per project)
2. Single‐resource with a project identifier in your telemetry

— Let me walk you through both and then show you how to pin a pie chart for each project onto one Azure dashboard.

1. Multi-resource approach

• Create (or use) one App Insights instance per project.

• Hook each app’s SDK (or agent) to its own AI resource.

• Point them all at the same Log Analytics workspace if you like central management (optional, but nice for querying).

Once that’s set up, go build a Log-Analytics-based tile:

• Azure Portal → your Azure Dashboard → Edit → + Add tile → Logs

• Choose your Log Analytics workspace (that holds all your AI tables)

• Paste a query like:

union

  app('ProjA-AI-Name').exceptions,

  app('ProjB-AI-Name').exceptions,

  app('ProjC-AI-Name').exceptions

| where timestamp > ago(1d)

| summarize ErrorCount = count() by appName

| render piechart

• Customize time range (say “Last 24 hours”), give it a title, hit “Pin to dashboard.”

That gives you one pie chart with slices per project. If you want separate pie charts per project, just repeat the same but query each app individually and pin three separate tiles.

2. Single-resource + custom property

If you’re already sending telemetry from multiple projects into the same AI resource, you need to tag each error with a “Project” dimension so you can group by it. In .NET for example:

TelemetryClient telemetry = new TelemetryClient(...);

var props = new Dictionary<string,string> { ["ProjectName"] = "MyProjectA" };

telemetry.TrackException(ex, props);

Then in Logs:

exceptions

| where timestamp > ago(1d)

| summarize ErrorCount = count() by tostring(customDimensions.ProjectName)

| render piechart

Pin that query to your dashboard, and you’ll get a pie chart that splits by the ProjectName dimension.

Once you have your piecharts pinned, you can:

• Resize & arrange them on a single Dashboard

• Set auto-refresh (e.g. every 5 mins)

• Share the dashboard (make sure folks have at least Reader on the AI resources)

Use Application Insights Workbooks for more interactive multi-tile, multi-project layouts. Workbooks let you parameterize the project name, show tables, time series, maps, etc., all in one living report.

Hope this helps! Thanks.

Reference links for steps above:

• Create an Azure portal dashboard

• Pin Logs queries as tiles

• Multi-resource Kusto union syntax

• Custom dimensions in App Insights SDK

• Application Insights Workbooks overview

can we create dashboard for azure app insight errors from multiple .net core production projects?

Yes. A single Azure dashboard can show Application Insights error KPIs from multiple projects, even across subscriptions and resource groups. Use a combination of Metrics and Logs charts pinned to a shared Azure portal dashboard.

Below is one concrete way to get a per‑project pie chart of production errors.

1. Model “project” and “environment” in telemetry
   • Ensure each app sends telemetry with fields that distinguish:
     • Project (for example, cloud_RoleName, operation_Name, or a custom dimension)
     • Environment (for example, releaseStage with values like Production, Staging, Local).
   • All data can still go to one Application Insights resource, as in the current setup.
2. Build a Logs query that groups errors by project
   • In the Azure portal, open the existing Application Insights resource.
   • Under Monitoring, select Logs.
   • Start from the exceptions table and summarize by project and environment. For example (adapt to actual fields):

      exceptions
      | where customDimensions.releaseStage == "Production"   // production only
      | summarize count() by Project = cloud_RoleName
      | sort by count_ desc
      | take 10
   

   • Run the query to validate results.
3. Render as a pie (or doughnut) chart
   • In the Logs window, select Chart.
   • Choose Doughnut (or Pie) as the visualization to get a per‑project slice of production errors, similar to the example image.
4. Pin the chart to a shared Azure dashboard
   • In the Logs window, select the pin icon to Pin to dashboard.
   • Choose an existing dashboard or create a new one dedicated to production error KPIs.
   • The chart is now a tile on that dashboard.
5. Create multiple tiles if needed
   • Repeat the process with variations of the query, for example:
     • One doughnut per environment (releaseStage) for a single project.
     • One doughnut per project filtered to Production only.
   • Each query result can be pinned as its own tile, then arranged on the dashboard canvas.
6. Use Metrics for time‑series error views
   • From the Application Insights resource, open Metrics.
   • Add metrics such as failed requests or exceptions, grouped by project or environment.
   • Select Pin to dashboard to add these time‑series charts alongside the pie charts.
7. Build a cross‑resource dashboard (if using multiple App Insights resources)
   • In the Azure portal left menu, select Dashboard → New dashboard → Blank dashboard.
   • From each Application Insights resource, pin Metrics charts and Logs charts as above.
   • A single dashboard can contain tiles from multiple subscriptions and resource groups.
8. Finalize and share
   • On the dashboard, select Edit to resize and arrange tiles, then Done customizing.
   • Use Share to publish and control access via Azure role‑based access control.

This approach yields a central dashboard with one or more pie/doughnut charts showing production errors per project, plus any additional KPIs needed for monitoring.

References:

• Application Insights Overview dashboard
• Overview of integration with Application Insights
• Azure Monitor