Overview
Location: Dashboards → Patches Compliance (relevant article)
Users can download the SLA Report by clicking the Download Reports button and selecting SLA Summary.
This report is available in CSV format and provides detailed information about all remediation plans where the SLA start/end date falls within the selected timeframe.
Use Case
Use the SLA Report to gain visibility into the status of remediation plans within a specific timeframe. This report is essential for:
- Monitoring compliance status of remediation plans.
- Identifying non-compliant devices.
- Reviewing remediation actions and planning further steps.
SLA Report Fields
Remediation Plan Details
| Field | Description |
| RP ID | Remediation Plan Identifier. |
| RP Name | Name of the Remediation Plan. |
| RP Description | Description of the Remediation Plan. |
| RP Status | Current status of the Remediation Plan. |
| Emergency | True/False — whether the RP was an emergency remediation plan. |
Timestamps (GMT)
| Field | Description |
| Creation Time | Time the remediation plan was created. |
| Activation Time | Time the remediation plan was activated. |
| Approval Time | Time the remediation plan was approved. |
| Deletion Time | Time the remediation plan was deleted (if applicable). |
SLA Dates (GMT)
| Field | Description |
| SLA Start Date | Start date of the SLA. |
| SLA End Date | End date of the SLA. |
SLA Status
| Status | Description |
| Done | The SLA time has been reached. |
| In Progress | The current date is within the SLA time. |
| Pending | The SLA time has not yet started. |
Endpoints
| Field | Description |
| Applicable Endpoints | Number of endpoints available for patching. |
| End of SLA Compliant Endpoints | Number of compliant endpoints after the SLA end date is reached. |
| Current Compliant Endpoints | Number of compliant endpoints at the time of downloading the report. |
How to Generate an SLA Report
- Navigate to Dashboard → Patches Compliance.
- Click the Reports button in the top right and select SLA Summary. A pop-up window will open.
- Fill in the SLA property and the timeframe of the RP’s SLA, then click Download.
- The SLA Report will be downloaded as a CSV file.
Which Remediation Plans Appear in the SLA Report
The SLA report shows all RPs that were activated in the past (including canceled RPs), excluding those rejected by ITSM, based on the SLA start/end date and the selected timeframe.
Example
Remediation Plan '500' was created on January 1st and activated on January 3rd. The following SLA dates were configured:
- SLA Start Date: January 15th.
- SLA End Date: February 15th.
| Time of Download | Report SLA Property | Timeframe | Appears? | Reason |
| Jan 2 | Start Date | Jan 1–20 | ❌ | RP not yet activated. |
| Jan 20 | Start Date | Jan 1–20 | ❌ | SLA Start not in timeframe. |
| Jan 20 | Start Date | Jan 1–20 | ✅ | SLA Start in timeframe. |
| Jan 20 | End Date | Jan 1–2 | ❌ | SLA End not in timeframe. |
| Jan 20 | End Date | Feb 1–20 | ✅ | SLA End in timeframe. |
| Jan 20 | End Date | Feb 20–25 | ❌ | SLA End not in timeframe. |
How to Change SLA Parameters
There are two configurable parameters:
- SLA Time – The planned end period of the remediation plan. Default: 30 days.
- SLA History – SLA report history. Default: 365 days.
Step 1: Edit the intigua.properties File
| Version | File Path |
| Before 5.0 | /usr/share/tomcat/default/conf/intigua.properties |
| Post 5.0 | /usr/share/intigua/services/data/intigua-main/conf/intigua.properties |
Step 2: Add the Parameters
Add the parameters below with the values you would like to use:
|
#(default is 30) - will determine the planned end date. Number of days after creation. pg.sla.planned-end-period.days = 30
#(default is 365) - clean the data that exist for X days. pg.sla.keep-history.days = 365 |
| Note: You can override the default values during Remediation Plan creation. |
Comments
0 comments
Please sign in to leave a comment.