smart.finder indexing jobs
If smart.finder indexing jobs finish unsuccessfully and remain in an invalid state, this can disrupt internal data pipelines. You can monitor the success of a configured smart.finder indexing job in terms of content — in particular, the validation of the dates, taking into account the defined cron execution rules.
To do this, proceed as follows:
-
Register a new service with type con terra smart.finder.
-
Create a new job. Follow the example URL schema for Content field:
/smartfinder-server/indexingmanagement/select?q=state:"executing". -
Test the request.
{
"responseHeader":{
"status":0,
"QTime":0,
"params":{
"q":"state:\"executing\""}},
"response":{"numFound":1,"start":0,"docs":[
{
"_version_":"1659634922297491456",
"id":"Del6fHG9aPfQpvoB",
"count":"0",
"source":"<backend service>",
"title":"<title>",
"creator":"",
"email":"",
"created":"2020-01-28T15:23:29Z",
"modified":"2020-02-26T22:06:40Z",
"state":"executing",
"cronstring":"0 6 22 ? * WED *",
"lastSuccess":"2020-02-12T09:50:05.332Z",
"lastExecutionResult":"success",
"executionCount":2,
"targetState":"scheduled",
"coreName":"core0",
"timestamp":"2020-02-26T21:06:40.003Z"}
}Based on the information about the respective indexing job — lastSuccess and cronstring — service.monitor can calculate whether another indexing activity should already have taken place for this job.
In this case, service.monitor sends a notification.
|
You can create multiple service.monitor jobs to accommodate different responsibilities for servicing smart.finder jobs. You can modify the above example as follows: |