Kyle Brandt 590702c497 Azure: Handle real type nan/inf values in Log/Insights Analytics (#26342) ...

Before this, if the user were to divide by 0.0, "Infinity" would be returned in the result and the user would get an error: "unexpected type, expected json.Number but got string". Now these values are properly set as Inf values (and also made sure to handle NaN as well).

2020-07-15 09:39:41 -04:00

..

1-log-analytics-response-metrics-single-series.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

2-log-analytics-response-metrics-multiple-series.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

3-log-analytics-response-metrics-no-metric-column.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

4-log-analytics-response-metrics-no-time-column.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

5-log-analytics-response-metrics-no-value-column.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

6-log-analytics-response-table.json

azuremonitor: port azure log analytics query function to the backend (#23839)

2020-04-27 17:43:02 +02:00

7-log-analytics-all-types-table.json

Azure Monitor: Log Analytics response to data frames (#25297)

2020-06-05 12:32:10 -04:00

8-log-analytics-response-nan-inf.json

Azure: Handle real type nan/inf values in Log/Insights Analytics (#26342)

2020-07-15 09:39:41 -04:00