Skip to content

fix(azure): keep the summary rule columns on EagleEventsDaily_CL - #9

Merged
danieltruong merged 1 commit into
mainfrom
fix-summary-rule-active
Sep 6, 2026
Merged

danieltruong merged 1 commit into
mainfrom
fix-summary-rule-active

Conversation

@danieltruong

Copy link
Copy Markdown
Collaborator

deploy-infra.sh test --what-if proposed removing _BinSize, _BinStartTime, _RuleLastModifiedTime and _RuleName from EagleEventsDaily_CL on every run. The tables API replaces the column list on PUT, so the template was asking ARM to delete the fields the summary rule eagle-events-daily adds.

The four columns are now declared on the table. The DCR stream declaration is unchanged, since it is the contract the history import posts against. What-if on test is clean for the table apart from the isLakeAllowed / isTroubleshootingAllowed residue that no template can set.

isActive on the summary rule is read-only (BCP073 and the published type index), so the - properties.isActive: true what-if line is noise; a comment above the resource says so.

The tables PUT replaces the column list, so every deploy asked ARM to
drop the four _Bin*/_Rule* columns the summary rule adds. Declare them
on the table (not the DCR stream) so what-if is clean and the rule
keeps its fields. isActive on the rule is read-only; the what-if line
for it is noise.
@danieltruong
danieltruong merged commit 6670c85 into main Sep 6, 2026
3 checks passed
danieltruong added a commit that referenced this pull request Sep 6, 2026
Log Analytics rejects a table PUT that names the rule's _-prefixed
columns (MSG 1008), so #9 broke the test deploy. Back to the single
column list; the four-column delete in what-if is noise.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant