O365 Monitoring - Service Health
Summary: Eddy Ortiz has raised a concern regarding the LogicMonitor's O365 Service Health module not updating properly when Microsoft reuses or updates existing advisories, without clear state changes. They provided an example of an Exchange incident that did not trigger a new alert because it remained at the same value from a previous notification. Eddy Ortiz is seeking best practices or suggestions to effectively leverage the Service Health module for tracking various Microsoft services, including Exchange Online, Microsoft Teams, and others.
Good afternoon,
Has anyone seen LogicMonitor’s O365 Service Health module miss or lag incidents when Microsoft updates/reuses an existing advisory (no clear state change)?
Example: yesterday Exchange incident stayed at a value of 15 (Service Degradation), but it was already reporting 15 from a previous alert, so we didn’t get a “new” alert or change in value and weren’t aware of this new issue.
Any bests practices or suggestions are greatly appreciated.
We are trying to leverage the Service Health module to keep track on some of these:
Basic Mobility and Security
Exchange Online
Microsoft 365 apps
Microsoft 365 Copilot Chat
Microsoft 365 for the web
Microsoft 365 suite
Microsoft Copilot (Microsoft 365)
Microsoft Entra
Microsoft Intune
Microsoft OneDrive
Microsoft Teams
Power Apps
Power Apps in Microsoft 365
SharePoint Online
