# Reports
**Instructions for viewing Anomalies**
1. On the main Infrastructure Anomalies screen, the system will display a summary of the Infrastructure Anomalies that occurred in the last 7 days.
* **Number of Monitored Accounts:** Total number of accounts being monitored to identify anomalies
* **Number of Enabled Models**: Number of enabled templates per account that can be infringed
* **Anomalies from last report**: Number of anomalies detected.
* **Total Deviations**: Total calculated value.
The system allows to change the number of days to be viewed in the report by clicking on the option:
2. In the Anomaly Listing corresponding to the desired date, click on **View Report "****"**.
A **List of Anomalies** for the day will be displayed, indicating the main information about the services consumed that violated the configured model.
3. The system allows you to filter the list by showing the anomalies that were verified or not, by clicking on the option:
4. To access the **Anomaly Details**, click on **View Report** **"****"**:
In the **Anomaly Detail**, it is possible to identify the infringed model, the Expected cost, the Increase in dollars and in percentage.
{% hint style="info" %}
Whenever the expected cost is **zero**, even if the increase in $ is greater than zero, the percentage increase cannot be calculated, returning the following message: "**Increase not applicable"**.
{% endhint %}
5. To open the View click on ""
The system allows to open the view and make adjustments if necessary:
{% hint style="info" %}
For each anomaly view generated, some default filter options will be applied, which can be customized as needed:
* lineitem/lineitemtype
* lineitem/usageaccountid
* product/region
* product/productname
* lineitem/usagetype
{% endhint %}
6. Set the Anomaly as "**Verified**":
* In the **Anomaly Listing**, click the **Verified** button:
* On the screen displayed, enter the **Classification**:
* **Anomaly**: Behavior outside the expected pattern.
* **False Positive**: Alert generated by something legitimate identified as a threat.
* **Expected Behavior**: When it is a behavior that is different from normal, but expected by the system due to a specific moment/event.
* Inform the **description** and then click the **Save** button.
{% hint style="info" %}
To send an alert about Anomalies, access: Alarms
{% endhint %}
#### Sync with Forecast
When selecting Sync with Forecast on an infrastructure anomaly, the system automatically creates an event in the Infrastructure Forecast module using the anomaly’s data.
While this event is active, the identified deviation will be excluded from the forecast calculation, preventing one-time spikes or drops from impacting future projections.
