Repository navigation
Lab 2, Step 3: clarify where to run the KQL query + realistic ingestion timing - #2
Merged
ajy0127 merged 1 commit intoSep 16, 2026
Conversation
…nd set realistic ingestion timing Two documentation clarity fixes for labs/02-toolkit, both verified live on a fresh free subscription: 1. The AzureActivity query is KQL, not a shell command, but it's formatted like the surrounding shell blocks. Students paste it into the terminal and hit `zsh: parse error near '|'` (reproduced). Even in the portal, "Logs" often opens in Simple mode (no query box) and it's easy to land on the subscription Activity Log blade by mistake. The step now: names the Logs blade explicitly (not Activity Log), calls out the Simple mode -> KQL mode toggle, and adds a copy-paste CLI equivalent for people who'd rather stay in the terminal. 2. Ingestion timing was understated as "~5-10 minutes." On a brand-new workspace the first AzureActivity rows can take 30-60 minutes to appear at all. Verified live: routing correct, workspace resolves, Administrative category enabled, a confirmed tag write captured, yet the table was still 0 rows 20 minutes later. The step now states the first-cycle delay explicitly (mirroring the Defender note in Step 4) so students don't think they broke something. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
Two documentation clarity fixes for Lab 2 (
labs/02-toolkit), Step 3, both found and verified while running the lab end-to-end on a fresh free subscription. Neither is a broken command — both are gaps that make correct setups look broken.Finding 1 — the
AzureActivityKQL query is easy to run in the wrong place/modeThe query is formatted like the shell command blocks around it, so following the "paste the next block" flow lands you in the wrong tool:
zsh: parse error near '|'(reproduced). Nothing flags it as portal-only.Fix: Step 3 now states the query is KQL (not a shell command) and gives two explicit paths — the portal Logs blade (not Activity Log) with the Simple → KQL mode toggle called out, and a copy-paste CLI equivalent (
az monitor log-analytics query ...) for people who'd rather stay in the terminal.Finding 2 — ingestion timing understated for a brand-new workspace
The step says ingestion lags "~5–10 minutes." On a brand-new workspace the first
AzureActivityrows can take 30–60 minutes to appear at all.Verified live: routing correct, workspace resolves, Administrative category enabled, a confirmed tag write captured — yet the table was still 0 rows 20 minutes after that write. A student following the current text concludes they broke something.
Fix: Step 3 now states the first-ingestion delay explicitly (mirroring the Defender first-cycle note in Step 4) and reframes an empty table as "wait, not broken."
Scope
labs/02-toolkit/README.md(Step 3 only).🤖 Generated with Claude Code