COMPENSATION Ideally, a retrobooking system should be implemented to charge end users for the resources they consume to provide the service they expect. This incentivizes companies to use management methods that optimize costs and performance. If this is not feasible, the costs should nevertheless be identified and reimbursed to the Business Units in order to take into account IT resources. The frequency and format of such information should also be described. It is expected that a huge amount of data will be tracked by anomaly detections in smart cities. It is therefore necessary to address the first challenge of anomaly detection on how this considerable amount of data can be processed, analyzed and managed effectively. In addition, anomaly detection in a smart city focuses on using anomaly detection algorithms on data collected, for example, by network services in order to detect anomalies in these cases in time and have enough time to take corrective action. These anomalies reflect potential performance losses, so early detection and proactive remediation can have a significant impact on the performance of the system to be analyzed. Therefore, another challenge is the timely detection of anomalies associated with appropriate corrective actions. Customers of the cloud computing system are presented as VMs.
Based on the SLA or by using workload forecasting taking into account the SLA, the amount of resources needed for each customer can be determined. These VMs are therefore considered processing volume and storage tape requirements at the time in question. This assumption applies to online services (not Batch applications). The aim should be to fairly integrate best practices and requirements that preserve the service and avoid additional costs. FP7 IRMOS also looked at aspects of translating application-level SLAs into resource-based attributes to bridge the gap between customer expectations and cloud provider resource management mechanisms.   The European Commission presented a summary of the results of different research projects in the field of ASAs (from specifications to control, management and implementation).  These systems and processes are often controlled by specialized third-party companies. If this is the case, it is necessary that the third party is also involved in the AAA negotiations. This gives them details of the service levels to be followed and explanations on how to track them. Metrics should reflect only factors under the appropriate control of the service provider. Measurements must also be easy to collect.
In addition, both parties should refuse to choose excessive amounts of metrics or measurements that produce large amounts of data. However, the inclusion of too few metrics can also be problematic, as the absence of a metric could draw the view as if the treaty had been violated. Measurement In this section, the process for tracking actual service levels and comparing with agreed service levels, as well as the frequency of monitoring, should be described. A brief description of the data collection and extrapolation processes should be included and how users should report problems to the IT. A service level agreement (SLA) is a contract between a service provider and its customers, which documents the services that the provider will provide and defines the service standards that the provider is required to meet. Termination Procedure – The SLA should define the circumstances in which the agreement may be terminated or expire.. . .