Aggregate dimensional metrics

[XiXiaPdx]

This is a stab to build off of this PR #376

Looking at the original comments by Vince, I think one missing piece was aggregating the dimensional metrics during the 5 second reporting interval? I took a stab at it.@tpitale , if you have some time, love to hear your thoughts on this. I know @mattbaker is interested in getting it over the finish line.

Also, I think that common block is accurate for count and summary - https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/report-metrics-metric-api/#optional-map-attributes.

But for gauge, it appears the interval.ms value isn't required. It probably does no harm 😄 As an aside, the old NR Telemetry SDK specs also show gauge without interval.ms

[CLAassistant]

All committers have signed the CLA.

[tpitale]

👀

[tpitale]

I have signed the CLA 👎🏼 I must have done it from my NR laptop 🙃

[XiXiaPdx]

I was able to send count and gauge to NR. https://staging.onenr.io/0oqQalyXGj1

But I'm having issues with summary and it is not clear to me why. I started a thread in help-metric

[tpitale]

Great stuff, thanks for picking this up!

[XiXiaPdx]

confirmed count gauge and summary are all making it to NR. https://staging.onenr.io/0kERzx3KAQr

[mattbaker]

Looks great. Sort of back tracked on how to handle the nil attribute thing (see comment) but otherwise this looks good to me! I see Tony already gave it the thumbs up.

We should give it a go in some prod systems to see how it goes.

Did you test the memory stuff with large maps in the key? I think that was the only remaining open question