Increasing metrics days collected for both AzureServiceBus and AWS SQS

[johnsimons]

We are increasing AzureServiceBus to collect 90 days of data and SQS to collect 365 days.
This is related to https://github.com/Particular/CustomerSuccess/issues/4092

[aleksandr-samila]

How can we distinguish your initialized "0" above from the metrics "0"?

[johnsimons]

Why do we need to distinguish whether the zero comes from the default or is set later on?
There is no reason to distinguish those.
The reason we need to do (metricValue.Total ?? 0) is because metricValue.Total can return a null, that is all.

[mikeminutillo]

Do we know what circumstances lead to a null?

[johnsimons]

@saratry @aleksandr-samila, I have pushed an update to deal with the start/end dates.
I tested this in both AWS and Azure, and both start creating metrics when a queue is created.
But because a user can create a new queue anytime, this means we can have multiple start dates based on when the queues are created. Which really means that the report will include the default 90 or 365 days for when the sampling is taken, but the actual internal data may not be for that length.

Also, I realise that if a customer decommissions an endpoint and deletes the queue, the metrics will no longer be available for the deleted queue. Hopefully, this is not something that happens a lot!