Schedule drift detection to occur immediately. If any changes are foind, the agent will report thenm back to the server in a separate request from agent to server. This method returns quickly and can be considered a non-blocking operation since the drift detection happens asynchronously.
Because the drift detection happens asynchronously, it cannot be guaranteed that the drift detection will actually happen immediately. Drift detection schedules are maintained by a priority queue and are ordered by their next scan time. The schedule corresponding to
resourceId and
driftDefinition has its next scan time reset in order to move the schedule to the front of the queue.
Note that when the drift detection occurs is largely dependent on a couple of factors. First there could be other schedules already at the front of the queue that would first be processed if their next scan times have also been reset. Secondly, drift detection occurs at regularly scheduled intervals in its own thread. If this method is called immediately after drift detection has just started, the earliest that the detection would occur is the time it takes for the current detection to finish plus the time period between executions of the drift detector task.
@param resourceId The id of the resource for which the request is being made
@param driftDefinition Specifies how the detection should be carried out. Thisincludes any filtering rules that should be applied.