|
14 | 14 | { |
15 | 15 | "metricName": "Total events received", |
16 | 16 | "legend": "GitHubAuditLogEvents", |
17 | | - "baseQuery": "GitHubAuditLogsV2_CL" |
| 17 | + "baseQuery": "GitHubAuditLogsV3_CL" |
18 | 18 | } |
19 | 19 | ], |
20 | 20 | "sampleQueries": [ |
21 | 21 | { |
22 | 22 | "description": "GitHub Audit Logs", |
23 | | - "query": "GitHubAuditLogsV2_CL | take 10" |
| 23 | + "query": "GitHubAuditLogsV3_CL | take 10" |
24 | 24 | } |
25 | 25 | ], |
26 | 26 | "dataTypes": [ |
27 | 27 | { |
28 | | - "name": "GitHubAuditLogsV2_CL", |
29 | | - "lastDataReceivedQuery": "GitHubAuditLogsV2_CL | summarize Time = max(TimeGenerated) | where isnotempty(Time)" |
| 28 | + "name": "GitHubAuditLogsV3_CL", |
| 29 | + "lastDataReceivedQuery": "GitHubAuditLogsV3_CL | summarize Time = max(TimeGenerated) | where isnotempty(Time)" |
30 | 30 | } |
31 | 31 | ], |
32 | 32 | "connectivityCriteria": [ |
|
123 | 123 | "type": "Textbox", |
124 | 124 | "parameters": { |
125 | 125 | "label": "The blob container's storage account resource group name", |
126 | | - "placeholder": "my-resource-group", |
| 126 | + "placeholder": "", |
127 | 127 | "type": "text", |
128 | 128 | "name": "StorageAccountResourceGroupName" |
129 | 129 | } |
|
159 | 159 | }, |
160 | 160 | { |
161 | 161 | "title": "Blob Lifecycle Policy (Recommended)", |
162 | | - "description": "To prevent unbounded storage growth, configure a [lifecycle management policy](https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview) on your storage account to automatically delete blobs after a retention period (for example, 7 days). Once the connector ingests the audit logs into Microsoft Sentinel, the source blobs are no longer needed.\n\nTo create a lifecycle rule scoped to your container:\n1. Navigate to your **Storage Account** -> **Data management** -> **Lifecycle management**.\n2. Click **Add a rule** and configure:\n - **Rule name:** for example, `github-audit-cleanup`\n - **Rule scope:** Select **Limit blobs with filters** and set the **Prefix match** to your container name (for example, `my-container/`). This ensures the rule applies only to blobs in that container.\n - **Blob type:** Block blobs.\n - **Base blobs:** Delete blobs that were last modified more than **7 days** ago (adjust as needed).\n3. Save the rule.\n\n> **Note:** Each storage account has a single management policy that can contain multiple rules. Each rule can target a specific container via prefix filters. If you already have a lifecycle policy, add a new rule to the existing policy rather than creating a new one.", |
163 | | - "instructions": [] |
| 162 | + "description": "To prevent unbounded storage growth, configure a [lifecycle management policy](https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-overview) on your storage account to automatically delete blobs after a retention period (for example, 7 days). Once the connector ingests the audit logs into Microsoft Sentinel, the source blobs are no longer needed.\n\nTo create a lifecycle rule scoped to your container:\n1. Navigate to your **Storage Account** -> **Data management** -> **Lifecycle management**.\n2. Click **Add a rule** and configure:\n - **Rule name:** for example, `github-audit-cleanup`\n - **Rule scope:** Select **Limit blobs with filters** and set the **Prefix match** to your container name (for example, `my-container/`). This ensures the rule applies only to blobs in that container.\n - **Blob type:** Block blobs.\n - **Base blobs:** Delete blobs that were last modified more than **7 days** ago (adjust as needed).\n3. Save the rule.\n\n> **Note:** Each storage account has a single management policy that can contain multiple rules. Each rule can target a specific container via prefix filters. If you already have a lifecycle policy, add a new rule to the existing policy rather than creating a new one." |
164 | 163 | }, |
165 | 164 | { |
166 | 165 | "title": "Reference", |
167 | | - "description": "For detailed instructions on setting up the Azure Storage connector to stream logs to Microsoft Sentinel, see [Set up Azure Storage connector](https://learn.microsoft.com/en-us/azure/sentinel/setup-azure-storage-connector).", |
168 | | - "instructions": [] |
| 166 | + "description": "For detailed instructions on setting up the Azure Storage connector to stream logs to Microsoft Sentinel, see [Set up Azure Storage connector](https://learn.microsoft.com/en-us/azure/sentinel/setup-azure-storage-connector)." |
169 | 167 | }, |
170 | 168 | { |
171 | 169 | "title": "Troubleshooting", |
172 | | - "description": "If you encounter issues with data ingestion:\n- **Enable the health feature** - If the connector health feature isn't enabled, enable it to monitor connector status and detect issues early.\n- **Enable diagnostic logs** - Consider enabling diagnostic logs for both the **Storage Account** and **Event Grid** resources to help identify and troubleshoot health issues.\n- For more details, see [Troubleshoot Azure Storage Blob connector issues](https://review.learn.microsoft.com/en-us/azure/sentinel/azure-storage-blob-connector-troubleshoot?branch=main).", |
173 | | - "instructions": [] |
| 170 | + "description": "If you encounter issues with data ingestion:\n- **Enable the health feature** - If the connector health feature isn't enabled, enable it to monitor connector status and detect issues early.\n- **Enable diagnostic logs** - Consider enabling diagnostic logs for both the **Storage Account** and **Event Grid** resources to help identify and troubleshoot health issues.\n- For more details, see [Troubleshoot Azure Storage Blob connector issues](https://review.learn.microsoft.com/en-us/azure/sentinel/azure-storage-blob-connector-troubleshoot?branch=main)." |
174 | 171 | } |
175 | 172 | ] |
176 | 173 | } |
|
0 commit comments