The KPI backfill was not functioning as expected in adaptive thresholding. The data backfill only occurred from the date the thresholding was enabled, and any prior data was not captured, leading to missing historical data.

Upon investigation, it was found that the issue was caused by the use of the |eval and |stats commands in the search, as well as the thresholding field referencing _time, which is not indexed in the original data. Since the threshold value field was being evaluated at runtime, backfill could not process the necessary data from before the KPI was created.
Additionally, the current KPI backfill status can be checked using the following REST command:
| rest serviceNS/nobody/SA-ITOA/backfill_services/backfill? | spath input=value | rename {}.* as *

| rest splunk_server=local /servicesNS/nobody/SA-ITOA/backfill_services/backfill report_as=text
| eval value=spath(value,"{}")
| fields value
| mvexpand value
| spath input=value
| eval t_start=strftime(t_start, "%H:%M:%S %d/%m/%Y")
| eval t_finish=strftime(t_finish, "%H:%M:%S %d/%m/%Y")
| rename t_start AS "Start_Time"
| rename t_finish AS "Finish_Time"
| table service_title kpi_title kpi_id Start_Time Finish_Time statusTo address this issue, modifications were made to the search by removing the |eval and |stats commands, along with updating the thresholding field to exclude _time.
These adjustments enabled the backfill process to work on indexed fields, successfully allowing for the retrieval of the historical data that had previously been missing.
| Revision | Publish Date | Comments |
|---|---|---|
1.0 |
29-Sep-2026
|
Initial Release |