Technical Tip: Machine Learning - HMM Learning Stage status 'Unconfirmed' and 'Confirmed' for a parameter
Description
This article describes about the new HMM Learning Stage 'Unconfirmed' and 'Confirmed' status introduced in 6.4 version, and also mentions how to overcome the situation where the parameter gets stuck at 'Unconfirmed' and discarded by the garbage collector eventually.
Scope
For version 6.4.
Solution
When ML anomaly detection learns a new parameter in 6.4 version, it sets the status of that new parameter to 'Unconfirmed' initially.


An event log gets generated 'Parameter deleted due to being unconfirmed for too long for parameter <submit> of URL </>. Parameter model changed from Running to Discarded by FortiWeb daemon'.
Denzil-ML-64 (machine-learni~g) edit 1
Denzil-ML-64 (1) set ip-expire-cnts 1
Denzil-ML-64 (1) end
The status will be changed to 'Confirmed' and then to 'Collecting' immediately as soon as ML sees a HTTP request with that parameter.

Related document:
Machine learning troubleshooting - FortiWeb 8.0.0 administration guide
