Enable monitoring agent to transmit to log analytics workspace #2279
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.
✅ Checklist
Enable foobar integration
rather than515 foobar
).develop
.🚦 Depends on
For Azure Monitoring Agent to be able to connect to a log analytics workspace, the VM it is on must have a Managed Identity.
This PR gives each VM a system-assigned managed identity, allowing the transmission of logs and metrics from the VM to the log analytics workspace.
An alternative would be to create a single managed identity to be shared across all VMs as a user-assigned managed identity rather than a system-assigned one.
🌂 Related issues
Closes #1931
🔬 Tests
Deployed a new SRE and observed that the logs are appropriately populated in the log analytics workspace.