Azure / Azure/bicep-registry-modules

[AVM Module Issue]: ALZ/ama - Logs missing

Open
#7,148 4 comments 0 reactions 4 assignees Claimed by @akshayrohilla View on GitHub
Class: Pattern Module :package: Needs: Immediate Attention :bangbang: Needs: Triage :mag: Status: Response Overdue :triangular_flag_on_post: Type: AVM :a: :v: :m: Type: Bug :bug:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Bug

### Module Name

avm/ptn/alz/ama

### (Optional) Module Version

_No response_

### Description

The bug:
There is no logs created the the DCR for Change Tracking.

No deployment Errors, no logs that I could find that talks about the error, the DCR just don't cheate any entries in the Log Analytics Workspace used.

File: avm/ptn/alz/ama/main.bicep
Change serviceSettings → servicesSettings in both the ChangeTracking-Windows and ChangeTracking-Linux extension settings blocks

From:
https://github.com/Azure/Azure-Landing-Zones/issues/4182
Where I got the recommendation to create the issue here.
```

With a fresh deployment of the Logging part of the core modules, there is still no data sent to the Log Analytics Workspace.

On the left is the DCR for change tracking I got when I created it though the portal, the right one is from you guys(Logging.Bicep) You can see there is an "s" missing in yours.
```

Image

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.