Add metrics to understand the incidence rate of low, standard, and high fees

[andresgalante]

No description provided.

[Eshwari007]

@beguene To understand the metric accurately,despite selecting low,standard, high and custom received the same metric:

Is this accurate?
analytics.track('use_fee_estimation_default_simulated', {
estimations: [
{
fee: 224,
fee_rate: 37.39330897956175
},
{
fee: 1671,
fee_rate: 278.65419292979175
},
{
fee: 72159,
fee_rate: 12026.585281780368
}
],
maxValues: [
{
fee: 224,
fee_rate: 37.39330897956175
},
{
fee: 1671,
fee_rate: 278.65419292979175
},
{
fee: 72159,
fee_rate: 12026.585281780368
}
],
network: 'testnet',
route: '/send',
usingDefaultHiroApi: true,
version: '2.23.1.672'
});

Noticed that the fees were

but its listed as {
fee: 72159,
fee_rate: 12026.585281780368
}

in the segment without decimal,is this the way we want the display of the fees in segment?
Also believe we are not adding the metrics for custom hence will leave the criteria out

[Eshwari007]

If the above findings are accurate,we can move the ticket to merge.Thx

[beguene]

@Eshwari007 My bad, I changed the key name, can you please check again ?
The fee is in micro STX, this is what we use throughout (in our UX code, api, blockchain and documentation) and matches the fee_rate which is also in based on micro STX. I would prefer to stay consistent so we can communicate with the same units if there is an issue.
But if we really need it I can change it.

[andresgalante]

+1 for consistency!

[Eshwari007]

@beguene the key name is reflecting to the changes

I also cross checked the values are acccurate as being displayed within the ww and segment using the micro STX system.
Will move the ticket to Merge as testing completed