Open
Conversation
…flows and documentation
…emplate validation
…n environment identification
…from user input' Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…from user input' Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
…TING_LOG_ANALYTICS_WORKSPACE_RID
…tion-pipeline ci: Refactor azure-dev and azd-template-validation workflows
feat: Enhance Application Insights logging configuration
chore: dependabot packages update
Priyanka-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft and
Roopan-Microsoft
as code owners
![github-code-quality[bot]](https://avatars.githubusercontent.com/u/9919?s=60&v=4){kind=small}
|
|
||
| try | ||
| { | ||
| _telemetryClient.TrackDependency(dependencyName, commandName, startTime, duration, success); |
Comment on lines
+53
to
+56
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to track event: {EventName}", eventName); | ||
| } |
Comment on lines
+76
to
+79
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to track exception"); | ||
| } |
Comment on lines
+101
to
+104
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to track dependency: {DependencyName}", dependencyName); | ||
| } |
Comment on lines
+124
to
+127
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to track metric: {MetricName}", metricName); | ||
| } |
Comment on lines
+146
to
+149
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to set activity tag: {Key}", key); | ||
| } |
Comment on lines
+166
to
+169
| catch (Exception ex) | ||
| { | ||
| _logger.LogError(ex, "Failed to flush telemetry client"); | ||
| } |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
fix: add bicep version requirement (>= 0.33.0) to azure.yaml
Avijit-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Avijit-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
ci: workflow to automate the validation of Bicep parameter files
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
| try: | ||
| data = json.loads(sanitized) | ||
| params = data.get("parameters", {}) | ||
| except json.JSONDecodeError: |
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Added notes about security restrictions and Azure OpenAI quota availability.
Added note about potential security restrictions affecting deployment.
…names fix: Update parameter names for standardization
Prachig-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Prachig-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
…-parameter-names fix: Update parameter names for standardization"
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
fix: Filter the paths to run the pipeline
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Roopan-Microsoft
had a problem deploying
to
production
GitHub Actions
Failure
Roopan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
docs: Added content in Readme and deploymentguide for SFI issue
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
11 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces significant improvements to the observability, reliability, and deployment automation of the chat API. The main focus is on adding detailed telemetry, logging, and error handling to both the synchronous and asynchronous chat endpoints, as well as introducing new GitHub Actions workflows for Azure deployment and template validation.
API Observability and Reliability Enhancements:
Chat API telemetry, logging, and error handling:
/chatand/chatAsyncendpoints inChat.cs, including request tracking, validation, performance metrics, and error handling for timeouts and exceptions. This improves traceability and helps with monitoring and debugging in production. [1] [2] [3]Dependency injection and helper usage:
TelemetryHelperandILogger<Chat>into the API endpoints for consistent telemetry and logging. [1] [2]CI/CD and Template Validation Automation:
GitHub Actions workflows:
.github/workflows/azure-dev.ymlto automate Azure deployment via theazdtool, including Azure login, environment setup, and deployment steps..github/workflows/azd-template-validation.ymlto schedule and manually trigger template validation using Microsoft's template validation action, improving CI reliability for infrastructure-as-code.These changes collectively improve the maintainability, observability, and operational robustness of the chat API and deployment process.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information