Enterprise Observability Platform

Enterprise Observability Platform Objectives:
• Establish a single enterprise observability view for critical service health and operational awareness.
• Reduce time to detect and understand incidents that cross infrastructure, network, identity, and SaaS boundaries.
• Provide executive and operational dashboards that translate technical telemetry into service health.
• Implement synthetic and availability monitoring that validates real service access paths rather than relying solely on component alarms.
• Provide an extensible platform architecture capable of supporting Phases 2–5 without a fundamental platform replacement.
• Enable EOTSS staff to administer, operate, tune, and extend the platform after implementation.
- Phase 1 Workstream A – Discovery, Architecture, and Design
• Conduct discovery workshops with EOTSS stakeholders covering infrastructure, network, identity, Microsoft 365, operations, service management, and security.
• Document the target observability architecture, data flows, collection methods, security boundaries, and integration points.
• Define naming, tagging/labeling, ownership, severity, and dashboard standards.
• Develop a phased onboarding plan identifying dependencies, implementation sequencing, and transition considerations.
• Produce a Solution Design Document for EOTSS approval before production implementation.
• Establish a multi-tenancy standard that provides an aggregated enterprise-wide view alongside granular, role-based access control at the individual agency/organizational-unit level
- Phase 1 Workstream B – Vmware / Virtual Infrastructure Services
• Monitor virtualization management infrastructure, hosts, clusters, virtual machines, datastores, and resource utilization.
• Provide availability, performance, capacity, and health indicators sufficient to assess the condition of the virtualized environment.
• Provide views that identify infrastructure conditions likely to affect dependent services.
• Support integration with existing infrastructure monitoring where necessary to avoid operational blind spots.
• Generate live, automated architecture diagrams for vSphere for troubleshooting and optimization.
- Phase 1 Workstream C – Microsoft 365
• Monitor availability and operational health of business-critical Microsoft 365 services, including Exchange Online, Teams, SharePoint Online, and related authentication dependencies.
• Provide synthetic or equivalent service validation for selected critical user journeys and endpoints.
• Provide dashboards that distinguish service-wide provider issues from localized access or connectivity issues.
- Phase 1 Workstream D – Internet Services
• Monitor Internet-facing connectivity and service availability for identified enterprise endpoints.
• Provide DNS, HTTP/HTTPS, TCP and/or equivalent endpoint tests where appropriate.
• Monitor certificate validity and expiration for identified public services.
• Provide latency and availability measurements from appropriate observation points, including private/internal vantage points where technically appropriate.
• Correlate Internet service health with dependent service checks and provide dependency diagrams accordingly.
- Phase 1 Workstream E – Identity Services
• Monitor Microsoft Entra ID service availability and key authentication paths.
• Monitor Active Directory service availability for identified domain controllers and core directory services.
• Provide synthetic validation of selected authentication/SSO journeys without storing credentials in the observability platform except where explicitly approved.
• Provide service-oriented health views for identity dependencies affecting enterprise access.