There was an error while loading. Please reload this page.
Document importer CPU aggressiveness settings (pnp/Microsoft365-Analytics-Insights#161/#162) Add 'Reducing importer CPU usage (aggressiveness)' section to Configuration Reference covering ImportAggressiveness, MaxAuditReportLoadConcurrency, ImportCyclePauseMinutes, GraphMetadataImportIntervalHours and ImportStartStaggerMinutes; cross-link from Monitoring System Performance checklist. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Wiki: finish branding modernisation + fix two malformed Analytics tables - Modernise generic 'Office 365' platform references to 'Microsoft 365' across the wiki (44 occurrences), now that the product is 'Microsoft 365 Advanced Analytics'. The real 'Office 365 Management [Activity] API' name and code identifiers (Office365ActivityImporter, o365_client_applications) are preserved. - Analytics - Data model: fix the malformed 'Usage metrics' table (the header had two columns but the data row had four; the stray cells duplicated the App-per-platform table below). - Analytics: de-indent the Runbooks table so it renders reliably (it was indented under a list item). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Wiki: modernise product name to 'Microsoft 365 Advanced Analytics' + accuracy/structure polish - Standardise the product name to Microsoft 365 Advanced Analytics (was a mix of 'Office 365 Advanced Analytics [Engine]', 'M365 Advanced Analytics', 'O365...'). Code identifiers (Office365ActivityImporter), the Office 365 Management Activity API name and the literal 'O365 Adv Analytics Setup Rule' firewall rule are deliberately preserved. - Replace legacy docs.microsoft.com links with learn.microsoft.com. - Tie the monitoring trio together: Health Alerts and Monitoring now cross-link Monitoring system performance and vice-versa. - Verify: fix informal wording and add a 'What good looks like' pass/fail checklist. - Troubleshooting: point fatal-exception reports at GitHub Issues (with a redact-secrets warning) instead of an unaddressed 'please email'. - Manual setup: clarify the importer uses the App Insights connection string, with the instrumentation key still needed for AITracker/legacy logging. - Architecture & costs: document the basis for the ~EUR170/month estimate. - CSP page: add deployment/context cross-links. - Align the Analytics page title with the sidebar ('Activity & Usage Analytics'). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Use sys.tables size query instead of deprecated sys_telemetry_reports The sys_telemetry_reports table is deprecated. Replace section 3 with a direct sys.tables/sys.partitions query that returns per-table row count and MB on disk, and add a mapping from each large table back to the import area that fills it so admins can either clean up or disable an import area they don't actually use. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Add Monitoring System Performance wiki page Documents how to monitor import cycle duration via Application Insights, how to diff sys_telemetry_reports snapshots to compare against previous metrics as the DB grows, and how/when to run Clean Old Data Data.sql followed by index rebuilds. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>