Final: live fleet monitoring + Azure Monitor (App Insights)#108
Merged
Conversation
…ion to the admin app
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
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.
Summary
A significant feature update to the Admin & Maintenance App for the final, adding two more Azure services to the solution and a real-time operations view.
1. Live fleet monitoring (real-time)
2. Azure Monitor / Application Insights (new service)
Iac/admin-webapp) provisions a dedicated Log Analytics workspace + Application Insights for the admin app.BotCreated,BotRecharged,BotServicingToggled,BotUpdated,BotDeleted).azand baked in — no data-plane RBAC / role assignment needed, so it's fully self-service.Passwordless / IaC / Actions
iac.yml(PR = plan, merge = apply).AdminWebpage-Deploy-WF.yml(OIDC).Tests
Notes for reviewers
iac.ymlcreates the App Insights resource; the admin deploy then fetches its connection string. If the deploy races ahead of the apply on first merge, telemetry turns on at the next deploy (graceful no-op until then).Relates to #18. Final feature (Option 1).