Expected numeric value for data point.

Hi! I was just alerted to this - I took a brief look, and it would indeed have been useful if the error message had said which item was problematic, so I will register this as a potential improvement we could make to our systems. Unfortunately, since this report is now two weeks old, the logs for that request id seem to be gone - and even if I had found them, I don't think they would have contained more information about the value that failed to parse (I can see from our code that we do not log the actual input data or the position of the bad input data). However, as far as I can see from our code, this error can only happen if all of the value fields inside the datapoint list are strings (their values begin and end with double quotes) while the timeseries itself is a numeric timeseries. Note that even if a string seemingly contains a number, we still interpret it as a string: "value": "3.14" is only valid for a string timeseries, not for a numeric timeseries. If this happens again, please check every timeseries that is involved in your request, and make sure that the datapoint ingestion request only has got numeric values for the ones where isString is false, e.g. "value": 3.14, and only string values for the ones where isString is true.

Hi @Sonali Vishal Patil,

Do you still observe the above mentioned error?

Best regards,
Dilini