feat: unit type mappings

[garbados]

WIP branch for adding unit type mappings to the collected metrics. This PR checks metric keys for known suffixes like 'uptime' or 'cluster' which it maps to particular type values, like 'ms' or 'counter' respectively.

I tried to be thorough but I recognize there are mappings I may have missed or misinterpreted.

[janl]

Code looks good, but not sure it is all done yet:

I’m running this branch on a client’s db1 like so:

 DEBUG=1 AWS_REGION=$REGION COUCH_URL=$COUCHDB_URL ./bin.js start -i 60000

And things look promising in the console:

[aws-couchwatch] Setting up...
[aws-couchwatch] Set up to handle 2.x instance.
1244 metrics received.
1236 metrics received.
1257 metrics received.
1243 metrics received.
1250 metrics received.
1248 metrics received.

But all metrics show up as “Metrics with no dimensions”

Graphing e.g. various request_time metrics produce reasonable graphs, but with non-sensible units:

My expectation would be that this shows up as milliseconds, and that other metrics are received with their respective units as well.

[garbados]

That's very curious. On my dashboard, request_time values do show up as milliseconds 🤔

[janl]

@garbados can you give it a spin in the customer environment?

[garbados]

Sure thing, I'll try that.

[garbados]

I don't have access to the AWS console for these instances, so while I can run the tool from the client environment, I'm unable to examine the resultant metrics in AWS currently.

[garbados]

I've improved the type mappings and tested it from the Ruum box; everything seems to look right. Let me know what looks amiss and I'll fix it.