GitHub Copilot Customization Explained for Beginners: Instructions, Prompt Files, Skills, Agents, and Hooks  Introduction If you've recently started using GitHub Copilot, you've probably come across terms like Instructions , Prompt Files , Skills , Agents , and Hooks . At first glance, they all seem to do the same thing—they tell Copilot what to do. So why does GitHub have five different customization features? The answer is simple: each feature solves a different problem. Think of GitHub Copilot as a new developer joining your team. On their first day, you don't just hand them code. You explain your coding standards, give them reusable templates, teach them specialized knowledge, assign them a role, and automate repetitive tasks. That's exactly how GitHub Copilot customization works. In this article, you'll learn what each feature does, when to use it, and how they all work together. By the end, you'll know which feature to start with and which ones can wait un...

Application Insights – Azure Service

Application Insights is an Azure Service which helps to monitor applications in real time. It’s a powerful service for Developer and DevOps professional which provide insights of your applications in terms of Performance, Application Health, Application Interaction, User flows, Availability, and its live metrics. Application Insights works on applications hosted on-premises, hybrid or any other cloud service provider. Application Insights comes with capability like Querying the metrics, dashboard for representing different metrics, ability to configure alerts, Integrating with Azure DevOps etc.

Application Insights can be used for monitoring Azure Services like Azure App service, VMs, Azure Function etc. Similarly, if you have existing application already build or deployed you can easily configure application-based monitoring using Application Insights SDK. We will see below how easy to integrate with new or existing application.

Below are the steps involved in configuring Application Insights for a .Net/.Net Core application.
1. Application Insight service is provisioned from Azure portal.
2. Right click on Start up project like WebAPI/MVC app and navigate to “Application Insights Telementry” as shown below.






3. In the start up class following code will be auto populated if not place it manually
services.AddApplicationInsightsTelemetry();

4. Appsettings.json populate Instrumentation key which will be available from Azure portal of Application Insights


Below is an example where I have deployed few services in Azure. There is a Front end application which is interacts with database for fetching data, front end app interacts with External webapi and External webapi in turn interacts with Azure Function(HTTP trigger).

Note: All your services sending telemetry to the same Application Insights instance. The Application Insights UI in the Azure Portal has no ability to display this visualizations across multiple Application Insights instances.

One frequent question I hear from developers “Can I use Application Insights because we are not on Azure”. Well you don’t need to host your application on Azure it can be hosted anywhere as long Azure Insights is created in Azure and integrated with your application using Instrumentation key.

Composite Application Map

You can see the full application topology across multiple levels of related application components. Components could be different Application Insights resources, or different roles in a single resource.


Using Application Insights you can drill down to application flow as shown below e.g. if we see from Front end component http call is made to WebAPI and from WebAPI it makes call to Azure function.

Comments

Popular posts from this blog

Tidy up - Unused Project and Nuget package reference using Visual Studio 2019

Azure Front Door vs Azure Traffic Manager?

Authenticate Azure Functions - API Keys