Hello,
When capturing HTTP status code by OneAgent bizevent capture from HTTP requests, the type of the captured field is double. Then if such a bizevent field is displayed without further conversion, values such as “200.0”, or “400.0” look strange at least to me.
If you create a metric using OpenPipeline and add this HTTP status (double type) as a dimension, you will still have dimensions with a point.
If you convert the double HTTP status using toLong() function and add such a dimension to a metric, it will never show up as a field in the legend.
The only workaround I was able to do is to convert it to long and then to string. Such string value can be then used as a dimension for splitting and successfully shows in the Legend.
So - my 2 questions
- In what universe is HTTP status a double type so that OneAgent bizevent capture stores it as double? (RFC specifies integer here)
- Why a dimension of long type can’t be used directly in the legend? Why is it not automatically converted to string as it is for double?