You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# ChatGPT + Enterprise data with Azure OpenAI and AI Search
19
19
20
-
> [!IMPORTANT]
20
+
> [!IMPORTANT]
21
21
> As of November 15, 2023, Azure Cognitive Search has been renamed to Azure AI Search.
22
22
23
-
### Announcing [**JavaScript**](https://aka.ms/azai/js/code), [**.NET**](https://aka.ms/azai/net/code), and [**Java**](https://aka.ms/azai/java/code) samples based on this one in [**Python**](https://aka.ms/azai/py/code). Learn more at https://aka.ms/azai.
23
+
### Announcing [**JavaScript**](https://aka.ms/azai/js/code), [**.NET**](https://aka.ms/azai/net/code), and [**Java**](https://aka.ms/azai/java/code) samples based on this one in [**Python**](https://aka.ms/azai/py/code). Learn more at https://aka.ms/azai.
-[Enabling login and document level access control](#enabling-login-and-document-level-access-control)
43
42
-[Enabling CORS for an alternate frontend](#enabling-cors-for-an-alternate-frontend)
44
43
-[Using the app](#using-the-app)
45
44
-[Running locally](#running-locally)
45
+
-[Monitoring with Application Insights](#monitoring-with-application-insights)
46
+
-[Customizing the UI and data](#customizing-the-ui-and-data)
46
47
-[Productionizing](#productionizing)
47
48
-[Resources](#resources)
48
49
-[Note](#note)
@@ -64,7 +65,7 @@ The repo includes sample data so it's ready to try end to end. In this sample ap
64
65
* Explores various options to help users evaluate the trustworthiness of responses with citations, tracking of source content, etc.
65
66
* Shows possible approaches for data preparation, prompt construction, and orchestration of interaction between model (ChatGPT) and retriever (AI Search)
66
67
* Settings directly in the UX to tweak the behavior and experiment with options
67
-
*Optional performance tracing and monitoring with Application Insights
68
+
*Performance tracing and monitoring with Application Insights
68
69
69
70

70
71
@@ -238,26 +239,6 @@ either you or they can follow these steps:
238
239
239
240
## Enabling optional features
240
241
241
-
### Enabling Application Insights
242
-
243
-
To enable Application Insights and the tracing of each request, along with the logging of errors, set the `AZURE_USE_APPLICATION_INSIGHTS` variable to true before running `azd up`
244
-
245
-
1. Run `azd env set AZURE_USE_APPLICATION_INSIGHTS true`
246
-
1. Run `azd up`
247
-
248
-
To see the performance data, go to the Application Insights resource in your resource group, click on the "Investigate -> Performance" blade and navigate to any HTTP request to see the timing data.
249
-
To inspect the performance of chat requests, use the "Drill into Samples" button to see end-to-end traces of all the API calls made for any chat request:
To see any exceptions and server errors, navigate to the "Investigate -> Failures" blade and use the filtering tools to locate a specific exception. You can see Python stack traces on the right-hand side.
254
-
255
-
You can also see chart summaries on a dashboard by running the following command:
256
-
257
-
```shell
258
-
azd monitor
259
-
```
260
-
261
242
### Enabling authentication
262
243
263
244
By default, the deployed Azure web app will have no authentication or access restrictions enabled, meaning anyone with routable network access to the web app can chat with your indexed data. You can require authentication to your Azure Active Directory by following the [Add app authentication](https://learn.microsoft.com/azure/app-service/scenario-secure-app-authentication-app-service) tutorial and set it up against the deployed web app.
@@ -300,6 +281,23 @@ Once in the web app:
300
281
* Explore citations and sources
301
282
* Click on "settings" to try different options, tweak prompts, etc.
302
283
284
+
## Monitoring with Application Insights
285
+
286
+
By default, deployed apps use Application Insights for the tracing of each request, along with the logging of errors.
287
+
288
+
To see the performance data, go to the Application Insights resource in your resource group, click on the "Investigate -> Performance" blade and navigate to any HTTP request to see the timing data.
289
+
To inspect the performance of chat requests, use the "Drill into Samples" button to see end-to-end traces of all the API calls made for any chat request:
To see any exceptions and server errors, navigate to the "Investigate -> Failures" blade and use the filtering tools to locate a specific exception. You can see Python stack traces on the right-hand side.
294
+
295
+
You can also see chart summaries on a dashboard by running the following command:
296
+
297
+
```shell
298
+
azd monitor
299
+
```
300
+
303
301
## Customizing the UI and data
304
302
305
303
Once you successfully deploy the app, you can start customizing it for your needs: changing the text, tweaking the prompts, and replacing the data. Consult the [app customization guide](docs/customization.md) as well as the [data ingestion guide](docs/data_ingestion.md) for more details.
0 commit comments