You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The DFA UI calls the endpoint _ml/data_frame/analytics/_explain for all analysis types. For outlier detection, no fields are supplied and the payload looks something like this:
If the index is a data stream which contains a counter field, an error is returned:
[memory_usage_estimation_137565] Unable to estimate memory usage as no documents in the source indices [metrics-weather_sensors-dev] contained all the fields selected for analysis. If you are relying on automatic field selection then there are currently mapped fields that do not exist in any indexed documents, and you will have to switch to explicit field selection and include only fields that exist in indexed documents.]: [memory_usage_estimation_137565] Unable to estimate memory usage as no documents in the source indices [metrics-weather_sensors-dev] contained all the fields selected for analysis. If you are relying on automatic field selection then there are currently mapped fields that do not exist in any indexed documents, and you will have to switch to explicit field selection and include only fields that exist in indexed documents.
This original description is wrong. The data being used when I originally noticed this had a counter field in the mappings, but it was not populated in the data.
When the counter field is populated, the error above does not happen. I don't know if it means this is still a problem, I would assume unpopulated counter fields should not cause the endpoint to throw an error?
In addition to this, currently the explain endpoint returns is_included: true for counter fields, is this correct?
The text was updated successfully, but these errors were encountered:
Further improvements to the anomaly detection and data frame analysts
wizards to ensure counter fields cannot be selected when configuring a
new job.
Adds a `counter` flag to the `new_job_caps` response which is used to
remove counter fields from dropdowns in the DFA and advanced AD wizards.
The outlier detection wizard still has an issue caused by the call to
the `_explain` endpoint. This needs to be fixed in elasticsearch
elastic/elasticsearch#94691
The DFA UI calls the endpoint
_ml/data_frame/analytics/_explain
for all analysis types. For outlier detection, no fields are supplied and the payload looks something like this:If the index is a data stream which contains a counter field, an error is returned:
[memory_usage_estimation_137565] Unable to estimate memory usage as no documents in the source indices [metrics-weather_sensors-dev] contained all the fields selected for analysis. If you are relying on automatic field selection then there are currently mapped fields that do not exist in any indexed documents, and you will have to switch to explicit field selection and include only fields that exist in indexed documents.]: [memory_usage_estimation_137565] Unable to estimate memory usage as no documents in the source indices [metrics-weather_sensors-dev] contained all the fields selected for analysis. If you are relying on automatic field selection then there are currently mapped fields that do not exist in any indexed documents, and you will have to switch to explicit field selection and include only fields that exist in indexed documents.
This original description is wrong. The data being used when I originally noticed this had a counter field in the mappings, but it was not populated in the data.
When the counter field is populated, the error above does not happen. I don't know if it means this is still a problem, I would assume unpopulated counter fields should not cause the endpoint to throw an error?
In addition to this, currently the explain endpoint returns
is_included: true
for counter fields, is this correct?The text was updated successfully, but these errors were encountered: