Comprehensive Explanation of SLA Violations at Runtime

Nowadays, lots of service providers offer predictive services that show in advance a condition or occurrence about the future. As a consequence, it becomes necessary for service customers to select the predictive service that best satisfies their needs. The QuPreSS reference model provides a standard solution for the selection of predictive services based on the quality of their predictions. QuPreSS has been designed to be applicable in any predictive domain (e.g., weather forecasting, economics, and medicine). This paper presents Mercury, a tool based on the QuPreSS reference model and customized to the weather forecast domain. Mercury measures weather predictive services' quality, and automates the context-dependent selection of the most accurate predictive service to satisfy a customer query. To do so, candidate predictive services are monitored so that their predictions can be eventually compared to real observations obtained from a trusted source. Mercury is a proof-of-concept of QuPreSS that aims to show that the selection of predictive services can be driven by the quality of their predictions. Throughout the paper, we show how Mercury was built from the QuPreSS reference model and how it can be installed and used.

show abstract

“…SALMon was chosen given its adaptability and performance exhibited in previous uses [35][36][37]. The data collection process works as follows.…”

Section: The Monitor and The Forecasting Data Collector Servicesmentioning

confidence: 99%

Mercury: Using the QuPreSS reference model to evaluate predictive services

Martínez‐Fernández

Franch

Bisbal

2017

Science of Computer Programming

View full text Add to dashboard Cite

show abstract

“…Specifically, a guarantee term, (guarantees from now on) is defined around the idea of a Service Level Objective (SLO) that should be guaranteed (by the guarantor) to the beneficiary (e.g. Response Time < 100ms or Monthly Uptime Percentage ≥ 99.95% ) Complementary, this specification also includes a placeholder to express penalties and rewards that can be extended with domain-specific languages [7,6].…”

Section: Compensable Slasmentioning

confidence: 99%

Towards Compensable SLAs

Müller

Gutierrez

Resinas

et al. 2015

Communications in Computer and Information Science

Self Cite

View full text Add to dashboard Cite

Abstract. Service Level Agreements (SLA) describe the rights and obligations of parties involved (typically the service consumer and the service provider); amongst other information they could include the definition of compensations: penalties and/or rewards depending on the level of service provided. We coin the concept of Compensable SLAs to such that include compensation information inside. In such a context, in spite of important steps towards the automation of the management of SLAs have been given, the expression of compensations remains as an important challenge to be addressed. In this paper we aim to provide a characterization model to create Compensable SLAs; specifically, the main contributions include: (i) the conceptualization of the Compensation Function to express consistently penalties and rewards. (ii) a model for Compensable SLAs as a set of guarantees that associate Service Level Objectives with Compensation Functions. We provide some properties and aspects that have been used to analyse two real-world SLAs.

show abstract

“…SALMon is a monitoring platform which main goal has been to gather the quality of service of web services and check simple SLA conditions. We extended SALMon jointly with its creators [3] in order to support: (1) the analysis of WS-Agreement-compliant agreements with expressive SLOs and (2) checking and explaining agreement violations. In turn, WSAG4J tool provides an implementation of the WS-Agreement protocol.…”

Section: Contributionsmentioning

confidence: 99%

On the automated analysis of WS–Agreement documents: Applications to the processes of creating and monitoring agreements

Müller

2014

AIC

View full text Add to dashboard Cite

Abstract. The need for Service Level Agreements (SLAs) to supervise the consumption of services is increasing in business applications and Cloud scenarios due to the penalties that can apply for violation of SLA terms. Such a need for SLAs boosts the importance and complexity of SLA lifecycle supporting systems (SLA-driven solutions). In our work we propose to improve the current support to develop SLA-driven solutions by enhancing both, the SLA specifications and automated analysis techniques. Furthermore, we have applied our proposal to creating and monitoring agreement solutions.

show abstract

Comprehensive Explanation of SLA Violations at Runtime

Cited by 59 publications

References 22 publications

Mercury: Using the QuPreSS reference model to evaluate predictive services

Mercury: Using the QuPreSS reference model to evaluate predictive services

Towards Compensable SLAs

On the automated analysis of WS–Agreement documents: Applications to the processes of creating and monitoring agreements

Contact Info

Product

Resources

About