Add RetailShield custom table schema definitions (data connector ARM template)#77
Merged
Conversation
Defines RetailShield_POS_CL and RetailShield_Logs_CL custom Log Analytics table schemas with full column definitions, types, and descriptions. Includes README documenting ingestion endpoints and standard table dependencies. Closes #70
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
The file was stored with literal \n sequences instead of real newlines (MCP push_files encoding bug from previous session), causing syntax errors in pytest and flake8 on every branch forked from dev.
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
1 participant
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
Closes #70
Adds the ARM template that provisions
RetailShield_POS_CLandRetailShield_Logs_CL— the two custom Log Analytics tables required by RetailShield detection rules — along with a README documenting their schemas.Files added
What the template does
Deploys both tables via
Microsoft.OperationalInsights/workspaces/tables(API 2022-10-01) with explicit column definitions including types and descriptions. This must be run before deploying analytics rules or ingesting POS/log data.RetailShield_POS_CL — 19 columns covering: TerminalID, StoreID, EmployeeID, OperatorID, TransactionType, TransactionAmount, VoidCount, RefundCount, GiftCardID, TotalGiftCardValue, RiskScore, PlaybookTrigger, and more.
RetailShield_Logs_CL — 17 columns covering: EventType (voice_fraud / pos_anomaly / network_anomaly), CallerID, CallCount, VoiceAnomalyScore, ProcessName, DeviceName, RiskScore, PlaybookTrigger, and more.
How to test
Deploy to a dev workspace:
Verify tables exist in the workspace:
Confirm schema — the response from each
table showcommand should list all columns with the correct types.JSON validation:
python -m json.tool sentinel/data-connectors/retailshield-connector.jsonGenerated by Claude Code