The SLA report provides an overall update of all remediation plans where the SLA start/end date falls within the selected timeframe.
SLA Report Fields
- RP ID
- RP Name
- RP Description
- RP Status
- Emergency - True / False if the RP was an emergency remediation plan or not.
- Creation Time (GMT) - time the remediation plan was created
- Activation Time (GMT) - time the remediation plan was activated
- Approval Time (GMT) - time the remediation plan was approved
- Unknown - for old RPs, activated before JetPatch 4.1.1 UR3 version.
- Waiting - for RPs that are waiting for approval in the ITMS.
- SLA Start Date (GMT) - SLA start date of the remediation plan, as configured in the RP creation
- SLA End Date (GMT) - SLA end date of the remediation plan, as configured in the RP creation
- SLA Status -
- Done - if the SLA time rechead
- In Progress - If the current date is still in the SLA Time
-
Pending - If the SLA Time still didn’t start.
- Applicable Endpoints - Number of endpoints that were available for patching
- End of SLA Compliant Endpoints - Number of compliant endpoints after SLA end date reached. Note - If the RP didn't reach the SLA time "Unknown" will be the value.
- Current Compliant Endpoints - Number of compliant endpoints in the time of downloading the report.
How to generate an SLA Report?
- Go to Dashboard
- Click on the 'Download Reports' button and select 'SLA summary' - A pop-up window should be opened
- Fill in the SLA property and the timeframe of RPs SLA and click 'Download'.
- An SLA report should be downloaded as a CSV file.
Which Remediation Plans should appear in the SLA report?
The SLA report shows all RPs that were activated in the past (including canceled RPs), without the rejected (By ITSM), based on the SLA start/end date and the selected timeframe.
Here is an example:
Remediation plan '500' was created on January 1st and activated on January 3rd. The user selected the following SLA Start Date and SLA End Date when creating the Remediation Plan
- SLA start date = January 15th.
- SLA end date = February 15th
Time of downloading the report | Report SLA property | The timeframe of the SLA | Will it appear in the report? | Reason |
January 2nd | Start Date | January 1st - January 20th | ![]() |
The RP is not activated yet |
January 20th | Start Date | January 1st - January 2nd | ![]() |
The SLA Start Date is not in the selected timeframe |
January 20th | Start Date | January 1st - January 20th | The SLA Start Date is not in the selected timeframe | |
January 20th | Start Date | January 20th - January 25th | ![]() |
The SLA Start Date is not in the selected timeframe |
January 20th | End Date | January 1st - January 2nd | ![]() |
The SLA End Date is not in the selected timeframe |
January 20th | End Date | February 1st - February 20th | The SLA End Date is not in the selected timeframe | |
January 20th | End Date | February 20th - February 25th | ![]() |
The SLA End Date is not in the selected timeframe |
How To Change SLA Parameters?
There are two configurable parameters:
- SLA time
- The planned end period of the remediation plan.
- The default value is 30 days
- SLA history
- SLA report history.
- The default value is 365 days
Follow the below instructions to configure the parameters:
1. Edi intigua.properties file (/usr/share/tomcat/default/conf/intigua.properties)
2. Add the below parameters with the values you would like to use.
#(default is 30) - will determine the planned end date. Number of days after activation.
pg.sla.planned-end-period.days = 30
#(default is 365) - clean the data that exist for X days.
pg.sla.keep-history.days = 365
Relevant Articles
- Configure the SLA dates in the Remediation Plan creation
Comments
0 comments
Please sign in to leave a comment.