Cortex-Integrated SLO Management Framework: A Dependency-Aware, Closed-Loop Reliability Optimization System
Keywords:
Service Level Objectives, Site Reliability Engineering, Azure Data Explorer, dependency-aware observability, closed-loop reliability management, consumer impact analysis, cloud-native microservices, telemetry correlationAbstract
Service Level Objectives (SLOs) are foundational to Site Reliability Engineering (SRE), yet existing implementations lack continuous enforcement, dependency awareness, and automated improvement mechanisms. This paper presents a Cortex-Integrated SLO Management Framework that enables end-to-end lifecycle management of SLOs—from definition and ingestion to evaluation, dependency correlation, and automated recommendations. The system leverages a workflow-driven ingestion mechanism, Azure-based processing pipelines, and a scalable analytics backend using Azure Data Explorer (ADX). By incorporating dependency-aware evaluation and consumer impact propagation, the framework provides actionable insights that significantly improve reliability outcomes. The architecture integrates centralized SLO governance, telemetry aggregation, service correlation, consumer impact analysis, and automated recommendation generation into a unified operational workflow. Controlled experimental evaluation conducted within a cloud-native microservices environment demonstrated substantial improvements in incident detection responsiveness, dependency attribution accuracy, and operational resolution efficiency. Specifically, the framework achieved approximately five-to-eight times faster Mean Time to Detect (MTTD), a fifty to sixty percent reduction in Mean Time to Resolve (MTTR), and root-cause attribution accuracy exceeding ninety percent compared with traditional threshold-based monitoring approaches. These findings demonstrate the value of integrating SLO governance with dependency-aware observability and automated recommendation generation for modern distributed cloud environments.
Downloads
References
Google, Site Reliability Engineering: How Google Runs Production Systems. O'Reilly Media, 2016.
Google, The Site Reliability Workbook: Practical Ways to Implement SRE. O'Reilly Media, 2018.
Datadog, "Service level objectives and error budgets," Datadog Documentation, 2023. [Online]. Available: https://docs.datadoghq.com
OpenTelemetry, "OpenTelemetry documentation," 2023. [Online]. Available: https://opentelemetry.io
Microsoft, "Azure Monitor documentation," Microsoft Learn, 2024. [Online]. Available: https://learn.microsoft.com
Microsoft, "Azure Workbooks overview," Microsoft Learn, 2024. [Online]. Available: https://learn.microsoft.com
Microsoft, "Azure Data Explorer documentation," Microsoft Learn, 2024. [Online]. Available: https://learn.microsoft.com
Cortex, "What is an internal developer portal?" Cortex.io, 2023. [Online]. Available: https://www.cortex.io
Cortex, "Building reliable services: A guide to setting SLOs," Cortex.io, 2023. [Online]. Available: https://www.cortex.io
Downloads
Published
How to Cite
Issue
Section
License

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
All papers should be submitted electronically. All submitted manuscripts must be original work that is not under submission at another journal or under consideration for publication in another form, such as a monograph or chapter of a book. Authors of submitted papers are obligated not to submit their paper for publication elsewhere until an editorial decision is rendered on their submission. Further, authors of accepted papers are prohibited from publishing the results in other publications that appear before the paper is published in the Journal unless they receive approval for doing so from the Editor-In-Chief.
IJISAE open access articles are licensed under a Creative Commons Attribution-ShareAlike 4.0 International License. This license lets the audience to give appropriate credit, provide a link to the license, and indicate if changes were made and if they remix, transform, or build upon the material, they must distribute contributions under the same license as the original.


