Hi, I had a question regarding the results index used in anomaly detection.
So far, I've created an anomaly detection job (let's say it has the job id 'ad-job'), in which I'm using partition_field and by_field.
I notice that there are two ways that I can see the results of the anomaly detection job:
POST .ml-anomalies-ad-job/_search
: This approach shows me some metadata of the anomaly detection job and shows me some data of anomalies when I query it further. However, it doesn't show me any of the partition_field_value/by_field_value which I need to view.POST _ml/anomaly_detectors/ad-job/results/records
: This query shows me everything I need, however it isn't an index?
As per my requirements, I basically want to take the results that I find from the second query and populate them in an index (which I can manually create if needed).
The reason why I need it in an index specifically is because querying code written on my usecase's backend can be generalized to any index.